October 2009 - jboss-osgi-issues - Jboss List Archives

[JBoss JIRA] Created: (JBOSGI-83) Add support for OSGi JMX Management (RFP-105)

by Thomas Diesler (JIRA)

Add support for OSGi JMX Management (RFP-105) --------------------------------------------- Key: JBOSGI-83 URL: https://jira.jboss.org/jira/browse/JBOSGI-83 Project: JBossOSGi Issue Type: Task Security Level: Public (Everyone can see) Components: Other Reporter: Thomas Diesler Add support for https://www.osgi.org/members/svn/documents/trunk/rfps/rfp-0105-JMXManagem... -- 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

1
9
0 / 0

[JBoss JIRA] Created: (JBOSGI-124) Lazily bundle should not define any eager managers

by Thomas Diesler (JIRA)

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) Reporter: Thomas Diesler Fix For: JBossOSGi 1.0.0 Beta4 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

14 years, 3 months

1
2
0 / 0

[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, 3 months

1
2
0 / 0

[JBoss JIRA] Created: (JBOSGI-122) A manager must be atomically activated

by Thomas Diesler (JIRA)

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) Reporter: Thomas Diesler Fix For: JBossOSGi 1.0.0 Beta4 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

14 years, 3 months

1
2
0 / 0

[JBoss JIRA] Created: (JBOSGI-121) Inlined beans always have prototype scope

by Thomas Diesler (JIRA)

Inlined beans always have prototype scope ----------------------------------------- Key: JBOSGI-121 URL: https://jira.jboss.org/jira/browse/JBOSGI-121 Project: JBoss OSGi Issue Type: Feature Request Security Level: Public (Everyone can see) Reporter: Thomas Diesler Fix For: JBossOSGi 1.0.x Inlined beans are further constrained to always have prototype scope. That is, every time they are asked to provide a component instance, they must return a different object. -- 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, 3 months

1
2
0 / 0

[JBoss JIRA] Created: (JBOSGI-118) Bean managers have a scope

by Thomas Diesler (JIRA)

Bean managers have a scope -------------------------- Key: JBOSGI-118 URL: https://jira.jboss.org/jira/browse/JBOSGI-118 Project: JBoss OSGi Issue Type: Feature Request Security Level: Public (Everyone can see) Reporter: Thomas Diesler Fix For: JBossOSGi 1.0.0 Beta4 Bean managers have a scope. This scope can be singleton, where the manager always provides the same object, or prototype, where the manager creates a new object for each request. -- 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, 3 months

1
2
0 / 0

[JBoss JIRA] Created: (JBOSGI-113) Add Blueprint binding validation

by Thomas Diesler (JIRA)

Add Blueprint binding validation --------------------------------- Key: JBOSGI-113 URL: https://jira.jboss.org/jira/browse/JBOSGI-113 Project: JBoss OSGi Issue Type: Task Security Level: Public (Everyone can see) Reporter: Thomas Diesler Fix For: JBossOSGi 1.0.0 Beta4 During development and binding of Java classes to schema components it's important to know whether the binding expressed with Java annotations match the existing XSD structure and components and if they don't what the binding inconsistencies are. In JBossXB-2.0.2.XX there is org.jboss.xb.util.SchemaBindingValidator interface that can be used to check that the XSD and SchemaBinding are consistent. http://www.jboss.org/community/wiki/Bindingvalidation -- 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, 3 months

1
2
0 / 0

[JBoss JIRA] Created: (JBOSGI-114) Abort initialization if Service not available

by Thomas Diesler (JIRA)

Abort initialization if Service not available --------------------------------------------- Key: JBOSGI-114 URL: https://jira.jboss.org/jira/browse/JBOSGI-114 Project: JBoss OSGi Issue Type: Feature Request Security Level: Public (Everyone can see) Reporter: Thomas Diesler Fix For: JBossOSGi 1.0.x All service reference managers track services in the service registry in order to determine if they are satisfied or not. If not, the Blueprint Container can optionally start a grace period. During the grace period, the Blueprint Container waits for all mandatory service reference managers to become satisfied. If this does not happen during the grace period, the Blueprint Container must abort the initialization. -- 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, 3 months

1
2
0 / 0

[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, 3 months

1
2
0 / 0

[JBoss JIRA] Created: (JBOSGI-117) Service reference managers provide proxies

by Thomas Diesler (JIRA)

Service reference managers provide proxies ------------------------------------------ Key: JBOSGI-117 URL: https://jira.jboss.org/jira/browse/JBOSGI-117 Project: JBoss OSGi Issue Type: Feature Request Security Level: Public (Everyone can see) Reporter: Thomas Diesler Fix For: JBossOSGi 1.0.x Service reference managers provide proxies to the actual service objects and fetch the service object lazily. They provide a constant reference that dampen the dynamics of the underlying service objects. -- 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, 3 months

1
2
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

jboss-osgi-issues October 2009