You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@aries.apache.org by "John Ross (JIRA)" <ji...@apache.org> on 2012/11/02 15:19:11 UTC

[jira] [Commented] (ARIES-956) Add ability to update the sharing policy of composite subsystems.

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

John Ross commented on ARIES-956:
---------------------------------

Further discussion regarding this issue took place outside of JIRA and the mailing lists. Assuming I understand correctly, the result of that discussion was that a requirement exists for the ability to update the sharing policy of an already installed composite. I realize this is all within the context of the broader discussion of updating subsystems in general but wanted to narrow the scope here to address the immediate issue. Is this scope sufficient?
                
> Add ability to update the sharing policy of composite subsystems.
> -----------------------------------------------------------------
>
>                 Key: ARIES-956
>                 URL: https://issues.apache.org/jira/browse/ARIES-956
>             Project: Aries
>          Issue Type: New Feature
>          Components: Subsystem
>            Reporter: John Ross
>            Assignee: John Ross
>
> I`m looking to implement a "Shared Bundle Subsystem" which is basically a subsystem container for other subsystems. It looks like there was consideration for this scenario in the spec as there is talk of an application container in the section which discusses appDependencies. 
> I have created a subsystem of type composite to which I am attempting to install an application subsystem. The problem is that the dependencies for the application subsystem cannot be satisfied because the manifest of the composite does not import them. At the point that I install the composite I can't supply the imports because I don't yet know which applications (and therefore which dependencies) will be installed. 
> Ideally what I was hoping for was an ability to import all available packages into the composite from the parent (in this case the root subsystem). I have attempted various methods of achieving this , (e.g. Including an empty bundle in the composite which has a DynamicImport-Package: *) but nothing seems to work. 
> Can you think of a way of implementing this scenario in the existing Subsystem framework? It's a fundamental part of what we (used to) do with the old composite bundle framework code so I`m hoping we can find a solution! 

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira