February 2010 - jboss-osgi-issues

[JBoss JIRA] Assigned: (JBOSGI-267) Allow multiple bundles to change state at once

by Thomas Diesler (JIRA)

[ https://jira.jboss.org/jira/browse/JBOSGI-267?page=com.atlassian.jira.plu... ] Thomas Diesler reassigned JBOSGI-267: ------------------------------------- Assignee: Thomas Diesler (was: Ales Justin) > Allow multiple bundles to change state at once > ---------------------------------------------- > > Key: JBOSGI-267 > URL: https://jira.jboss.org/jira/browse/JBOSGI-267 > Project: JBoss OSGi > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Core Framework > Reporter: Thomas Diesler > Assignee: Thomas Diesler > Fix For: Framework 1.0.0 Alpha4 > > > Currently the BundleManager can only reslove bundles one-by-one > deployerClient.change(unit.getName(), DeploymentStages.CLASSLOADER); > deployerClient.checkComplete(unit.getName()); > bundleState.changeState(Bundle.RESOLVED); > this results in uglyness in PackageAdmin > int resolved = 1; > while (resolved > 0) > { > resolved = 0; > Iterator<OSGiBundleState> it = resolvableBundles.iterator(); > while (it.hasNext()) > { > OSGiBundleState bundleState = it.next(); > if (bundleManager.resolveBundle(bundleState, false)) > { > it.remove(); > resolved++; > } > } > } > PackageAdmin should be able to use an API that resolves multiple deployemnts at once. -- 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
0
0 / 0

[JBoss JIRA] Created: (JBOSGI-292) PackageAdmin cannot obtain classloading metadata

by Thomas Diesler (JIRA)

PackageAdmin cannot obtain classloading metadata ------------------------------------------------ Key: JBOSGI-292 URL: https://jira.jboss.org/jira/browse/JBOSGI-292 Project: JBoss OSGi Issue Type: Bug Security Level: Public (Everyone can see) Components: Core Framework Reporter: Thomas Diesler Assignee: Thomas Diesler Fix For: JBossOSGi 1.0.0 Beta7 Caused by: java.lang.IllegalStateException: Cannot obtain ClassLoadingMetaData at org.jboss.osgi.framework.packageadmin.PackageAdminImpl.getExportedPackages(PackageAdminImpl.java:149) at org.jboss.osgi.framework.packageadmin.PackageAdminImpl.getExportedPackages(PackageAdminImpl.java:176) at org.apache.aries.jmx.util.FrameworkUtils.getBundleImportedPackages(FrameworkUtils.java:265) -- 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-290) Use LifecycleInterceptor with Aries Blueprint

by Thomas Diesler (JIRA)

Use LifecycleInterceptor with Aries Blueprint --------------------------------------------- Key: JBOSGI-290 URL: https://jira.jboss.org/jira/browse/JBOSGI-290 Project: JBoss OSGi Issue Type: Task Security Level: Public (Everyone can see) Components: jboss-osgi-blueprint Reporter: Thomas Diesler Assignee: Thomas Diesler Fix For: JBossOSGi 1.0.0 Beta7 -- 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-289) Migrate all components to jboss-logging

by Thomas Diesler (JIRA)

Migrate all components to jboss-logging --------------------------------------- Key: JBOSGI-289 URL: https://jira.jboss.org/jira/browse/JBOSGI-289 Project: JBoss OSGi Issue Type: Task Security Level: Public (Everyone can see) Reporter: Thomas Diesler Assignee: Thomas Diesler Fix For: JBossOSGi 1.0.0 Beta7 -- 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
1
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-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-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-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-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 February 2010