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

[JBoss JIRA] Created: (JBOSGI-139) Implement system BundleContext.loadClass()

by Thomas Diesler (JIRA)

Implement system BundleContext.loadClass() ------------------------------------------ Key: JBOSGI-139 URL: https://jira.jboss.org/jira/browse/JBOSGI-139 Project: JBoss OSGi Issue Type: Sub-task Security Level: Public (Everyone can see) Components: Core Reporter: Thomas Diesler Priority: Critical Fix For: Framework 1.0.0 Alpha1 -- 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

13 years, 11 months

1
7
0 / 0

[JBoss JIRA] Created: (JBOSGI-332) Enhance the Auto Start Plugin to support specification of start level

by David Bosschaert (JIRA)

Enhance the Auto Start Plugin to support specification of start level --------------------------------------------------------------------- Key: JBOSGI-332 URL: https://jira.jboss.org/browse/JBOSGI-332 Project: JBoss OSGi Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Core Framework Affects Versions: JBossOSGi 1.0.0 Beta8 Reporter: David Bosschaert Assignee: David Bosschaert The Auto Start Plugin needs to be enhanced to support the specification of start levels in the JBOSGi configuration file. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 11 months

2
8
0 / 0

[JBoss JIRA] Created: (JBOSGI-344) When stopping the framework bundles need to be taken down in the correct startlevel order

by David Bosschaert (JIRA)

When stopping the framework bundles need to be taken down in the correct startlevel order ----------------------------------------------------------------------------------------- Key: JBOSGI-344 URL: https://jira.jboss.org/browse/JBOSGI-344 Project: JBoss OSGi Issue Type: Bug Security Level: Public (Everyone can see) Components: Core Framework Reporter: David Bosschaert Assignee: David Bosschaert When the framework is shutting down the bundles need to be stopped in the reverse start order. Currently the stopFramework() doesn't take the start levels into account yet. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 11 months

2
5
0 / 0

[JBoss JIRA] Created: (JBOSGI-352) Remove dependency on osgi deployers project

by Thomas Diesler (JIRA)

Remove dependency on osgi deployers project ------------------------------------------- Key: JBOSGI-352 URL: https://jira.jboss.org/browse/JBOSGI-352 Project: JBoss OSGi Issue Type: Task Security Level: Public (Everyone can see) Components: Core Framework Reporter: Thomas Diesler Assignee: Thomas Diesler Fix For: JBossOSGi 1.0.0 Beta8 With Felix and Equinox gone there is no need to maintain a project for framework independent deployers http://github.com/jbosgi/jbosgi-deployers -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 11 months

1
1
0 / 0

[JBoss JIRA] Created: (JBOSGI-278) Revisit ControllerContext handling

by Thomas Diesler (JIRA)

Revisit ControllerContext handling ---------------------------------- Key: JBOSGI-278 URL: https://jira.jboss.org/jira/browse/JBOSGI-278 Project: JBoss OSGi Issue Type: Sub-task Security Level: Public (Everyone can see) Reporter: Thomas Diesler Assignee: Ales Justin -- 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

13 years, 11 months

1
8
0 / 0

[JBoss JIRA] Created: (JBOSGI-301) Enable VFS3 leak detection in runtime and jbossas

by Thomas Diesler (JIRA)

Enable VFS3 leak detection in runtime and jbossas ------------------------------------------------- Key: JBOSGI-301 URL: https://jira.jboss.org/jira/browse/JBOSGI-301 Project: JBoss OSGi Issue Type: Task Security Level: Public (Everyone can see) Reporter: Thomas Diesler Fix For: JBossOSGi 1.0.0 Beta7 Code which does not properly cleanup a mount point can be detected by enabling leak detection. Leak detection can be enabled by setting the jboss.vfs.leakDebugging system property to true. -- 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

13 years, 11 months

1
5
0 / 0

[JBoss JIRA] Created: (JBOSGI-349) Remove Felix and Equinox from the Installer

by Thomas Diesler (JIRA)

Remove Felix and Equinox from the Installer -------------------------------------------- Key: JBOSGI-349 URL: https://jira.jboss.org/browse/JBOSGI-349 Project: JBoss OSGi Issue Type: Task Security Level: Public (Everyone can see) Components: IzPack Installer Reporter: Thomas Diesler Assignee: Thomas Diesler Fix For: JBossOSGi 1.0.0 Beta8 The feature set of this release now allows us to focus entirely on the JBoss Native OSGi framework -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 11 months

1
2
0 / 0

[JBoss JIRA] Created: (JBOSGI-94) Remove DeploymentProvidedDeploymentUnitFilter

by Thomas Diesler (JIRA)

Remove DeploymentProvidedDeploymentUnitFilter --------------------------------------------- Key: JBOSGI-94 URL: https://jira.jboss.org/jira/browse/JBOSGI-94 Project: JBoss OSGi Issue Type: Task Security Level: Public (Everyone can see) Components: Other Reporter: Thomas Diesler Fix For: JBossOSGi 1.0.x Remove this class when this functionallity is natively supported by all target containers -- 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

13 years, 11 months

1
2
0 / 0

[JBoss JIRA] Created: (JBOSGI-334) Fix Start Level Support from the webconsole

by David Bosschaert (JIRA)

Fix Start Level Support from the webconsole ------------------------------------------- Key: JBOSGI-334 URL: https://jira.jboss.org/browse/JBOSGI-334 Project: JBoss OSGi Issue Type: Bug Security Level: Public (Everyone can see) Components: jboss-osgi-webconsole Affects Versions: JBossOSGi 1.0.0 Beta8 Reporter: David Bosschaert Current this is broken. We need to properly support specifying bundle start levels from the web console. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 11 months

2
6
0 / 0

[JBoss JIRA] Created: (JBOSGI-348) EventAdmin unexpectedly unregistered in Runtime

by Thomas Diesler (JIRA)

EventAdmin unexpectedly unregistered in Runtime ----------------------------------------------- Key: JBOSGI-348 URL: https://jira.jboss.org/browse/JBOSGI-348 Project: JBoss OSGi Issue Type: Bug Security Level: Public (Everyone can see) Reporter: Thomas Diesler Assignee: Thomas Diesler Fix For: JBossOSGi 1.0.0 Beta8 The EventAdminTestCase.testEventHandler fails consistently in the Hudson remote Runtime test with java.lang.IllegalArgumentException: Null reference at org.jboss.osgi.framework.bundle.ServiceManagerPluginImpl.getService(ServiceManagerPluginImpl.java:195) at org.jboss.osgi.framework.bundle.AbstractBundleState.getService(AbstractBundleState.java:521) at org.jboss.osgi.framework.bundle.OSGiBundleContextWrapper.getService(OSGiBundleContextWrapper.java:145) at org.jboss.test.osgi.example.event.EventAdminTestCase.testEventHandler(EventAdminTestCase.java:106) The reason is that the EventAdmin service is not registered. When I enable TRACE logging I see [tdiesler@tdbell jbosgi]$ cat ~/Desktop/server.log | grep org.osgi.service.event.EventAdmin | grep REGISTER 2010-06-18 10:44:04,991 DEBUG [org.jboss.osgi.framework.plugins.internal.FrameworkEventsPluginImpl] Service REGISTERED: Service{id=85,classes=[org.osgi.service.event.EventAdmin]} 2010-06-18 10:44:05,107 DEBUG [org.jboss.osgi.framework.plugins.internal.FrameworkEventsPluginImpl] Service UNREGISTERING: Service{id=85,classes=[org.osgi.service.event.EventAdmin]} 2010-06-18 10:45:05,221 DEBUG [org.jboss.osgi.framework.plugins.internal.FrameworkEventsPluginImpl] Service REGISTERED: Service{id=112,classes=[org.osgi.service.event.EventAdmin]} [tdiesler@tdbell jbosgi]$ cat ~/Desktop/server.log | grep getServiceReference | grep org.osgi.service.event.EventAdmin 2010-06-18 10:44:04,264 TRACE [org.jboss.osgi.framework.bundle.ServiceManagerPluginImpl] getServiceReferences(Bundle{jboss-osgi-blueprint-1.0.0.Beta2},org.osgi.service.event.EventAdmin,null,true) 2010-06-18 10:44:41,167 TRACE [org.jboss.osgi.framework.bundle.ServiceManagerPluginImpl] getServiceReferences(Bundle{system.bundle-0.0.0},org.osgi.service.event.EventAdmin,null,true) 2010-06-18 10:44:41,852 TRACE [org.jboss.osgi.framework.bundle.ServiceManagerPluginImpl] getServiceReferences(Bundle{example-event-0.0.0},org.osgi.service.event.EventAdmin,null,true) In the log I also see 2010-06-18 10:44:05,107 DEBUG [org.jboss.osgi.framework.plugins.internal.FrameworkEventsPluginImpl] Service UNREGISTERING: Service{id=85,classes=[org.osgi.service.event.EventAdmin]} 2010-06-18 10:44:05,108 TRACE [org.jboss.osgi.framework.bundle.ServiceManagerPluginImpl] getServiceReferences(Bundle{org.apache.felix.eventadmin-1.2.2},org.osgi.framework.hooks.service.FindHook,null,true) 2010-06-18 10:44:05,108 TRACE [org.jboss.osgi.framework.bundle.ServiceManagerPluginImpl] Considered contexts: : 108 2010-06-18 10:44:05,107 DEBUG [org.apache.felix.configadmin] Running task ManagedService Update: pid=org.apache.felix.eventadmin.impl.EventAdmin 2010-06-18 10:44:05,113 TRACE [org.jboss.osgi.framework.bundle.ServiceManagerPluginImpl] Remaining contexts: : 0 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 11 months

1
7
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

jboss-osgi-issues June 2010