aries-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Tuomas Kiviaho (JIRA)" <>
Subject [jira] [Created] (ARIES-913) Deterministic handling order of application context bundles
Date Fri, 31 Aug 2012 09:18:07 GMT
Tuomas Kiviaho created ARIES-913:

             Summary: Deterministic handling order of application context bundles
                 Key: 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:

View raw message