September 2011 - jboss-osgi-issues

[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, 2 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

[JBoss JIRA] Created: (JBOSGI-490) NPE in FelixResolver

by Thomas Diesler (JIRA)

NPE in FelixResolver -------------------- Key: JBOSGI-490 URL: https://issues.jboss.org/browse/JBOSGI-490 Project: JBoss OSGi Issue Type: Bug Security Level: Public (Everyone can see) Reporter: Thomas Diesler Assignee: Thomas Diesler geekonek says, I was getting random npe on org.jboss.osgi.resolver.felix.FelixResolver. I don't really have time to dig into this but for some bundles (fe com.springsource.com.sun.tools.xjc-2.2.0.jar) i got npe on FelixResolver.java:117; ex.getModule() returned null; There's quick fix on gh that solved this for me, but idk if i broken something else :) https://github.com/geekonek/jbosgi-resolver/commit/7dd6d6ef0ec385ed310276... -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 6 months

4
5
0 / 0

[JBoss JIRA] Created: (JBOSGI-486) Revisit system package and boot delegation

by Thomas Diesler (JIRA)

Revisit system package and boot delegation ------------------------------------------ Key: JBOSGI-486 URL: https://issues.jboss.org/browse/JBOSGI-486 Project: JBoss OSGi Issue Type: Bug Security Level: Public (Everyone can see) Components: Core Framework Reporter: Thomas Diesler Assignee: Thomas Diesler Fix For: Core Framework 1.0.1 Packages defined through FRAMEWORK_SYSTEM_PACKAGES end up being loaded from the system class loader. They should however be loaded from the system bundle. In AS7 this breaks modularity because some javax.* packages are defined in modules and should not be loaded from the system class loader. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 6 months

2
3
0 / 0

[JBoss JIRA] Created: (JBOSGI-483) Update framework to modules 1.0.1 or later

by Thomas Diesler (JIRA)

Update framework to modules 1.0.1 or later ------------------------------------------ Key: JBOSGI-483 URL: https://issues.jboss.org/browse/JBOSGI-483 Project: JBoss OSGi Issue Type: Task Security Level: Public (Everyone can see) Reporter: Thomas Diesler Assignee: Thomas Diesler Fix For: Core Framework 1.0.1 -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 6 months

2
7
0 / 0

[JBoss JIRA] Created: (JBOSGI-488) Replace jboss-osgi-common by jboss-osgi-logging in distro

by Thomas Diesler (JIRA)

Replace jboss-osgi-common by jboss-osgi-logging in distro --------------------------------------------------------- Key: JBOSGI-488 URL: https://issues.jboss.org/browse/JBOSGI-488 Project: JBoss OSGi Issue Type: Task Security Level: Public (Everyone can see) Reporter: Thomas Diesler Assignee: David Bosschaert 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, 7 months

2
4
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

jboss-osgi-issues September 2011