[JBoss JIRA] Created: (JBOSGI-120) All top level managers share a single namespace
by Thomas Diesler (JIRA)
All top level managers share a single namespace
-----------------------------------------------
Key: JBOSGI-120
URL: https://jira.jboss.org/jira/browse/JBOSGI-120
Project: JBoss OSGi
Issue Type: Feature Request
Security Level: Public (Everyone can see)
Reporter: Thomas Diesler
Fix For: JBossOSGi 1.0.0 Beta4
The Blueprint Container maintains a registry of managers by their id. These
are the managers that are called the top-level managers. Top level managers
are managers defined as child elements of the top XML blueprint element or
bean managers in the type-converters element. Their Metadata is registered
under their id (or calculated id) in the Blueprint Container. All top level
managers share a single namespace. That is, it is an error if the same id is
used multiple times or attempts to override the built-in environment 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
14 years, 2 months
[JBoss JIRA] Created: (JBOSGI-119) Blueprint Container service is unregistered
by Thomas Diesler (JIRA)
Blueprint Container service is unregistered
-------------------------------------------
Key: JBOSGI-119
URL: https://jira.jboss.org/jira/browse/JBOSGI-119
Project: JBoss OSGi
Issue Type: Feature Request
Security Level: Public (Everyone can see)
Reporter: Thomas Diesler
Fix For: JBossOSGi 1.0.0 Beta4
When the Blueprint Container must be destroyed because: the Blueprint
bundle has stopped, there is a failure, or the Blueprint extender is stopped,
then the Blueprint Container service is unregistered and all managers are
deactivated. This will unregister any services and disable listeners, which
release the component instances. Then all component instances are
destroyed in reverse dependency order. That is, a component instance is
destroyed when no other component instances depend on it.
--
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
14 years, 2 months
[JBoss JIRA] Created: (JBOSGI-115) service managers must have a Service Factory registered
by Thomas Diesler (JIRA)
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)
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
14 years, 2 months