You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@aries.apache.org by "Valentin Mahrwald (JIRA)" <ji...@apache.org> on 2010/01/20 17:25:54 UTC

[jira] Commented: (ARIES-125) Implement a new BundleTracker that automatically filters out events related to framework bundles in a composite bundle

    [ https://issues.apache.org/jira/browse/ARIES-125?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12802884#action_12802884 ] 

Valentin Mahrwald commented on ARIES-125:
-----------------------------------------

Two things I noticed when I tried to use this in the JPA container:
- The statemask supplied to AriesCompositeBundleTracker is not used (incorrectly, I think) for tracking inside child frameworks
- The class does not correctly handle BundleTracker.getObject, BundleTracker.getBundles and other methods that inspect the currently tracked bundles. I do not think we absolutely need to support these methods (so you could not choose not to inherit from BundleTracker). But if we do, the methods should work as expected.

> Implement a new BundleTracker that automatically filters out events related to framework bundles in a composite bundle
> ----------------------------------------------------------------------------------------------------------------------
>
>                 Key: ARIES-125
>                 URL: https://issues.apache.org/jira/browse/ARIES-125
>             Project: Aries
>          Issue Type: Improvement
>    Affects Versions: Incubation
>            Reporter: Brian DePradine
>         Attachments: patch.txt
>
>
> This new BundleTracker should be aware of what a CompositeBundle is and should automatically handle events related to framework bundles. This should make life a bit easier for clients.

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