[jboss-osgi-issues] [JBoss JIRA] (JBOSGI-689) Complete support for OSGi JNDI

[Thomas Diesler (JIRA)]

     [ https://issues.jboss.org/browse/JBOSGI-689?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Thomas Diesler updated JBOSGI-689:
----------------------------------

    Component/s: JNDI
                 WildFly

    
> Complete support for OSGi JNDI
> ------------------------------
>
>                 Key: JBOSGI-689
>                 URL: https://issues.jboss.org/browse/JBOSGI-689
>             Project: JBoss OSGi
>          Issue Type: Feature Request
>          Components: JNDI, WildFly
>            Reporter: Thomas Diesler
>              Labels: roadmap
>
> As expected because of the missing integration with the NamingManger singletons, all tests that go through NamingManager to obtain the InitialContextFactory or the ObjectFactory fail.
> {code}
> Running org.jboss.test.osgi.example.jndi.JNDITestCase
> Tests run: 12, Failures: 1, Errors: 2, Skipped: 2, Time elapsed: 15.574 sec <<< FAILURE!
> Results :
> Failed tests:   testContextManagerReferenceBinding(org.jboss.test.osgi.example.jndi.JNDITestCase): expected:<bar> but was:<Reference Class Name: java.lang.String(..)
> Tests in error: 
>   testTraditionalAPIValueBinding(org.jboss.test.osgi.example.jndi.JNDITestCase): JBAS011843: Failed instantiate InitialContextFactory org.jboss.test.osgi.example.jndi.bundle.JNDITestActivator$SimpleInitalContextFactory from classloader ModuleClassLoader for Module "deployment.arquillian-service:main" from Service Module Loader
>   testTraditionalAPIReferenceBinding(org.jboss.test.osgi.example.jndi.JNDITestCase): JBAS011843: Failed instantiate InitialContextFactory org.jboss.test.osgi.example.jndi.bundle.JNDITestActivator$SimpleInitalContextFactory from classloader ModuleClassLoader for Module "deployment.arquillian-service:main" from Service Module Loader
> {code}
> In reality it means that OSGi Bundles cannot use JNDI with object References and cannot expect the traditional JNDI API to work. These findings generally raise the question how a spec compliant OSGI JNDI Implementation is supposed to work in a container environment. Specifically, in an environment that has already set the NamingManager singletons.
> IMHO there is a layer of abstraction missing. Perhaps the container should register a NamingManger service that the JNDI Implementation can use to register its InitialContextFactoryBuilder and ObjectFactoryBuilder.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira