harmony-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Regis <xu.re...@gmail.com>
Subject Re: [classlib][ldap] Several development concerns about Ldap service provider
Date Fri, 07 Sep 2007 05:26:47 GMT

Spark Shen wrote:
> We had some discussions[1] with developers in Apache DS community. And find
> they have existing sharable classes.
> http://svn.apache.org/viewvc/directory/shared/trunk/ldap/src/main/java/org/apache/directory/shared/ldap/
> These classes constitute 3 major features.
> 1. codec - encode/decode ldap message
> 2. filter - parsing search filters such as 'cn=*'
> 3. schema - parsing schema
> I prefer to include them into our project instead of re-implement.
> We do have problems. So far, I can see at least 2 problems:
> 1. Dependency: How should we include those code from Apache DS. Using binary
> jars as Yoko, or SVN external link as our concurrent module.
> Both of the methods will have its pro & con. Binary form will involve more
> manual efforts, while external link may potentially pollute our code base.
I prefer to use binary jars, because the interface and methods we used 
should be stable, use SVN external link may make our code in unstable 

ApacheDS also depends on some jars, such as common-lang, antlr, if they 
can provide the whole package is the best.
> 2. Code duplication: Apache DS have classes which will duplicate our code. A
> simple example is LdapDN. Shall we adapt our implementation to their code?
> Any comments?
seems ApackeDS' implementation can't avoid, so we should use theirs as 
more as possible, if there is no way to avoid using both implementations 
simultaneous, adaptor would be helpful.
> [1]http://www.nabble.com/-OT--Is-studio-using-Sun'
> s-ldap-service-provider--t4376387.html

View raw message