aries-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "John Ross (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (ARIES-956) Add ability to update the sharing policy of composite subsystems.
Date Thu, 08 Nov 2012 00:46:12 GMT

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

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

I added initial support for this in http://svn.apache.org/viewvc?view=revision&revision=1406875.

The API now allows null, contrary to note (4) in my previous comment, in order to be backwards
compatible with the existing idirfinder URL functionality.

Modifying the current Region Digraph will fail if it was already modified by something else
after the copy was made. Synchronization is done on the BasicSubsystem class in order to avoid
conflicts from other subsystems whose requirements are also being updated. This will not avoid
conflicts from Region Digraph users outside of the subsystems implementation. It also introduces
the possibility of contention. Currently, only a single attempt is made. It might be worthwhile
to make this more robust by making up to a set number of attempts in case of failure. This
could also remove the need for synchronization.
                
> 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
>         Attachments: AriesSubsystem.java
>
>
> 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

Mime
View raw message