[
https://issues.apache.org/jira/browse/GERONIMO-5445?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
David Jencks closed GERONIMO-5445.
----------------------------------
Resolution: Fixed
This is more complicated than it seems since jndi is supposed to produce a new
object on each lookup but aries jndi is quite effective at always returning the
same object. Connectors are now using a ref that looks up osgi services. We
can open other issues if we decide this is a reasonable approach for other
objects.
> Use links to osgi jndi (that look up osgi services) rather than looking up
> gbeans
> ---------------------------------------------------------------------------------
>
> Key: GERONIMO-5445
> URL: https://issues.apache.org/jira/browse/GERONIMO-5445
> Project: Geronimo
> Issue Type: Improvement
> Security Level: public(Regular issues)
> Components: naming
> Affects Versions: 3.0
> Reporter: David Jencks
> Assignee: David Jencks
> Fix For: 3.0
>
>
> One thing we can do to move closer to osgi is to hook up the java: jndi stuff
> to osgi services rather than the kernel gbean registry as at present. This
> won't work using the osgi: stuff directly because many java: objects such as
> javax.mail.Session can't be proxied. However, pending the resolution of
> ARIES-356 we may be able to use the aries: namespace, or just define our own
> more direct lookup.
> Implemented first for connectors, ejb's are also a candidate.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
