Hi Guillaume
Nice work.
I've also done some prototyping work on JNDI/OSGi integration, and I
have some questions:
* Where did you find the RFC 142 ? I've search the core & compendium 4.2
drafts with no success.
* If I understand well, what the contribution do is allowing OSGi
services access from a simple InitialContext.lookup, right ?
* Does this contribution address the general JNDI/OSGi problem, that is
'JNDI is always using the TCCL to load classes' ?
This is that last point that I've worked on.
For example, ObjectFactory instances (the objects that knows how to
recreate an instance from a Reference object) are registered as OSGi
services, and I've provided an ObjectFactoryBuilder, that is OSGi aware,
and that looks in the service registry for an ObjectFactory with a given
name. If the ObjectFactory is found, it returns it to be used by JNDI,
so no new classloading ...
There is a similar problem with InitialContextFactory (that are loaded
from a given ClassLoader)...
Does the RFC 142 also addresses theses 2 points ?
Cheers
--Guillaume
BTW, the code is here:
Eclipse workspace:
http://fisheye.easybeans.org/browse/EasyBeans/sandbox/sauthieg/naming
Core code:
http://fisheye.easybeans.org/browse/EasyBeans/sandbox/sauthieg/naming/org.ow2.jonas.naming.factories/src/org/ow2/jonas/naming/factories
Guillaume Nodet a écrit :
I have attached to the above issues two patches which consist of
implementations of RFC-0142 (JNDI integration) and RFC-98
(Transactions in OSGi).
I have refactored the implementations in ServiceMix NMR so that they
do not have any dependenies on Spring-DM and become standalone
bundles.
Feedback welcome!
