July 2012 - jboss-osgi-issues - Jboss List Archives

[JBoss JIRA] (JBOSGI-580) Service not guranteed to be available on return of BundleContext.registerService(...)

by Thomas Diesler (JIRA)

Thomas Diesler created JBOSGI-580: ------------------------------------- Summary: Service not guranteed to be available on return of BundleContext.registerService(...) Key: JBOSGI-580 URL: https://issues.jboss.org/browse/JBOSGI-580 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.2.0 [registerService(String[], Object, Dictionary)|http://www.osgi.org/javadoc/r5/core/org/osgi/framework/Bundle...] [ServiceEvent.REGISTERED|http://www.osgi.org/javadoc/r5/core/org/osgi/fram...] -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 10 months

1
4
0 / 0

[JBoss JIRA] (JBOSGI-570) Verify that resolved packagers from fragments show up in PackageAdmin

by Thomas Diesler (JIRA)

11 years, 10 months

1
1
0 / 0

[JBoss JIRA] (JBOSGI-571) Package exported by fragment not visible through PackageAdmin.getExportedPackage()

by Thomas Diesler (JIRA)

11 years, 10 months

1
1
0 / 0

[JBoss JIRA] (JBOSGI-560) NullPointerException in AbstractBundleState#ensureResolved if debug logging is enabled

by Rico Neubauer (JIRA)

Rico Neubauer created JBOSGI-560: ------------------------------------ Summary: NullPointerException in AbstractBundleState#ensureResolved if debug logging is enabled Key: JBOSGI-560 URL: https://issues.jboss.org/browse/JBOSGI-560 Project: JBoss OSGi Issue Type: Bug Security Level: Public (Everyone can see) Reporter: Rico Neubauer Assignee: Thomas Diesler Occurs with JBoss 7.1.2.Final (EAP) running with jbosgi-framework 1.3.0.Final If debug logging is enabled, method org.jboss.osgi.framework.internal.AbstractBundleState#ensureResolved may throw a NullPointerException in case of "wiring" being null. See stacktrace below. Will add a pull request, doing the missing check for null. {noformat} Caused by: java.lang.NullPointerException at org.jboss.osgi.framework.internal.AbstractBundleState.ensureResolved(AbstractBundleState.java:558) at org.jboss.osgi.framework.internal.FallbackLoader.findInUnresolvedModules(FallbackLoader.java:230) at org.jboss.osgi.framework.internal.FallbackLoader.findModuleDynamically(FallbackLoader.java:156) at org.jboss.osgi.framework.internal.FallbackLoader.loadClassLocal(FallbackLoader.java:85) at org.jboss.modules.Module.loadModuleClass(Module.java:535) at org.jboss.modules.ModuleClassLoader.findClass(ModuleClassLoader.java:182) at org.jboss.modules.ConcurrentClassLoader.performLoadClassUnchecked(ConcurrentClassLoader.java:468) at org.jboss.modules.ConcurrentClassLoader.performLoadClassChecked(ConcurrentClassLoader.java:456) at org.jboss.modules.ConcurrentClassLoader.performLoadClassChecked(ConcurrentClassLoader.java:423) at org.jboss.modules.ConcurrentClassLoader.performLoadClass(ConcurrentClassLoader.java:398) at org.jboss.modules.ConcurrentClassLoader.loadClass(ConcurrentClassLoader.java:120) at java.lang.Class.forName0(Native Method) [rt.jar:1.6.0_31] at java.lang.Class.forName(Class.java:247) [rt.jar:1.6.0_31] at com.company.sth.ConnectionPool.<init>(ConnectionPool.java:131) {noformat} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 10 months

2
10
0 / 0

[JBoss JIRA] (JBOSGI-562) Unable to resolve HostBundleRevision

by Rico Neubauer (JIRA)

Rico Neubauer created JBOSGI-562: ------------------------------------ Summary: Unable to resolve HostBundleRevision Key: JBOSGI-562 URL: https://issues.jboss.org/browse/JBOSGI-562 Project: JBoss OSGi Issue Type: Bug Security Level: Public (Everyone can see) Components: Core Framework Reporter: Rico Neubauer Assignee: Thomas Diesler Occurs with JBoss 7.1.2.Final (EAP) running with jbosgi-resolver 2.1.0.Final There is no component for the resolver, so I add it under core-framework. Not sure about the conditions, but happens with dynamic class loading. org.jboss.osgi.resolver.felix.StatelessResolver.ResolveContextDelegate#matches(Requirement, Capability) does check the Requirement for being a HostedRequirement, but does not do the same for the Capability. As result, the cast of Capability to XCapability fails: {noformat} Caused by: java.lang.ClassCastException: org.jboss.osgi.resolver.spi.AbstractPackageRequirement cannot be cast to org.apache.felix.resolver.impl.HostedCapability at org.jboss.osgi.resolver.felix.StatelessResolver$ResolveContextDelegate.matches(StatelessResolver.java:144) at org.apache.felix.resolver.impl.Util.getSatisfyingCapability(Util.java:103) at org.apache.felix.resolver.impl.ResolverImpl.toStringBlame(ResolverImpl.java:1723) at org.apache.felix.resolver.impl.ResolverImpl.checkPackageSpaceConsistency(ResolverImpl.java:1050) at org.apache.felix.resolver.impl.ResolverImpl.checkPackageSpaceConsistency(ResolverImpl.java:1156) at org.apache.felix.resolver.impl.ResolverImpl.resolve(ResolverImpl.java:229) at org.apache.felix.resolver.impl.ResolverImpl.resolve(ResolverImpl.java:86) at org.jboss.osgi.resolver.felix.StatelessResolver.resolve(StatelessResolver.java:66) at org.jboss.osgi.framework.internal.ResolverPlugin.resolve(ResolverPlugin.java:116) at org.jboss.osgi.framework.internal.ResolverPlugin.resolveAndApply(ResolverPlugin.java:120) at org.jboss.osgi.framework.internal.AbstractBundleState.ensureResolved(AbstractBundleState.java:551) at org.jboss.osgi.framework.internal.FallbackLoader.findInUnresolvedModules(FallbackLoader.java:230) at org.jboss.osgi.framework.internal.FallbackLoader.findModuleDynamically(FallbackLoader.java:156) at org.jboss.osgi.framework.internal.FallbackLoader.loadClassLocal(FallbackLoader.java:85) at org.jboss.modules.Module.loadModuleClass(Module.java:535) at org.jboss.modules.ModuleClassLoader.findClass(ModuleClassLoader.java:182) at org.jboss.modules.ConcurrentClassLoader.performLoadClassUnchecked(ConcurrentClassLoader.java:468) at org.jboss.modules.ConcurrentClassLoader.performLoadClassChecked(ConcurrentClassLoader.java:456) at org.jboss.modules.ConcurrentClassLoader.performLoadClassChecked(ConcurrentClassLoader.java:423) at org.jboss.modules.ConcurrentClassLoader.performLoadClass(ConcurrentClassLoader.java:398) at org.jboss.modules.ConcurrentClassLoader.loadClass(ConcurrentClassLoader.java:120) at java.lang.Class.forName0(Native Method) at java.lang.Class.forName(Class.java:247) at com.company.sth.ConnectionPool.<init>(ConnectionPool.java:131) ... 95 more {noformat} Will attach a pull request, which fixes the problem. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 10 months

2
3
0 / 0

[JBoss JIRA] (JBOSGI-565) Attachment support leaks into public API

by Thomas Diesler (JIRA)

Thomas Diesler created JBOSGI-565: ------------------------------------- Summary: Attachment support leaks into public API Key: JBOSGI-565 URL: https://issues.jboss.org/browse/JBOSGI-565 Project: JBoss OSGi Issue Type: Bug Security Level: Public (Everyone can see) Components: Core Framework Reporter: Thomas Diesler Assignee: Thomas Diesler Various entities support attachments, which when visible through public API, is a security/consistency risk. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 10 months

1
4
0 / 0

[JBoss JIRA] (JBOSGI-554) Invalid recursive module creation triggered by bundle event

by Thomas Diesler (JIRA)

Thomas Diesler created JBOSGI-554: ------------------------------------- Summary: Invalid recursive module creation triggered by bundle event Key: JBOSGI-554 URL: https://issues.jboss.org/browse/JBOSGI-554 Project: JBoss OSGi Issue Type: Bug Security Level: Public (Everyone can see) Reporter: Thomas Diesler Assignee: Thomas Diesler {code} at org.jboss.as.osgi.service.ModuleLoaderIntegration.addModule(ModuleLoaderIntegration.java:128) at org.jboss.osgi.framework.internal.ModuleManagerPlugin.createHostModule(ModuleManagerPlugin.java:298) at org.jboss.osgi.framework.internal.ModuleManagerPlugin.addModule(ModuleManagerPlugin.java:196) at org.jboss.osgi.framework.internal.ResolverPlugin.addModules(ResolverPlugin.java:253) at org.jboss.osgi.framework.internal.ResolverPlugin.applyResolverResults(ResolverPlugin.java:201) at org.jboss.osgi.framework.internal.ResolverPlugin.resolveAndApply(ResolverPlugin.java:121) at org.jboss.osgi.framework.internal.AbstractBundleState.ensureResolved(AbstractBundleState.java:551) at org.jboss.osgi.framework.internal.HostBundleRevision.findEntries(HostBundleRevision.java:126) at org.jboss.osgi.framework.internal.AbstractBundleState.findEntries(AbstractBundleState.java:443) at org.eclipse.gemini.blueprint.extender.internal.support.NamespaceManager.maybeAddNamespaceHandlerFor(NamespaceManager.java:130) at org.eclipse.gemini.blueprint.extender.internal.activator.ContextLoaderListener.maybeAddNamespaceHandlerFor(ContextLoaderListener.java:462) at org.eclipse.gemini.blueprint.extender.internal.activator.ContextLoaderListener$NamespaceBundleLister.handleEvent(ContextLoaderListener.java:169) at org.eclipse.gemini.blueprint.extender.internal.activator.ContextLoaderListener$BaseListener.bundleChanged(ContextLoaderListener.java:137) at org.jboss.osgi.framework.internal.FrameworkEventsPlugin.fireBundleEvent(FrameworkEventsPlugin.java:372) at org.jboss.osgi.framework.internal.AbstractBundleState.fireBundleEvent(AbstractBundleState.java:198) at org.jboss.osgi.framework.internal.AbstractBundleState.changeState(AbstractBundleState.java:192) at org.jboss.osgi.framework.internal.AbstractBundleState.changeState(AbstractBundleState.java:174) at org.jboss.osgi.framework.internal.ResolverPlugin.setBundleToResolved(ResolverPlugin.java:277) at org.jboss.osgi.framework.internal.ResolverPlugin.applyResolverResults(ResolverPlugin.java:207) at org.jboss.osgi.framework.internal.ResolverPlugin.resolveAndApply(ResolverPlugin.java:121) at org.jboss.osgi.framework.internal.AbstractBundleState.ensureResolved(AbstractBundleState.java:551) at org.jboss.osgi.framework.internal.HostBundleState.startInternal(HostBundleState.java:232) at org.jboss.osgi.framework.internal.AbstractBundleState.start(AbstractBundleState.java:485) at org.jboss.as.osgi.management.BundleResourceHandler.handleOperation(BundleResourceHandler.java:145) at org.jboss.as.osgi.management.BundleResourceHandler.executeRuntimeStep(BundleResourceHandler.java:99) {code} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 10 months

1
2
0 / 0

[JBoss JIRA] (JBOSGI-524) Relicense repository code base to ASL2.0

by Thomas Diesler (JIRA)

Thomas Diesler created JBOSGI-524: ------------------------------------- Summary: Relicense repository code base to ASL2.0 Key: JBOSGI-524 URL: https://issues.jboss.org/browse/JBOSGI-524 Project: JBoss OSGi Issue Type: Task Security Level: Public (Everyone can see) Reporter: Thomas Diesler Assignee: Thomas Diesler This implementaiton is going to be the RI. We re-license to http://www.apache.org/licenses/LICENSE-2.0 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 10 months

1
8
0 / 0

[JBoss JIRA] (JBOSGI-583) Move JBOSGi downloads to jboss.org

by Thomas Diesler (JIRA)

Thomas Diesler created JBOSGI-583: ------------------------------------- Summary: Move JBOSGi downloads to jboss.org Key: JBOSGI-583 URL: https://issues.jboss.org/browse/JBOSGI-583 Project: JBoss OSGi Issue Type: Task Security Level: Public (Everyone can see) Components: Distribution Reporter: Thomas Diesler Assignee: Thomas Diesler Fix For: JBossOSGi 1.2.0 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 11 months

1
0
0 / 0

[JBoss JIRA] Created: (JBOSGI-499) Run OSGi CT with AS7

by David Bosschaert (JIRA)

Run OSGi CT with AS7 -------------------- Key: JBOSGI-499 URL: https://issues.jboss.org/browse/JBOSGI-499 Project: JBoss OSGi Issue Type: Task Security Level: Public (Everyone can see) Reporter: David Bosschaert Assignee: David Bosschaert The OSGi CT is currently run with the JBoss OSGi framework standalone. It should also be possible to run the CT with the AS7 integration. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 11 months

2
5
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

jboss-osgi-issues July 2012