[jboss-osgi-issues] [JBoss JIRA] Resolved: (JBOSGI-122) A manager must be atomically activated

[Thomas Diesler (JIRA)]

     [ https://jira.jboss.org/jira/browse/JBOSGI-122?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Thomas Diesler resolved JBOSGI-122.
-----------------------------------

    Fix Version/s:     (was:  JBossOSGi 1.0.x)
       Resolution: Out of Date


Obsolete. this is now covered by the Apache Aries integration

> A manager must be atomically activated
> --------------------------------------
>
>                 Key: JBOSGI-122
>                 URL: https://jira.jboss.org/jira/browse/JBOSGI-122
>             Project: JBoss OSGi
>          Issue Type: Feature Request
>      Security Level: Public(Everyone can see) 
>          Components: jboss-osgi-blueprint
>            Reporter: Thomas Diesler
>
> A manager must be atomically activated when it has to provide its first component
> instance. During activation it can perform a manager specific initialization
> that will actually consume resources from the Blueprint bundle. This activation
> must be atomic. That is, if a manager is being activated then other
> threads must block until the activation is completed.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira