February 2012 - jboss-osgi-issues

[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] (JBOSGI-518) NPE in ServiceState.ungetScopedValue()

by Thomas Diesler (JIRA)

Thomas Diesler created JBOSGI-518: ------------------------------------- Summary: NPE in ServiceState.ungetScopedValue() Key: JBOSGI-518 URL: https://issues.jboss.org/browse/JBOSGI-518 Project: JBoss OSGi Issue Type: Bug Security Level: Public (Everyone can see) Reporter: Thomas Diesler Assignee: Thomas Diesler Caused by: java.lang.NullPointerException at org.jboss.osgi.framework.internal.ServiceState.ungetScopedValue(ServiceState.java:192) -- 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

12 years, 3 months

1
3
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] (JBOSGI-516) Add default BundleManifestVersion to OSGiManifestBuilder

by Thomas Diesler (JIRA)

Thomas Diesler created JBOSGI-516: ------------------------------------- Summary: Add default BundleManifestVersion to OSGiManifestBuilder Key: JBOSGI-516 URL: https://issues.jboss.org/browse/JBOSGI-516 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.1 -- 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

12 years, 3 months

1
2
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] (JBOSGI-508) Declarative Services don't start if bundles are activated in different order

by Martin Ždila (JIRA)

Martin Ždila created JBOSGI-508: ----------------------------------- Summary: Declarative Services don't start if bundles are activated in different order Key: JBOSGI-508 URL: https://issues.jboss.org/browse/JBOSGI-508 Project: JBoss OSGi Issue Type: Bug Security Level: Public (Everyone can see) Components: Compendium Services Reporter: Martin Ždila Assignee: Thomas Diesler I am using JBoss AS 7.1CR1b. I have two bundles each of them having one Declarative Service (Component). Bundle1 has Service1 and Bundle1 has Service2. Service2 Component is "immediate" and also has reference to Service1. If I have both Bundle1 and Bundle2 in RESOLVED state and start them in order Bundle1, Bundle2, then both services are started (Service1=registered, Service2=unsatisfied) and my testcase prints: {noformat} 16:34:27,124 INFO [org.jboss.osgi.framework.internal.HostBundleState] (qtp1633087118-107) Bundle started: gofer-sandbox1:1.0.0 16:34:28,646 INFO [stdout] (qtp1633087118-110) activate 1 16:34:28,646 INFO [stdout] (qtp1633087118-110) activate 2 16:34:28,656 INFO [org.jboss.osgi.framework.internal.HostBundleState] (qtp1633087118-110) Bundle started: gofer-sandbox2:1.0.0 {noformat} But if the startup order is reverse (Bundle2, Bundle1) then none of the services starts and the components are in the state Service1=registered, Service2=unsatisfied and in the logs I see: {noformat} 16:13:11,162 INFO [org.jboss.osgi.framework.internal.HostBundleState] (qtp1633087118-112) Bundle started: gofer-sandbox2:1.0.0 16:13:14,633 WARN [org.jboss.osgi.framework.internal.ServiceState] (qtp1633087118-107) The service's classloader has no visibility of the requested class: com.mwaysolutions.gofer2.sandbox1.Service1 16:13:14,634 WARN [org.jboss.osgi.framework.internal.ServiceState] (qtp1633087118-107) The service's classloader has no visibility of the requested class: com.mwaysolutions.gofer2.sandbox1.Service1 16:13:14,635 INFO [org.jboss.osgi.framework.internal.HostBundleState] (qtp1633087118-107) Bundle started: gofer-sandbox1:1.0.0 {noformat} The testcase works correctly when using Apache Felix OSGi Framework with Apache Felix Declarative Services. I also think that the problem is deeper than in Declarative Services implementation. I am attaching the testcase. -- 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

12 years, 3 months

3
8
0 / 0

[JBoss JIRA] (JBOSGI-509) IllegalStateException when service is unregistered twice

by Thomas Diesler (JIRA)

Thomas Diesler created JBOSGI-509: ------------------------------------- Summary: IllegalStateException when service is unregistered twice Key: JBOSGI-509 URL: https://issues.jboss.org/browse/JBOSGI-509 Project: JBoss OSGi Issue Type: Task Security Level: Public (Everyone can see) Components: Core Framework Reporter: Thomas Diesler Assignee: Thomas Diesler Check whether this exception is required by spec/tck -- 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

12 years, 3 months

1
2
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] (JBOSGI-517) Add AS7 integration tests to examples

by Thomas Diesler (JIRA)

Thomas Diesler created JBOSGI-517: ------------------------------------- Summary: Add AS7 integration tests to examples Key: JBOSGI-517 URL: https://issues.jboss.org/browse/JBOSGI-517 Project: JBoss OSGi Issue Type: Task Security Level: Public (Everyone can see) Components: Distribution Reporter: Thomas Diesler Assignee: Thomas Diesler Fix For: JBossOSGi 1.0.1 -- 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

12 years, 3 months

1
1
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

jboss-osgi-issues February 2012