[
https://issues.apache.org/jira/browse/ARIES-343?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jarek Gawor resolved ARIES-343.
-------------------------------
Fix Version/s: 0.2
Resolution: Invalid
As mentioned before this is working as expected and there are ways of passing
the appropriate calling bundle to the jndi code.
> AbstractServiceRegistryContext caches BundleContexts inappropriately
> --------------------------------------------------------------------
>
> Key: ARIES-343
> URL: https://issues.apache.org/jira/browse/ARIES-343
> Project: Aries
> Issue Type: Bug
> Components: JNDI
> Affects Versions: 0.2
> Reporter: Holly Cummins
> Fix For: 0.2
>
>
> We've recently made a change to AbstractServiceRegistryContext so that it
> gets passed a BundleContext on construction and caches it. This creates
> problems down the line because utility bundles will end up using their own
> bundle context for lookups instead of the context of the calling bundle. I've
> seen this behaviour in calls to ServiceHelper.findService().
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
