June 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

15 years, 6 months

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

15 years, 6 months

1
5
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

15 years, 8 months

1
9
0 / 0

[JBoss JIRA] Created: (JBOSGI-99) No explicit control over bundle.start()

by Thomas Diesler (JIRA)

No explicit control over bundle.start() --------------------------------------- Key: JBOSGI-99 URL: https://jira.jboss.org/jira/browse/JBOSGI-99 Project: JBoss OSGi Issue Type: Bug Security Level: Public (Everyone can see) Components: Runtime Reporter: Thomas Diesler Fix For: JBossOSGi 1.0.0 Beta3 The BundleStartStopDeployer always tries to resolve a bundle, which prevents test cases to only install a bundle -- 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, 12 months

1
10
0 / 0

[JBoss JIRA] Created: (JBOSGI-74) Provide and use remoting bundles

by Thomas Diesler (JIRA)

Provide and use remoting bundles -------------------------------- Key: JBOSGI-74 URL: https://jira.jboss.org/jira/browse/JBOSGI-74 Project: JBossOSGi Issue Type: Task Security Level: Public (Everyone can see) Components: Other Reporter: Thomas Diesler Assignee: Thomas Diesler Fix For: JBossOSGi 1.0.0 Beta2 Provide and use remoting bundles instead of including them into the jboss-osgi-xyz bundles -- 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

16 years

2
7
0 / 0

[JBoss JIRA] Created: (JBOSGI-78) ResourceNotFoundException too verbose

by Thomas Diesler (JIRA)

ResourceNotFoundException too verbose ------------------------------------- Key: JBOSGI-78 URL: https://jira.jboss.org/jira/browse/JBOSGI-78 Project: JBossOSGi Issue Type: Bug Security Level: Public (Everyone can see) Components: Core Affects Versions: JBossOSGi 1.0.0 Beta1 Environment: https://issues.apache.org/jira/browse/FELIX-1124 Reporter: Thomas Diesler Assignee: Thomas Diesler -- 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

16 years, 1 month

1
4
0 / 0

[JBoss JIRA] Created: (JBOSGI-80) Add support for Framework Launching (RFC-132)

by Thomas Diesler (JIRA)

Add support for Framework Launching (RFC-132) --------------------------------------------- Key: JBOSGI-80 URL: https://jira.jboss.org/jira/browse/JBOSGI-80 Project: JBossOSGi Issue Type: Task Security Level: Public (Everyone can see) Components: Other 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

16 years, 1 month

1
4
0 / 0

[JBoss JIRA] Created: (JBOSGI-56) Investigate RFC-139 for JMX Control of OSGi

by Thomas Diesler (JIRA)

Investigate RFC-139 for JMX Control of OSGi ------------------------------------------- Key: JBOSGI-56 URL: https://jira.jboss.org/jira/browse/JBOSGI-56 Project: JBossOSGi Issue Type: Task Security Level: Public (Everyone can see) Components: Framework Reporter: Thomas Diesler Fix For: JBossOSGi 1.0.x Investigate management and control (install/deploy, uninstall/undeploy, start, stop, etc.) to be compatible with RFC-139 (JMX Control of OSGi) -- 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

16 years, 3 months

1
2
0 / 0

[JBoss JIRA] Created: (JBOSGI-73) Prototype of Blueprint Service

by Thomas Diesler (JIRA)

Prototype of Blueprint Service ------------------------------ Key: JBOSGI-73 URL: https://jira.jboss.org/jira/browse/JBOSGI-73 Project: JBossOSGi Issue Type: Task Security Level: Public (Everyone can see) Reporter: Thomas Diesler Assignee: Thomas Diesler Fix For: JBossOSGi 1.0.0 Beta2 Provide a prototype of the Blueprint Service based on JBossMC -- 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

16 years, 3 months

1
5
0 / 0

[JBoss JIRA] Created: (JBOSGI-92) XMLParserActivator in compendium cantot load SAXParserFactory

by Thomas Diesler (JIRA)

XMLParserActivator in compendium cantot load SAXParserFactory ------------------------------------------------------------- Key: JBOSGI-92 URL: https://jira.jboss.org/jira/browse/JBOSGI-92 Project: JBossOSGi Issue Type: Bug Security Level: Public (Everyone can see) Components: Compendium Reporter: Thomas Diesler Fix For: Continuing The XercesParserActivator fails with Caused by: javax.xml.parsers.FactoryConfigurationError: java.lang.ClassNotFoundException: *** Class 'org.apache.xerces.jaxp.SAXParserFactoryImpl' was not found because bundle 1 does not import 'org.apache.xerces.jaxp' even though bundle 4 does export it. Additionally, the class is also available from the system class loader. There are two fixes: 1) Add an import for 'org.apache.xerces.jaxp' to bundle 1; imports are necessary for each class directly touched by bundle code or indirectly touched, such as super classes if their methods are used. 2) Add package 'org.apache.xerces.jaxp' to the 'org.osgi.framework.bootdelegation' property; a library or VM bug can cause classes to be loaded by the wrong class loader. The first approach is preferable for preserving modularity. *** at org.osgi.util.xml.XMLParserActivator.getFactory(XMLParserActivator.java:459) at org.osgi.util.xml.XMLParserActivator.registerSAXParsers(XMLParserActivator.java:237) at org.osgi.util.xml.XMLParserActivator.start(XMLParserActivator.java:146) at org.jboss.osgi.apache.xerces.internal.XercesParserActivator.start(XercesParserActivator.java:50) at org.apache.felix.framework.util.SecureAction.startActivator(SecureAction.java:589) at org.apache.felix.framework.Felix.startBundle(Felix.java:1458) which is caused by Class.forName(parserFactoryClassName).newInstance() in the compendium jar -- 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

16 years, 3 months

1
6
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

jboss-osgi-issues June 2009