directory-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Trustin Lee (JIRA)" <>
Subject [jira] Commented: (DIREVE-316) StringUtils & StringTools
Date Wed, 21 Dec 2005 09:34:33 GMT
    [ ] 

Trustin Lee commented on DIREVE-316:

The original reason we forked commons-* is because of the infamous class loader problem when
ApacheDS is embedded in WAS.  This became a problem because WAS also used commons-* JARs.
 I guess this issue must have been resolved in many WAS in market.  The other reason I discussed
with Alex was that commons-* projects sometimes introduces the change of behavior between
minor version-ups, and it produces unexpected bugs.  It makes sense, but it think this is
a matter of trust for other projects.  I think we cannot say less dependency is a good thing

BTW I had to fork NIO ByteBuffer because it was really hard to extend java.nio.ByteBuffer.

> StringUtils & StringTools
> -------------------------
>          Key: DIREVE-316
>          URL:
>      Project: Directory Server
>         Type: Improvement
>     Reporter: Emmanuel Lecharny
>     Priority: Minor

> We have two classes which semantics are almost the same :
> - StringTools in ldap-common
> - StringUtils in asn1-codec
> The second one is horrible, because it overlaps with the a.o.commons.lang.StringUtils.
> I think it could be good to merge both classes into StringTools, and to move this class
in a common subproject to be created (ads-commons, for instance). 
> wdyt ?

This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
For more information on JIRA, see:

View raw message