September 2010 - jboss-osgi-issues

[JBoss JIRA] Created: (JBOSGI-390) ModuleLoader does not implement BundleReference

by Thomas Diesler (JIRA)

ModuleLoader does not implement BundleReference ------------------------------------------------ Key: JBOSGI-390 URL: https://jira.jboss.org/browse/JBOSGI-390 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.x This is expected to work Class<?> clazz = bundle.loadClass(ObjectA.class.getName()); ClassLoader classLoader = clazz.getClassLoader(); assertTrue("Instance of BundleReference", classLoader instanceof BundleReference); Bundle result = FrameworkUtil.getBundle(clazz); assertEquals(bundle, result); The returned ClassLoader is however an instance of ModuleLoader -- 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, 8 months

1
0
0 / 0

[JBoss JIRA] Created: (JBOSGI-387) Potential problem with refreshing uninstalled bundles via JMX

by David Bosschaert (JIRA)

Potential problem with refreshing uninstalled bundles via JMX ------------------------------------------------------------- Key: JBOSGI-387 URL: https://jira.jboss.org/browse/JBOSGI-387 Project: JBoss OSGi Issue Type: Bug Security Level: Public (Everyone can see) Components: jboss-osgi-jmx Affects Versions: JBossOSGi 1.0.0 Beta8 Reporter: David Bosschaert Assignee: David Bosschaert Separated comment out of JBOSGI-336: There might be an issue with FrameworkMBean.refreshBundles(long[] bundleIds). The Aries implementation delegates to PackageAdmin.refreshPackages, for which it needs an Bundle[]. BundleContext.getBundle(long bundleId) would however return nulll for already uninstalled bundles. As a result it seems that you cannot refresh a bundle that is already uninstalled. -- 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, 8 months

2
5
0 / 0

[JBoss JIRA] Created: (JBOSGI-359) Comprehensive Bundle test coverage

by Thomas Diesler (JIRA)

Comprehensive Bundle test coverage ---------------------------------- Key: JBOSGI-359 URL: https://jira.jboss.org/browse/JBOSGI-359 Project: JBoss OSGi Issue Type: Task Security Level: Public (Everyone can see) Components: Core Framework Reporter: Thomas Diesler Fix For: JBossOSGi 1.0.0 Beta9 Provide comprehensive Bundle API test coverage -- 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, 8 months

2
11
0 / 0

[JBoss JIRA] Created: (JBOSGI-336) Add support for PackageAdmin.refreshPackages(Bundle[])

by Thomas Diesler (JIRA)

Add support for PackageAdmin.refreshPackages(Bundle[]) ------------------------------------------------------ Key: JBOSGI-336 URL: https://jira.jboss.org/browse/JBOSGI-336 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 -- 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, 8 months

2
12
0 / 0

[JBoss JIRA] Created: (JBOSGI-379) Implement Bundle.update()

by David Bosschaert (JIRA)

Implement Bundle.update() ------------------------- Key: JBOSGI-379 URL: https://jira.jboss.org/browse/JBOSGI-379 Project: JBoss OSGi Issue Type: Task Security Level: Public (Everyone can see) Reporter: David Bosschaert Assignee: David Bosschaert Fix For: JBossOSGi 1.0.0 Beta9 -- 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, 8 months

2
9
0 / 0

[JBoss JIRA] Created: (JBOSGI-386) Invoking Refresh Packages on the framework from Web Console causes issues

by David Bosschaert (JIRA)

Invoking Refresh Packages on the framework from Web Console causes issues ------------------------------------------------------------------------- Key: JBOSGI-386 URL: https://jira.jboss.org/browse/JBOSGI-386 Project: JBoss OSGi Issue Type: Feature Request Security Level: Public (Everyone can see) Components: jboss-osgi-jmx, jboss-osgi-webconsole Affects Versions: JBossOSGi 1.0.0 Beta8 Reporter: David Bosschaert Refreshing individual bundles from the web console works fine, but when invoking 'Refresh Packages' on the whole framework, a number of bundles cause issues. The first issue appears when we're trying to refresh EventAdmin: java.lang.IllegalStateException: Cannot remove [jbosgi."org.apache.felix.eventadmin".ManagedService.40] from: [jbosgi.jboss-osgi-http.ManagedService.14, jbosgi.jboss-osgi-webconsole.ManagedService.22] at org.jboss.osgi.container.plugin.internal.ServiceManagerPluginImpl.unregisterNameAssociation(ServiceManagerPluginImpl.java:393) at org.jboss.osgi.container.plugin.internal.ServiceManagerPluginImpl.unregisterService(ServiceManagerPluginImpl.java:428) at org.jboss.osgi.container.bundle.ServiceState.unregister(ServiceState.java:228) at org.jboss.osgi.container.bundle.HostBundle.stopInternal(HostBundle.java:304) at org.jboss.osgi.container.bundle.AbstractBundle.stop(AbstractBundle.java:494) at org.jboss.osgi.container.bundle.HostBundle.stop(HostBundle.java:249) at org.jboss.osgi.container.plugin.internal.PackageAdminPluginImpl$1.run(PackageAdminPluginImpl.java:279) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) at java.lang.Thread.run(Thread.java:619) Which is then followed by an issue around the JMXConnectorServer: [JMXConnectorService] Cannot stop JMXConnectorServer java.io.IOException: Cannot bind to URL: javax.naming.NoInitialContextException: Need to specify class name in environment or system property, or as an applet parameter, or in an application resource file: java.naming.factory.initial at javax.management.remote.rmi.RMIConnectorServer.newIOException(RMIConnectorServer.java:804) at javax.management.remote.rmi.RMIConnectorServer.stop(RMIConnectorServer.java:555) at org.jboss.osgi.jmx.internal.JMXConnectorService.stop(JMXConnectorService.java:90) at org.jboss.osgi.jmx.internal.JMXServiceActivator.stop(JMXServiceActivator.java:133) at org.jboss.osgi.container.bundle.HostBundle.stopInternal(HostBundle.java:292) at org.jboss.osgi.container.bundle.AbstractBundle.stop(AbstractBundle.java:494) at org.jboss.osgi.container.bundle.HostBundle.stop(HostBundle.java:249) at org.jboss.osgi.container.plugin.internal.PackageAdminPluginImpl$1.run(PackageAdminPluginImpl.java:279) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) at java.lang.Thread.run(Thread.java:619) Caused by: javax.naming.NoInitialContextException: Need to specify class name in environment or system property, or as an applet parameter, or in an application resource file: java.naming.factory.initial at javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:645) at javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:288) at javax.naming.InitialContext.getURLOrDefaultInitCtx(InitialContext.java:325) at javax.naming.InitialContext.unbind(InitialContext.java:416) at javax.management.remote.rmi.RMIConnectorServer.stop(RMIConnectorServer.java:547) ... 9 more Needless to say is that restarting these also causes issues since they weren't properly shut down. -- 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, 8 months

1
4
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

jboss-osgi-issues September 2010