Hi, Am Donnerstag, den 10.03.2011, 14:49 +0000 schrieb Alasdair Nottingham: > I think it would depend on how you are thinking of hooking this in. I > wouldn't want > this in the jndi-core project itself. I think this is perhaps more of > a jndi-legacy-support > thing.
Surely not part of jndi-core, probably not even jndi-legacy-support but rather a separate one -- mostly along the lines of the JMX whiteboard project. As it stands now it is a single class plus its activator. Regards Felix > > So rather than imagining the 20 bazillian ways you could integrate and > commenting on them > I'm wondering if you can provide more information. > > Alasdair > > On 10 March 2011 14:20, Felix Meschberger <[email protected]> wrote: > > Hi all, > > > > We have a problem to register OSGi services with JNDI (mostly in the > > java:comp context and its subcontexts) for supporting legacy > > applications moved to OSGi (but not fully converted). > > > > So my idea was to add whiteboard pattern registration support for JNDI: > > Each service registered with a special service registration property, > > say aries.jndi.name, is registered within a JNDI context. > > > > For example if the UserTransaction service is registered with > > aries.jndi.name = java:comp/UserTransaction > > it would be registered as java:comp/UserTransaction. > > > > Likewise a DataSource service registered with > > aries.jndi.name = java:comp/env/jdbc/sampleDS > > would be registered as java:comp/env/jdbc/sampleDS > > > > The environment of the initial context used by this whiteboard helper is > > configurable with ConfigurationAdmin configuration (defaulting to an > > empty environment). > > > > Does this make sense ? > > > > I have created a first version of such a JNDI white board support > > "service", which I would be contributing. > > > > Regards > > Felix > > > > > > >
