[jira] Resolved: (ARIES-272) BundleTrackerCustomizers will not recurse on bundles added to a CompositeBundle before the composite bundle is started

["Lin Sun (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/ARIES-272?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Lin Sun resolved ARIES-272.
---------------------------

      Assignee: Lin Sun
    Resolution: Fixed

Patch integrated in rev 941776.  Thanks Holly!

> BundleTrackerCustomizers will not recurse on bundles added to a CompositeBundle before the composite bundle is started
> ----------------------------------------------------------------------------------------------------------------------
>
>                 Key: ARIES-272
>                 URL: https://issues.apache.org/jira/browse/ARIES-272
>             Project: Aries
>          Issue Type: Improvement
>            Reporter: Holly Cummins
>            Assignee: Lin Sun
>         Attachments: aries272-revised.patch, aries272.patch, InternalRecursiveBundleTracker.java
>
>   Original Estimate: 24h
>  Remaining Estimate: 24h
>
> At the moment the AbstractBundleTrackerCustomizer and its descendents trap Bundle.STARTING events. If the originator is a composite bundle they add themselves as a tracker to the composite bundle's context so that they are notified of bundle events in the child framework. This model assumes that the child bundles are added to the composite bundle *after* it is started. It would be better to trap Bundle.INSTALLED events, since child bundles can be added any time after the composite bundle is installed. For example, if the composite bundle has exports, its children have to be added *before* it is started so that it can satisfy the exports.
> There is also quite a lot of  redunant and duplicate code in the area of the bundle tracker customizers which should be cleaned up.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.