[jboss-osgi-issues] [JBoss JIRA] Resolved: (JBOSGI-124) Lazily bundle should not define any eager managers

[Thomas Diesler (JIRA)]

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

Thomas Diesler resolved JBOSGI-124.
-----------------------------------

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


Obsolete. this is now covered by the Apache Aries integration

> Lazily bundle should not define any eager managers
> --------------------------------------------------
>
>                 Key: JBOSGI-124
>                 URL: https://jira.jboss.org/jira/browse/JBOSGI-124
>             Project: JBoss OSGi
>          Issue Type: Feature Request
>      Security Level: Public(Everyone can see) 
>          Components: jboss-osgi-blueprint
>            Reporter: Thomas Diesler
>
> Eager managers are explicitly activated by asking them to provide a component
> instance after all other initialization is done. A bundle that wants to be
> lazily initialized should not define any eager managers.

-- 
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