[jboss-osgi-issues] [JBoss JIRA] (JBOSGI-81) Compliant JNDI integration
David Bosschaert (JIRA)
jira-events at lists.jboss.org
Wed Feb 8 10:43:48 EST 2012
[ https://issues.jboss.org/browse/JBOSGI-81?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12665080#comment-12665080 ]
David Bosschaert commented on JBOSGI-81:
----------------------------------------
The actual problem is this:
{noformat}Failed: org.jboss.test.osgi.example.jbossas.JNDIIntegrationTestCase.testOSGiNamingContext: java.lang.ClassCastException: org.apache.aries.jndi.ContextManagerService cannot be cast to org.osgi.service.jndi.JNDIContextManager
at org.jboss.test.osgi.NamingSupport.provideJNDIIntegration(NamingSupport.java:47)
at org.jboss.test.osgi.example.jbossas.JNDIIntegrationTestCase.testOSGiNamingContext(JNDIIntegrationTestCase.java:88){noformat}
Looking at the source in Aries, the ContextManagerService implements JNDIContextManager. So the test must be getting the JNDIContextManager class from another source than the Aries JNDI bundle.
> Compliant JNDI integration
> --------------------------
>
> Key: JBOSGI-81
> URL: https://issues.jboss.org/browse/JBOSGI-81
> Project: JBoss OSGi
> Issue Type: Task
> Security Level: Public(Everyone can see)
> Components: Enterprise Services
> Reporter: Thomas Diesler
> Assignee: David Bosschaert
> Fix For: JBossOSGi 1.0.1
>
>
> Chapter 126 in the OSGi Enterprise Specification 4.2: http://www.osgi.org/Download/Release4V42
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
More information about the jboss-osgi-issues
mailing list