You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@aries.apache.org by "zoe slattery (JIRA)" <ji...@apache.org> on 2010/09/07 11:35:34 UTC
[jira] Updated: (ARIES-397) Enable ServiceRegistryContext caching
override
[ https://issues.apache.org/jira/browse/ARIES-397?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
zoe slattery updated ARIES-397:
-------------------------------
Fix Version/s: 0.3
(was: Incubation)
> Enable ServiceRegistryContext caching override
> ----------------------------------------------
>
> Key: ARIES-397
> URL: https://issues.apache.org/jira/browse/ARIES-397
> Project: Aries
> Issue Type: Improvement
> Components: JNDI
> Affects Versions: Incubation
> Reporter: Mark Nuttall
> Assignee: Mark Nuttall
> Fix For: 0.3
>
> Original Estimate: 1h
> Remaining Estimate: 1h
>
> Further to Aries-343, environments consuming jndi-url but not jndi-core need a way to work around the caching behaviour seen in AbstractServiceRegistryContext. Change the AbstractServiceRegistryContext constructors so that if a BundleContext is provided in the input environment under the JNDIConstants.BUNDLE_CONTEXT key, this BundleContext should be used in preference to the 'callerContext' argument. Although _a_ BundleContext, it's not in this case the one that should be used.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.