|
From: Colin S. <col...@ex...> - 2006-07-02 16:27:10
|
All,
The code from the LdapTemplate project:
http://ldaptemplate.sourcefourge.net
created by Ulrik Sandberg & Mattias Arthursson now has a new home as a
full Spring subproject: Spring-LDAP!
This is a very useful library for accessing LDAP without much of the
normal boilerplate, as well as doing DAO style operations with LDAP. It
is similar in some respects to JdbcTemplate, and in fact includes an
LdapTemplate class.
I have checked in Spring-LDAP as part of spring-projects. It is
available via SVN from:
https://svn.sourceforge.net/svnroot/springframework/spring-projects/trunk/spring-ldap
but you normally need to check out spring-projects entirely, since it
will need to build with common-build out of spring-projects:
https://svn.sourceforge.net/svnroot/springframework/spring-projects/trunk
This code is based off the v1.0.2 LdapTemplate release. I have not
touched (refactoring aside) any code, but there were some
logistics/changes involved:
- refactor 'net.sf.ldaptemplate' base package to
'org.springframework.ldap'
- LdapTemplate used common-build, but based of a slightly older
version. In the meantime, common-build in spring-projects has moved to
Maven2 directory conventions, so I had to refactor the actual source trees
- LdapTemplate used to have a static filesytem repo of jars. I have
made the new code pull everything from online, via a combination of the
maven2 public repo as well as our own http repo (just an http view of
part of our svn directory). This did change some jar version numbers.
- unit tests currently run ok
- integration tests currently compile (in Eclipse), but the
spring-projects version of common-build actually needs to be upgraded to
do the compiles, and run them.
Going forward, Ulrik and Mattias will continue to mostly maintain the
code, but I will help at least with logistics.
I will ensure a proper Jira target is set up.
We will most likely release the next version as spring-ldap-1.0.3 to
continue from ldaptemplate-1.0.2, but I don't think we should feel 100%
constrained to this. If somebody can strongly justify the need for a
refactoring or something of that nature that would entail some big
changes, it could go out as a 1.1-dev or something like that.
---
Colin Sampaleanu
Principal, Interface21
Spring Training, Consulting and Support - "From the Source"
http://www.interface21.com
|