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

[JBoss JIRA] Created: (JBOSGI-91) Integrate trailblazer in hudson

by Thomas Diesler (JIRA)

Integrate trailblazer in hudson ------------------------------- Key: JBOSGI-91 URL: https://jira.jboss.org/jira/browse/JBOSGI-91 Project: JBossOSGi Issue Type: Task Security Level: Public (Everyone can see) Components: Documentation Reporter: Thomas Diesler Assignee: Thomas Diesler Fix For: JBossOSGi 1.0.0 Beta2 -- 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, 1 month

1
6
0 / 0

[JBoss JIRA] Created: (JBOSGI-85) Document Trailblazer Application

by Thomas Diesler (JIRA)

Document Trailblazer Application -------------------------------- Key: JBOSGI-85 URL: https://jira.jboss.org/jira/browse/JBOSGI-85 Project: JBossOSGi Issue Type: Task Security Level: Public (Everyone can see) Components: Documentation Reporter: Thomas Diesler Assignee: Thomas Diesler Fix For: JBossOSGi 1.0.0 Beta2 -- 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, 1 month

1
5
0 / 0

[JBoss JIRA] Created: (JBOSGI-126) Replace the SPI JMX functionality by RFC-139 API

by Thomas Diesler (JIRA)

Replace the SPI JMX functionality by RFC-139 API ------------------------------------------------- Key: JBOSGI-126 URL: https://jira.jboss.org/jira/browse/JBOSGI-126 Project: JBoss OSGi Issue Type: Feature Request Security Level: Public (Everyone can see) Reporter: Thomas Diesler Fix For: JBossOSGi 1.0.0 Beta4 -- 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, 4 months

1
8
0 / 0

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

1
2
0 / 0

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

by Thomas Diesler (JIRA)

Bean managers have a scope -------------------------- Key: JBOSGI-116 URL: https://jira.jboss.org/jira/browse/JBOSGI-116 Project: JBoss OSGi Issue Type: Feature Request Security Level: Public (Everyone can see) Reporter: Thomas Diesler 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, 4 months

1
2
0 / 0

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

1
2
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

jboss-osgi-issues July 2009