You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@aries.apache.org by "Tuomas Kiviaho (JIRA)" <ji...@apache.org> on 2012/08/31 11:18:07 UTC
[jira] [Created] (ARIES-913) Deterministic handling order of
application context bundles
Tuomas Kiviaho created ARIES-913:
------------------------------------
Summary: Deterministic handling order of application context bundles
Key: ARIES-913
URL: https://issues.apache.org/jira/browse/ARIES-913
Project: Aries
Issue Type: Improvement
Components: Application
Reporter: Tuomas Kiviaho
Currently ApplicationManagerImpl uses hash sets/maps to preserve and provide bundles which effectively loses the order in which they were originally described in APPLICATION.MF.
The order is also important in following scenario where several bundles override stdout one after the other.
app context start
start gogo # Preserves orginal state of system out
start sysout-over-slf4j # Preserves gogo's system out
app context stop
stop gogo # Reverts system out back to original state
stop sysout-over-slf4j # Reverts system out back to gogo's system out
Here the stdout is left pointing into already stopped bundle causing all kind of problems. The situation can be improved by applying uninstall and stop in reverse order compared to install and start which guarantees that at least behaviour of an individual application context is consistent.
--
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