[jira] Resolved: (ARIES-51) Allow to use different blueprint bundle tracker customizer based on different osgi framework

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

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

Lin Sun resolved ARIES-51.
--------------------------

    Resolution: Fixed

> Allow to use different blueprint bundle tracker customizer based on different osgi framework
> --------------------------------------------------------------------------------------------
>
>                 Key: ARIES-51
>                 URL: https://issues.apache.org/jira/browse/ARIES-51
>             Project: Aries
>          Issue Type: New Feature
>            Reporter: Lin Sun
>            Assignee: Lin Sun
>
> In Aries-7, we provided a default blueprint bundle tracker customizer.  However, this default tracker customizer only handles bundles installed in the same framework as the Aries blueprint bundle.   I'd like to propose an alternative blueprint bundle tracker customizer that handles bundles installed in the child frameworks as well, and we would only use this blue print tracker customizer if we can find CompositeBundleFactory service (as defined in RFC 138 draft) in the OSGi service registry.   My understanding is that the CompositeBundleFactory service exists for equinox 3.5 but not felix.

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