[jboss-osgi-issues] [JBoss JIRA] Updated: (JBOSGI-115) service managers must have a Service Factory registered

[Thomas Diesler (JIRA)]

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

Thomas Diesler updated JBOSGI-115:
----------------------------------

    Fix Version/s:  JBossOSGi 1.0.x
                       (was: JBossOSGi 1.0.0 Beta4)


> service managers must have a Service Factory registered
> -------------------------------------------------------
>
>                 Key: JBOSGI-115
>                 URL: https://jira.jboss.org/jira/browse/JBOSGI-115
>             Project: JBoss OSGi
>          Issue Type: Feature Request
>      Security Level: Public(Everyone can see) 
>          Components: jboss-osgi-blueprint
>            Reporter: Thomas Diesler
>             Fix For:  JBossOSGi 1.0.x
>
>
> However, the activation needs a trigger to start. There are two triggers.
> • Service Request - All service managers must have a Service Factory registered
> with the OSGi service registry whenever that service manager is
> enabled, see Enabled on page 672.
> • Eager Managers - To kick start the application in the bundle, the Blueprint
> Container must ask all eager managers to provide a component
> instance, thereby activating these managers, see Eager Instantiation on
> page 651.

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