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

[JBoss JIRA] Created: (JBOSGI-485) Blueprint bundle install

by Andreas Tauber (JIRA)

Blueprint bundle install ------------------------ Key: JBOSGI-485 URL: https://issues.jboss.org/browse/JBOSGI-485 Project: JBoss OSGi Issue Type: Bug Security Level: Public (Everyone can see) Components: jboss-osgi-blueprint Affects Versions: JBossOSGi 1.0.0 Reporter: Andreas Tauber Assignee: Thomas Diesler Installing blueprint bundles with multilevel service dependency which work fine on equinox/springDM and felix/aries. Receiving warning; The service's classloader has no visibility of the requested class XXX, though the class is exported in OSGI Manifest. After the warning the following stack trace appears: 20:56:45,939 WARN [FrameworkEventsPlugin] Framework WARNING org.osgi.framework.ServiceException: Cannot unget factory value at org.jboss.osgi.framework.internal.ServiceState.ungetScopedValue(ServiceState.java:195) at org.jboss.osgi.framework.internal.ServiceManagerPlugin.ungetService(ServiceManagerPlugin.java:428) at org.jboss.osgi.framework.internal.AbstractBundleContext.ungetService(AbstractBundleContext.java:360) at org.apache.aries.blueprint.container.ReferenceRecipe.bind(ReferenceRecipe.java:142) at org.apache.aries.blueprint.container.ReferenceRecipe.retrack(ReferenceRecipe.java:112) at org.apache.aries.blueprint.container.AbstractServiceReferenceRecipe.updateListeners(AbstractServiceReferenceRecipe.java:392) at org.apache.aries.blueprint.container.ReferenceRecipe.internalCreate(ReferenceRecipe.java:91) at org.apache.aries.blueprint.di.AbstractRecipe.create(AbstractRecipe.java:64) at org.apache.aries.blueprint.di.RefRecipe.internalCreate(RefRecipe.java:60) at org.apache.aries.blueprint.di.AbstractRecipe.create(AbstractRecipe.java:64) at org.apache.aries.blueprint.container.BeanRecipe.setProperty(BeanRecipe.java:771) at org.apache.aries.blueprint.container.BeanRecipe.setProperties(BeanRecipe.java:742) at org.apache.aries.blueprint.container.BeanRecipe.setProperties(BeanRecipe.java:723) at org.apache.aries.blueprint.container.BeanRecipe.internalCreate(BeanRecipe.java:689) at org.apache.aries.blueprint.di.AbstractRecipe.create(AbstractRecipe.java:64) at org.apache.aries.blueprint.container.BlueprintRepository.createInstances(BlueprintRepository.java:219) at org.apache.aries.blueprint.container.BlueprintRepository.createAll(BlueprintRepository.java:147) at org.apache.aries.blueprint.container.BlueprintContainerImpl.instantiateEagerComponents(BlueprintContainerImpl.java:624) at org.apache.aries.blueprint.container.BlueprintContainerImpl.doRun(BlueprintContainerImpl.java:315) at org.apache.aries.blueprint.container.BlueprintContainerImpl.run(BlueprintContainerImpl.java:213) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:441) at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303) at java.util.concurrent.FutureTask.run(FutureTask.java:138) at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.java:98) at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:206) 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:662) Caused by: java.lang.NullPointerException at org.jboss.osgi.framework.internal.ServiceState.ungetScopedValue(ServiceState.java:192) ... 27 more cause the bundles work fine, on the other two deployment enviroments something must be wrong with jboss osgi impl -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 2 months

3
11
0 / 0

[JBoss JIRA] Created: (JBOSGI-291) Allow wildcards in org.osgi.framework.system.packages.extra

by Thomas Diesler (JIRA)

Allow wildcards in org.osgi.framework.system.packages.extra ----------------------------------------------------------- Key: JBOSGI-291 URL: https://jira.jboss.org/jira/browse/JBOSGI-291 Project: JBoss OSGi Issue Type: Feature Request Security Level: Public (Everyone can see) Reporter: Thomas Diesler Fix For: Framework 1.0.x Currently we have  org.jboss.osgi.spi;version=1.0, org.jboss.osgi.spi.capability;version=1.0, org.jboss.osgi.spi.framework;version=1.0, org.jboss.osgi.spi.management;version=1.0, org.jboss.osgi.spi.service;version=1.0, org.jboss.osgi.spi.util;version=1.0, org.jboss.osgi.testing;version=1.0 It should be possible to define this as  org.jboss.osgi.spi*;version=1.0, org.jboss.osgi.testing;version=1.0 -- 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

12 years, 3 months

1
2
0 / 0

[JBoss JIRA] Created: (JBOSGI-467) Review concurrent access to collections

by Thomas Diesler (JIRA)

Review concurrent access to collections --------------------------------------- Key: JBOSGI-467 URL: https://issues.jboss.org/browse/JBOSGI-467 Project: JBoss OSGi Issue Type: Task Security Level: Public (Everyone can see) Reporter: Thomas Diesler Assignee: Thomas Diesler Fix For: JBossOSGi 1.0.1 -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 3 months

1
2
0 / 0

[JBoss JIRA] Created: (JBOSGI-457) ConcurrentModificationException in UserBundleState.hasActiveWires

by Stuart Douglas (JIRA)

ConcurrentModificationException in UserBundleState.hasActiveWires ----------------------------------------------------------------- Key: JBOSGI-457 URL: https://issues.jboss.org/browse/JBOSGI-457 Project: JBoss OSGi Issue Type: Bug Security Level: Public (Everyone can see) Reporter: Stuart Douglas Assignee: Thomas Diesler 10:36:30,347 WARN [org.jboss.msc.service.fail] MSC00004: Failure during stop of service jbosgi.bundle.9."org.apache.aries.jmx"."0.3.0".INSTALLED: java.util.ConcurrentModificationException at java.util.LinkedHashMap$LinkedHashIterator.nextEntry(LinkedHashMap.java:373) [:1.6.0_22] at java.util.LinkedHashMap$KeyIterator.next(LinkedHashMap.java:384) [:1.6.0_22] at java.util.Collections$UnmodifiableCollection$1.next(Collections.java:1010) [:1.6.0_22] at org.jboss.osgi.framework.internal.UserBundleState.hasActiveWires(UserBundleState.java:237) at org.jboss.osgi.framework.internal.BundleManager.uninstallBundle(BundleManager.java:462) at org.jboss.osgi.framework.internal.UserBundleInstalledService.stop(UserBundleInstalledService.java:88) at org.jboss.msc.service.ServiceControllerImpl$StopTask.run(ServiceControllerImpl.java:1779) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) [:1.6.0_22] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) [:1.6.0_22] at java.lang.Thread.run(Thread.java:680) [:1.6.0_22] -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 3 months

2
7
0 / 0

[JBoss JIRA] Created: (JBOSGI-460) Improve toString() for resolver objects

by Thomas Diesler (JIRA)

Improve toString() for resolver objects --------------------------------------- Key: JBOSGI-460 URL: https://issues.jboss.org/browse/JBOSGI-460 Project: JBoss OSGi Issue Type: Bug Security Level: Public (Everyone can see) Reporter: Thomas Diesler Assignee: Thomas Diesler Caused by: org.osgi.framework.BundleException: Cannot initialize XModule from: {Export-Package=[org.jboss.osgi.metadata.internal.AbstractPackageAttribute@24ebf068, org.jboss.osgi.metadata.internal.AbstractPackageAttribute@7df44ec7, org.jboss.osgi.metadata.internal.AbstractPackageAttribute@32602b6b, org.jboss.osgi.metadata.internal.AbstractPackageAttribute@47c297a3, org.jboss.osgi.metadata.internal.AbstractPackageAttribute@38717323, org.jboss.osgi.metadata.internal.AbstractPackageAttribute@203e1bc8, org.jboss.osgi.metadata.internal.AbstractPackageAttribute@4d91f801, org.jboss.osgi.metadata.internal.AbstractPackageAttribute@2a313170, org.jboss.osgi.metadata.internal.AbstractPackageAttribute@3a4c5b4, org.jboss.osgi.metadata.internal.AbstractPackageAttribute@36afae4a, org.jboss.osgi.metadata.internal.AbstractPackageAttribute@47db9852, org.jboss.osgi.metadata.internal.AbstractPackageAttribute@21ed5459, org.jboss.osgi.metadata.internal.AbstractPackageAttribute@643cb075, org.jboss.osgi.metadata.internal.AbstractPackageAttribute@4c6504bc, org.jboss.osgi.metadata.internal.AbstractPackageAttribute@7c19f9d2, org.jboss.osgi.metadata.internal.AbstractPackageAttribute@d6089a5, org.jboss.osgi.metadata.internal.AbstractPackageAttribute@3cecb67f, org.jboss.osgi.metadata.internal.AbstractPackageAttribute@58c16b18], Bundle-SymbolicName=[org.jboss.osgi.metadata.internal.AbstractParameterizedAttribute@25e222e], Bundle-Activator=org.jboss.arquillian.osgi.ArquillianBundleActivator, Bundle-Version=1.0.0.CR1-as734-SNAPSHOT} at org.jboss.osgi.resolver.spi.AbstractModuleBuilder.load(AbstractModuleBuilder.java:202) at org.jboss.osgi.resolver.spi.AbstractModuleBuilder.createModule(AbstractModuleBuilder.java:56) at org.jboss.osgi.framework.internal.UserBundleState.createResolverModule(UserBundleState.java:152) at org.jboss.osgi.framework.internal.UserBundleInstalledService.start(UserBundleInstalledService.java:62) ... 4 more Caused by: java.lang.NumberFormatException: For input string: "${version" at java.lang.NumberFormatException.forInputString(NumberFormatException.java:48) at java.lang.Integer.parseInt(Integer.java:449) at java.lang.Integer.parseInt(Integer.java:499) at org.osgi.framework.Version.<init>(Version.java:125) at org.osgi.framework.Version.parseVersion(Version.java:218) at org.jboss.osgi.resolver.spi.AbstractPackageCapability.<init>(AbstractPackageCapability.java:48) at org.jboss.osgi.resolver.spi.AbstractModuleBuilder.addPackageCapability(AbstractModuleBuilder.java:100) at org.jboss.osgi.resolver.spi.AbstractModuleBuilder.load(AbstractModuleBuilder.java:163) ... 7 more -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 3 months

1
4
0 / 0

[JBoss JIRA] Created: (JBOSGI-413) Xerces bundle defines invalid dependency on wutka.dtdparser

by Thomas Diesler (JIRA)

Xerces bundle defines invalid dependency on wutka.dtdparser ----------------------------------------------------------- Key: JBOSGI-413 URL: https://jira.jboss.org/browse/JBOSGI-413 Project: JBoss OSGi Issue Type: Bug Security Level: Public (Everyone can see) Reporter: Thomas Diesler Fix For: JBossOSGi 1.0.x Currently we need to exclude the dependency on wutka.dtdparser because it is not in the public jboss repository Builds with a clea mvn repo fail. Try a build after rm -rf ~/.m2/repository/wutka-dtdparser https://repository.jboss.org/nexus/content/groups/public-jboss/wutka-dtdp... -- 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

12 years, 3 months

1
4
0 / 0

[JBoss JIRA] Created: (JBOSGI-285) Add PaxWeb JSP support

by Thomas Diesler (JIRA)

Add PaxWeb JSP support ---------------------- Key: JBOSGI-285 URL: https://jira.jboss.org/jira/browse/JBOSGI-285 Project: JBoss OSGi Issue Type: Feature Request Security Level: Public (Everyone can see) Reporter: Thomas Diesler Fix For: JBossOSGi 1.0.0 Beta7 It seems that another jar is missing from distribution, the Pax Web Extender JSP, as the log message says: WARN [RegisterWebAppVisitorWC] Jsp support is not enabled. Is org.ops4j.pax.web.jsp bundle installed? Obviously not! So I downloaded the latest version (0.7.1) of Pax Web Extender JSP and successfully deployed it: INFO [BundleStartStopDeployer] Started: org.ops4j.pax.web.pax-web-extender-war [16] INFO [Activator] Pax Web started INFO [BundleStartStopDeployer] Started: org.ops4j.pax.web.pax-web-jetty-bundle [17] INFO [JettyServerImpl] Pax Web available at [0.0.0.0]:[8090] INFO [HttpServiceFactoryImpl] Binding bundle: [jboss-osgi-webconsole [12]] to http service INFO [BundleStartStopDeployer] Started: org.ops4j.pax.web.pax-web-jsp [18] But it doesn't seems to work because I always get the same WARN message above... suggestions? -- 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

12 years, 3 months

2
14
0 / 0

[JBoss JIRA] Created: (JBOSGI-480) Resolver Exception sometimes gets hidden by a subsequent NPE

by David Bosschaert (JIRA)

Resolver Exception sometimes gets hidden by a subsequent NPE ------------------------------------------------------------ Key: JBOSGI-480 URL: https://issues.jboss.org/browse/JBOSGI-480 Project: JBoss OSGi Issue Type: Bug Security Level: Public (Everyone can see) Reporter: David Bosschaert Assignee: David Bosschaert In some cases a resolver exception gets shadowed by a NPE that happens during the processing of the resolver exception, this means that the end user has no way of knowing why the resolution failed, he only sees the NPE. The offending code can be found in the FelixResolver class, line 117: XResolverException resex = new XResolverException(msg, exmod.getModule(), exreq); In some cases exmod is null which means that an NPE gets thrown and the resolution exception is lost. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 3 months

2
6
0 / 0

[JBoss JIRA] Created: (JBOSGI-466) Felix web console depends on start order

by David Bosschaert (JIRA)

Felix web console depends on start order ---------------------------------------- Key: JBOSGI-466 URL: https://issues.jboss.org/browse/JBOSGI-466 Project: JBoss OSGi Issue Type: Bug Security Level: Public (Everyone can see) Components: jboss-osgi-webconsole Affects Versions: JBossOSGi 1.0.0 Beta10 Reporter: David Bosschaert Assignee: Thomas Diesler The Felix web console only works when started after the webcontainer. See JBOSGI-464 -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 3 months

3
7
0 / 0

[JBoss JIRA] Created: (JBOSGI-322) [EOSGi] Integrate the OSGi Remote Services implementation from CXF

by David Bosschaert (JIRA)

[EOSGi] Integrate the OSGi Remote Services implementation from CXF ------------------------------------------------------------------ Key: JBOSGI-322 URL: https://jira.jboss.org/jira/browse/JBOSGI-322 Project: JBoss OSGi Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Compendium Services Reporter: David Bosschaert The Enterprise OSGi Spec describes OSGi Remote Services which is a way to Distribute OSGi Services. An implementation on top of Web Services and REST is available at the CXF Distributed OSGi project (http://cxf.apache.org/distributed-osgi.html). Integrating this in the JBoss OSGi distribution would provide it with support for this important OSGi spec. -- 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

12 years, 6 months

6
10
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

jboss-osgi-issues July 2011