You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@aries.apache.org by "Alasdair Nottingham (Created) (JIRA)" <ji...@apache.org> on 2012/04/06 23:36:16 UTC
[jira] [Created] (ARIES-844) Ability to set the start level for a
composite bundle used with application isolation
Ability to set the start level for a composite bundle used with application isolation
-------------------------------------------------------------------------------------
Key: ARIES-844
URL: https://issues.apache.org/jira/browse/ARIES-844
Project: Aries
Issue Type: Improvement
Components: Application
Reporter: Alasdair Nottingham
Assignee: Alasdair Nottingham
In my runtime we make use of start level to orchestrate startup. I hit a live lock issue where the shared bundle framework was at the default start level (in this case 20) and I was trying to use it when it was at start level 18. I've worked around it in our code so we don't live lock, but I think it should be possible to influence the start level for the composite bundle.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (ARIES-844) Ability to set the start level for a
composite bundle used with application isolation
Posted by "Alasdair Nottingham (Updated) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/ARIES-844?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Alasdair Nottingham updated ARIES-844:
--------------------------------------
Attachment: ARIES-844-patch.txt
I've attached a patch for review. I feel a little conflicted by the setStartLevel on the FrameworkBundleConfiguration rather than putting it on the factory, but that keeps the factory simpler.
> Ability to set the start level for a composite bundle used with application isolation
> -------------------------------------------------------------------------------------
>
> Key: ARIES-844
> URL: https://issues.apache.org/jira/browse/ARIES-844
> Project: Aries
> Issue Type: Improvement
> Components: Application
> Reporter: Alasdair Nottingham
> Assignee: Alasdair Nottingham
> Attachments: ARIES-844-patch.txt
>
>
> In my runtime we make use of start level to orchestrate startup. I hit a live lock issue where the shared bundle framework was at the default start level (in this case 20) and I was trying to use it when it was at start level 18. I've worked around it in our code so we don't live lock, but I think it should be possible to influence the start level for the composite bundle.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira