Mailing-List: contact dev-help@directory.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Apache Directory Developers List" <dev@directory.apache.org>
Received-SPF: pass (nike.apache.org: domain of
 gcaidd-directory-dev@m.gmane.org designates 80.91.229.12 as permitted sender)
To: dev@directory.apache.org
connect(): No such file or directory
From: =?UTF-8?B?SsO2cmc=?= Schaible <joerg.schaible@gmx.de>
Subject: Re: [ApacheDS] Scripting, groovy, stored procedures and Java 6
Followup-To: gmane.comp.apache.incubator.directory.devel
Date: Fri, 28 May 2010 09:23:39 +0200
Lines: 19
Message-ID: <htnr1r$frt$1@dough.gmane.org>
References: <AANLkTikr0dSi7myHKGbVbBcGfm9p8-0h5Ixtidz6lKMZ@mail.gmail.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: 8Bit
X-Complaints-To: usenet@dough.gmane.org
X-Gmane-NNTP-Posting-Host: mail.elsag-solutions.com
User-Agent: KNode/4.3.5
X-Virus-Checked: Checked by ClamAV on apache.org

Alex Karasulu wrote:

> Hi all,
> 
> I don't know what state Groovy LDAP is in but it would be really neat to
> be able to leverage Groovy as a SP scripting language in the server. This
> means certain bindings will most likely be needed but there's also the
> Java 6 scripting support we will need. Regardless of this need for Java 6,
> I'm of the opinion we should move to Java 6 anyway considering the EOL for
> Java 5.
> 
> Thoughts?

You may alternatively use BSF 3.0 that provides the JSR 223 scripting 
support down to JDK 1.4, i.e. in a Java 6 environment you can drop the BSF 
artifact while for Java 5 it is enough to add it as runtime dep.

- Jörg