Hi all!

There is a new effort within the Groovy community to include LDAP
support within Groovy ("Gldap"). It is driven by Luke Daley (cc) and has
nothing to do with my attempt. The mission statement/target
group/approach is totally different. For instance Gldap provides mapping
between Groovy objects (defined via a class) and LDAP entries. Gldap
operates on top of Spring LDAP (and inherit the dependency to the Spring
Framework).

Learn more about it here:
http://groovy.codehaus.org/Gldap

Luke and Guillaume Laforge encouraged me to continue my work on an LDAP
integration alternative in Groovy targeted to people familiar with LDAP,
although I do not know who will use/find/need it, if Gldap is hosted by
Groovy itself. For programming triggers and stored procedures within
ApacheDS in Groovy, I still think my approach is more suitable, because
it does not abstract from the underlying directory, and has a minimum of
dependencies.

Greetings from Hamburg,
Stefan

---8<---

Stefan Zoerner (szoerner-1oDqGaOF3Lkdnm+yROfE0A@public.gmane.org)
Committer :: PMC Member

Apache Directory Project
http://directory.apache.org

[ Post a follow-up to this message ]

FYI a friend name Rickard (CC'd above) was thinking of working on some OR or
rather OH (object hierarchical) mapping tool for LDAP.  I think the same
code can be used by Groovy
eventually.  Rickard wanted to work on it here at Directory.

Alex

On 6/30/07, Stefan Zoerner <szoerner-1oDqGaOF3Lkdnm+yROfE0A@public.gmane.org> wrote:
>
> Hi all!
>
> There is a new effort within the Groovy community to include LDAP
> support within Groovy ("Gldap"). It is driven by Luke Daley (cc) and has
> nothing to do with my attempt. The mission statement/target
> group/approach is totally different. For instance Gldap provides mapping
> between Groovy objects (defined via a class) and LDAP entries. Gldap
> operates on top of Spring LDAP (and inherit the dependency to the Spring
> Framework).
>
> Learn more about it here:
> http://groovy.codehaus.org/Gldap
>
> Luke and Guillaume Laforge encouraged me to continue my work on an LDAP
> integration alternative in Groovy targeted to people familiar with LDAP,
> although I do not know who will use/find/need it, if Gldap is hosted by
> Groovy itself. For programming triggers and stored procedures within
> ApacheDS in Groovy, I still think my approach is more suitable, because
> it does not abstract from the underlying directory, and has a minimum of
> dependencies.
>
> Greetings from Hamburg,
>      Stefan
>
> ---8<---
>
> Stefan Zoerner (szoerner-1oDqGaOF3Lkdnm+yROfE0A@public.gmane.org)
> Committer :: PMC Member
>
> Apache Directory Project
> http://directory.apache.org
>
>
> ---------- Forwarded message ----------
> From: Luke Daley <ld-Hc2V4H83aCrQT0dZR+AlfA@public.gmane.org>
> To: Groovy Users <user-i9PBDF1N6cxnkHa44VUL00B+6BGkLq7r@public.gmane.org>
> Date: Sat, 30 Jun 2007 20:12:45 +1000
> Subject: [groovy-user] Gldap 0.1
> Hi,
>
> Gldap 0.1 is available.
>
> Compiled: http://staff.cqu.edu.au/daleyl/gldap-0.1.tar.gz
> Source: http://staff.cqu.edu.au/daleyl/gldap-src-0.1.zip
> Wiki: http://groovy.codehaus.org/Gldap
>
> It's pretty rough around the edges. There is little documentation,
> but probably enough to get the idea. It also only supports searching
> ATM.
>
> This is my first reasonable Open Source contribution so I would
> appreciate any feedback.
>
> Thanks,
>
> - LD.
>
> ---------------------------------------------------------------------
> To unsubscribe from this list please visit:
>
>     http://xircles.codehaus.org/manage_email
>
>
>
>
>

[ Post a follow-up to this message ]

Stefan,
I agree with you about the scripting for triggers, etc.  I think this should
actually be much easier to do as an abstraction over the existing APIs like
you are already doing.

Chris

On 6/30/07, Stefan Zoerner <szoerner-1oDqGaOF3Lkdnm+yROfE0A@public.gmane.org> wrote:
>
> Hi all!
>
> There is a new effort within the Groovy community to include LDAP
> support within Groovy ("Gldap"). It is driven by Luke Daley (cc) and has
> nothing to do with my attempt. The mission statement/target
> group/approach is totally different. For instance Gldap provides mapping
> between Groovy objects (defined via a class) and LDAP entries. Gldap
> operates on top of Spring LDAP (and inherit the dependency to the Spring
> Framework).
>
> Learn more about it here:
> http://groovy.codehaus.org/Gldap
>
> Luke and Guillaume Laforge encouraged me to continue my work on an LDAP
> integration alternative in Groovy targeted to people familiar with LDAP,
> although I do not know who will use/find/need it, if Gldap is hosted by
> Groovy itself. For programming triggers and stored procedures within
> ApacheDS in Groovy, I still think my approach is more suitable, because
> it does not abstract from the underlying directory, and has a minimum of
> dependencies.
>
> Greetings from Hamburg,
>      Stefan
>
> ---8<---
>
> Stefan Zoerner (szoerner-1oDqGaOF3Lkdnm+yROfE0A@public.gmane.org)
> Committer :: PMC Member
>
> Apache Directory Project
> http://directory.apache.org
>
>
> ---------- Forwarded message ----------
> From: Luke Daley <ld-Hc2V4H83aCrQT0dZR+AlfA@public.gmane.org>
> To: Groovy Users <user-i9PBDF1N6cxnkHa44VUL00B+6BGkLq7r@public.gmane.org>
> Date: Sat, 30 Jun 2007 20:12:45 +1000
> Subject: [groovy-user] Gldap 0.1
> Hi,
>
> Gldap 0.1 is available.
>
> Compiled: http://staff.cqu.edu.au/daleyl/gldap-0.1.tar.gz
> Source: http://staff.cqu.edu.au/daleyl/gldap-src-0.1.zip
> Wiki: http://groovy.codehaus.org/Gldap
>
> It's pretty rough around the edges. There is little documentation,
> but probably enough to get the idea. It also only supports searching
> ATM.
>
> This is my first reasonable Open Source contribution so I would
> appreciate any feedback.
>
> Thanks,
>
> - LD.
>
> ---------------------------------------------------------------------
> To unsubscribe from this list please visit:
>
>     http://xircles.codehaus.org/manage_email
>
>
>
>
>

[ Post a follow-up to this message ]