[
https://jira.jboss.org/jira/browse/JBOSGI-120?page=com.atlassian.jira.plu...
]
Thomas Diesler resolved JBOSGI-120.
-----------------------------------
Fix Version/s: (was: JBossOSGi 1.0.x)
Resolution: Out of Date
Obsolete. this is now covered by the Apache Aries integration
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)
Components: jboss-osgi-blueprint
Reporter: Thomas Diesler
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