You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@directory.apache.org by "Alex Karasulu (JIRA)" <di...@incubator.apache.org> on 2005/09/23 08:35:31 UTC

[jira] Resolved: (DIREVE-246) Addition of ExprNode to environment props causing tight coupling of LDAP wire protocol to ApacheDS core

     [ http://issues.apache.org/jira/browse/DIREVE-246?page=all ]
     
Alex Karasulu resolved DIREVE-246:
----------------------------------

    Fix Version: 0.9.3
     Resolution: Fixed

ommited in revision 291082 here:

http://svn.apache.org/viewcvs.cgi?view=rev&rev=291082

> Addition of ExprNode to environment props causing tight coupling of LDAP wire protocol to ApacheDS core
> -------------------------------------------------------------------------------------------------------
>
>          Key: DIREVE-246
>          URL: http://issues.apache.org/jira/browse/DIREVE-246
>      Project: Directory Server
>         Type: Improvement
>     Reporter: Enrique Rodriguez
>     Assignee: Alex Karasulu
>     Priority: Minor
>      Fix For: 0.9.3

>
> SearchHandler.java:114 adds a filter created by the LDAP wire protocol to the context environment, for use by the JNDI provider.  This causes an issue decoupling the LDAP protocol provider from the backing store.   This issue arises with the OSGi container, resulting in a NoClassDefFoundError unless the filter package is shared between apacheds-core and ldap-protocol.
> At this point in the code there is an old note discussing the need to improve this "Eve JNDI Provider Specific Hack."

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira