January 2010 - jboss-osgi-issues - Jboss List Archives

[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

15 years, 9 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

15 years, 9 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

15 years, 9 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

15 years, 9 months

1
2
0 / 0

[JBoss JIRA] Created: (JBOSGI-123) A bean manager can only be eager if it has singleton scope

by Thomas Diesler (JIRA)

A bean manager can only be eager if it has singleton scope ---------------------------------------------------------- Key: JBOSGI-123 URL: https://jira.jboss.org/jira/browse/JBOSGI-123 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 can force the activation of the application in the Blueprint bundle with eager managers. An eager manager is a manager that has the activation set to eager. A bean manager can only be eager if it has singleton scope -- 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

15 years, 9 months

1
2
0 / 0

[JBoss JIRA] Created: (JBOSGI-281) Release JBoss OSGi 1.0.0.Beta6

by Thomas Diesler (JIRA)

Release JBoss OSGi 1.0.0.Beta6 ------------------------------ Key: JBOSGI-281 URL: https://jira.jboss.org/jira/browse/JBOSGI-281 Project: JBoss OSGi Issue Type: Task Security Level: Public (Everyone can see) Components: Documentation Reporter: Thomas Diesler Assignee: Thomas Diesler Fix For: JBossOSGi 1.0.0 Beta5 The release procedure is documented here http://www.jboss.org/community/wiki/ReleaseProcedure -- 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

15 years, 9 months

1
2
0 / 0

[JBoss JIRA] Created: (JBOSGI-265) Update to jboss-osgi-framework-1.0.0.Alpha3

by Thomas Diesler (JIRA)

Update to jboss-osgi-framework-1.0.0.Alpha3 ------------------------------------------- Key: JBOSGI-265 URL: https://jira.jboss.org/jira/browse/JBOSGI-265 Project: JBoss OSGi Issue Type: Task Security Level: Public (Everyone can see) Components: jboss-osgi-spi Reporter: Thomas Diesler Assignee: Thomas Diesler Fix For: JBossOSGi 1.0.0 Beta5 -- 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

15 years, 9 months

1
2
0 / 0

[JBoss JIRA] Created: (JBOSGI-145) JAXB classes are loaded from the system classpath

by Thomas Diesler (JIRA)

JAXB classes are loaded from the system classpath ------------------------------------------------- Key: JBOSGI-145 URL: https://jira.jboss.org/jira/browse/JBOSGI-145 Project: JBoss OSGi Issue Type: Bug Security Level: Public (Everyone can see) Components: Core Reporter: Thomas Diesler Fix For: Framework 1.0.0 Alpha1 [tdiesler@tdvaio example]$ mvn -Dframework=jbossmc -Dtest=JAXBTestCase test Running org.jboss.test.osgi.example.xml.jaxb.JAXBTestCase Tests run: 1, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 5.721 sec Caused by: javax.xml.bind.JAXBException: Provider com.sun.xml.internal.bind.v2.ContextFactory not found - with linked exception: [java.lang.ClassNotFoundException: com.sun.xml.internal.bind.v2.ContextFactory from OSGiBundleClassLoader@14596d5{VFSClassLoaderPolicy@1b19753{name=vfszip:/home/tdiesler/svn/jboss-osgi/trunk/testsuite/example/target/test-libs/example-xml-jaxb.jar/ domain=ClassLoaderDomain@74cb02{name=DefaultDomain parentPolicy=(before=[javax.imageio, javax.imageio.stream, javax.management, javax.management.remote, javax.naming, javax.naming.event, javax.naming.spi, javax.net, javax.net.ssl, javax.xml.datatype, javax.xml.namespace, javax.xml.parsers, javax.xml.transform, javax.xml.transform.dom, javax.xml.transform.sax, javax.xml.transform.stream, javax.xml.validation, org.jboss.logging, org.jboss.osgi.spi.capability, org.jboss.osgi.spi.framework, org.jboss.osgi.spi.logging, org.jboss.osgi.spi.management, org.jboss.osgi.spi.service, org.jboss.osgi.spi.testing, org.jboss.osgi.spi.util, org.osgi.framework, org.osgi.framework.launch, org.osgi.service.packageadmin, org.osgi.service.startlevel, org.osgi.util.tracker, org.w3c.dom, org.w3c.dom.events, org.w3c.dom.ls, org.w3c.dom.ranges, org.w3c.dom.traversal, org.w3c.dom.views, org.xml.sax, org.xml.sax.ext, org.xml.sax.helpers] <INCLUDE_JAVA> after=<NOTHING>) parent=sun.misc.Launcher$AppClassLoader@1a7bf11} roots=[DelegatingHandler@4574743[path= context=file:/home/tdiesler/svn/jboss-osgi/trunk/testsuite/example/target/test-libs/example-xml-jaxb.jar real=vfszip:/home/tdiesler/svn/jboss-osgi/trunk/testsuite/example/target/test-libs/example-xml-jaxb.jar]] delegates=[FilteredDelegateLoader@dd5681{delegate=VFSClassLoaderPolicy@1453d72{vfszip:/home/tdiesler/svn/jboss-osgi/trunk/testsuite/example/target/test-libs/bundles/jboss-osgi-jaxb.jar/}}, FilteredDelegateLoader@15a4523{delegate=VFSClassLoaderPolicy@1453d72{vfszip:/home/tdiesler/svn/jboss-osgi/trunk/testsuite/example/target/test-libs/bundles/jboss-osgi-jaxb.jar/}}, FilteredDelegateLoader@171120a{delegate=VFSClassLoaderPolicy@1453d72{vfszip:/home/tdiesler/svn/jboss-osgi/trunk/testsuite/example/target/test-libs/bundles/jboss-osgi-jaxb.jar/}}, FilteredDelegateLoader@57828d{delegate=VFSClassLoaderPolicy@6147d9{vfszip:/home/tdiesler/svn/jboss-osgi/trunk/testsuite/example/target/test-libs/bundles/jboss-osgi-husky.jar/}}, FilteredDelegateLoader@13c296b{delegate=VFSClassLoaderPolicy@6147d9{vfszip:/home/tdiesler/svn/jboss-osgi/trunk/testsuite/example/target/test-libs/bundles/jboss-osgi-husky.jar/}}, FilteredDelegateLoader@c360a5{delegate=VFSClassLoaderPolicy@1453d72{vfszip:/home/tdiesler/svn/jboss-osgi/trunk/testsuite/example/target/test-libs/bundles/jboss-osgi-jaxb.jar/}}, FilteredDelegateLoader@fe2558{delegate=VFSClassLoaderPolicy@6147d9{vfszip:/home/tdiesler/svn/jboss-osgi/trunk/testsuite/example/target/test-libs/bundles/jboss-osgi-husky.jar/}}] exported=[org.jboss.test.osgi.example.xml.jaxb]}}] at javax.xml.bind.ContextFinder.newInstance(ContextFinder.java:147) at javax.xml.bind.ContextFinder.find(ContextFinder.java:290) at javax.xml.bind.JAXBContext.newInstance(JAXBContext.java:372) at org.jboss.osgi.jaxb.internal.JAXBServiceImpl.newJAXBContext(JAXBServiceImpl.java:58) at org.jboss.osgi.jaxb.internal.JAXBServiceImpl.newJAXBContext(JAXBServiceImpl.java:52) at org.jboss.test.osgi.example.xml.jaxb.JAXBTestCase.getJAXBContext(JAXBTestCase.java:119) at org.jboss.test.osgi.example.xml.jaxb.JAXBTestCase.testUnmarshaller(JAXBTestCase.java:97) -- 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

15 years, 9 months

1
4
0 / 0

[JBoss JIRA] Created: (JBOSGI-279) Update to jboss-cl-2.2.x stable release

by Thomas Diesler (JIRA)

Update to jboss-cl-2.2.x stable release --------------------------------------- Key: JBOSGI-279 URL: https://jira.jboss.org/jira/browse/JBOSGI-279 Project: JBoss OSGi Issue Type: Task Security Level: Public (Everyone can see) Components: Core Framework Reporter: Thomas Diesler Assignee: Ales Justin Fix For: Framework 1.0.0 Alpha3 The kernel need to be released and included in framework so we can ship it as part of osgi Beta6 (1-Feb-2010) -- 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

15 years, 9 months

2
14
0 / 0

[JBoss JIRA] Created: (JBOSGI-210) Bundle is only installed but not started.

by Csaba Szucs (JIRA)

Bundle is only installed but not started. ----------------------------------------- Key: JBOSGI-210 URL: https://jira.jboss.org/jira/browse/JBOSGI-210 Project: JBoss OSGi Issue Type: Bug Security Level: Public (Everyone can see) Components: Integration (Equinox) Affects Versions: JBossOSGi 1.0.0 Beta4 Environment: OS: WinXP SP3 & CygWin V1.7 /run.sh had to be changed to work: JAVA_OPTS must be set AFTER all cygpath commands/ Reporter: Csaba Szucs My sample hot-deployed bundle is only installed but not started by the framework. This same bundle is also started within JBoss OSGi with Apache Felix integration. My sample bundle was created by Eclipse V3.5 as an Equinox plug-in and contains an Activator class only with code to log the bundle's lifecycle events. -- 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

15 years, 9 months

2
11
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

jboss-osgi-issues January 2010