[
https://issues.apache.org/jira/browse/ARIES-1215?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Thomas Watson resolved ARIES-1215.
----------------------------------
Resolution: Fixed
Assignee: Thomas Watson
I fixed this in commit:
http://svn.apache.org/viewvc?view=revision&revision=1609727
If the property org.apache.aries.blueprint.use.system.context=true is set
then the blueprint extender will use the system bundle context to track
blueprint bundles
and track NamespaceHandler services.
Two new testcases were added.
1) verifies that if a blueprint bundle is hidden
from the blueprint extender, using bundle hooks, then the blueprint extender
can still
track the bundle properly using the system bundle context
2) verifies that if the blueprint cm bundle is hidden from the
blueprint extender, using service hooks, then the blueprint extender can still
process blueprint bundles that use the cm namespace handler properly
When org.apache.aries.blueprint.use.system.context=true the blueprint extender
will no longer use the RecursiveBundleTracker. This means that the old
equinox composite bundles will not be supported when this option is enabled.
This option is intended to be used with subsystems.
> Use system bundle for tracking namespace handlers and bundles
> -------------------------------------------------------------
>
> Key: ARIES-1215
> URL: https://issues.apache.org/jira/browse/ARIES-1215
> Project: Aries
> Issue Type: Improvement
> Components: Blueprint
> Reporter: Thomas Watson
> Assignee: Thomas Watson
>
> The blueprint implementation currently uses its own BundleContext to track
> Namespace handlers. This can cause issues if namespace handlers are
> contained in subsystems. One approach to support namespace handlers
> contained in application subsystems would be for blueprint to use the system
> bundle context to track namespace handlers.
> Blueprint also uses the org.apache.aries.util.tracker.RecursiveBundleTracker
> to track bundles with blueprint components. The RecursiveBundleTracker
> understands composites and knows how to recurse into them to track for
> blueprints contained in composite bundles. We should make the dependency on
> RecursiveBundleTracker optional and fallback to using the system bundle
> context for tracking blueprints. This would allow for the support of
> subsystems with blueprints.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
