You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@directory.apache.org by "Enrique Rodriguez (JIRA)" <di...@incubator.apache.org> on 2005/09/07 16:15:31 UTC
[jira] Created: (DIREVE-244) Static ContextFactoryService call causing tight coupling of LDAP wire protocol to ApacheDS core
Static ContextFactoryService call causing tight coupling of LDAP wire protocol to ApacheDS core
-----------------------------------------------------------------------------------------------
Key: DIREVE-244
URL: http://issues.apache.org/jira/browse/DIREVE-244
Project: Directory Server
Type: Improvement
Reporter: Enrique Rodriguez
Assigned to: Alex Karasulu
ModifyHandler.java:101 makes a static call using ContextFactoryService. This call traverses the o.a.ldap.server.jndi and o.a.ldap.server.schema packages, which causes tight coupling of the LDAP wire protocol to the apacheds core. This makes it difficult to de-couple the LDAP protocol provider from the backing store. This issue arises with the OSGi container, resulting in a NoClassDefFoundError unless I start opening packages between apacheds-core and ldap-protocol:
- java.lang.NoClassDefFoundError: org/apache/ldap/server/jndi/ContextFactoryService
at org.apache.ldap.server.protocol.ModifyHandler.messageReceived(ModifyHandler.java:101)
at org.apache.mina.protocol.handler.DemuxingProtocolHandler.messageReceived(DemuxingProtocolHandler.java:70)
The code at this point contains the TODO to "figure out how to best integrate this code into the schema interceptor."
--
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
[jira] Closed: (DIREVE-244) Static ContextFactoryService call causing tight coupling of LDAP wire protocol to ApacheDS core
Posted by "Enrique Rodriguez (JIRA)" <di...@incubator.apache.org>.
[ http://issues.apache.org/jira/browse/DIREVE-244?page=all ]
Enrique Rodriguez closed DIREVE-244:
------------------------------------
Fix Version: 0.9.3
Resolution: Fixed
Rebuilt and tested fine.
> Static ContextFactoryService call causing tight coupling of LDAP wire protocol to ApacheDS core
> -----------------------------------------------------------------------------------------------
>
> Key: DIREVE-244
> URL: http://issues.apache.org/jira/browse/DIREVE-244
> Project: Directory Server
> Type: Improvement
> Reporter: Enrique Rodriguez
> Assignee: Alex Karasulu
> Fix For: 0.9.3
>
> ModifyHandler.java:101 makes a static call using ContextFactoryService. This call traverses the o.a.ldap.server.jndi and o.a.ldap.server.schema packages, which causes tight coupling of the LDAP wire protocol to the apacheds core. This makes it difficult to de-couple the LDAP protocol provider from the backing store. This issue arises with the OSGi container, resulting in a NoClassDefFoundError unless I start opening packages between apacheds-core and ldap-protocol:
> - java.lang.NoClassDefFoundError: org/apache/ldap/server/jndi/ContextFactoryService
> at org.apache.ldap.server.protocol.ModifyHandler.messageReceived(ModifyHandler.java:101)
> at org.apache.mina.protocol.handler.DemuxingProtocolHandler.messageReceived(DemuxingProtocolHandler.java:70)
> The code at this point contains the TODO to "figure out how to best integrate this code into the schema interceptor."
--
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