February 2012 - jboss-osgi-issues

[JBoss JIRA] (JBOSGI-515) Integrate latest PaxHttp and PaxWeb directly

by Thomas Diesler (JIRA)

Thomas Diesler created JBOSGI-515: ------------------------------------- Summary: Integrate latest PaxHttp and PaxWeb directly Key: JBOSGI-515 URL: https://issues.jboss.org/browse/JBOSGI-515 Project: JBoss OSGi Issue Type: Task Security Level: Public (Everyone can see) Components: Compendium Services Reporter: Thomas Diesler Assignee: Thomas Diesler Fix For: JBossOSGi 1.0.1 As of this release we integrate 3rd party bundles directly -- 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, 2 months

1
5
0 / 0

[JBoss JIRA] (JBOSGI-513) Deprecate jbosgi-blueprint. Use latest Aries Blueprint directly

by Thomas Diesler (JIRA)

Thomas Diesler created JBOSGI-513: ------------------------------------- Summary: Deprecate jbosgi-blueprint. Use latest Aries Blueprint directly Key: JBOSGI-513 URL: https://issues.jboss.org/browse/JBOSGI-513 Project: JBoss OSGi Issue Type: Task Security Level: Public (Everyone can see) Components: Compendium Services Reporter: Thomas Diesler Assignee: Thomas Diesler Fix For: JBossOSGi 1.0.1 As of this release we integrate 3rd party bundles directly -- 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, 2 months

1
5
0 / 0

[JBoss JIRA] (JBOSGI-514) Integrate latest Aries JMX directly

by Thomas Diesler (JIRA)

Thomas Diesler created JBOSGI-514: ------------------------------------- Summary: Integrate latest Aries JMX directly Key: JBOSGI-514 URL: https://issues.jboss.org/browse/JBOSGI-514 Project: JBoss OSGi Issue Type: Task Security Level: Public (Everyone can see) Components: Compendium Services Reporter: Thomas Diesler Assignee: Thomas Diesler Fix For: JBossOSGi 1.0.1 As of this release we integrate 3rd party bundles directly -- 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, 2 months

1
3
0 / 0

[JBoss JIRA] (JBOSGI-510) StartLevelIntegrationTestCase fails on jdk1.7

by Thomas Diesler (JIRA)

Thomas Diesler created JBOSGI-510: ------------------------------------- Summary: StartLevelIntegrationTestCase fails on jdk1.7 Key: JBOSGI-510 URL: https://issues.jboss.org/browse/JBOSGI-510 Project: JBoss OSGi Issue Type: Bug Security Level: Public (Everyone can see) Components: Core Framework Reporter: Thomas Diesler Failed tests: testOrderedStop(org.jboss.test.osgi.framework.startlevel.StartLevelIntegrationTestCase): expected:<start1st[]art3start2stop2stop3...> but was:<start1st[op1start1stop1start1st]art3start2stop2stop3...> -- 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, 2 months

2
7
0 / 0

[JBoss JIRA] Created: (JBOSGI-489) Comprehensive coverage of AS7 / OSGi integration in user guide

by Thomas Diesler (JIRA)

Comprehensive coverage of AS7 / OSGi integration in user guide -------------------------------------------------------------- Key: JBOSGI-489 URL: https://issues.jboss.org/browse/JBOSGI-489 Project: JBoss OSGi Issue Type: Task Security Level: Public (Everyone can see) Components: Documentation Reporter: Thomas Diesler Assignee: Thomas Diesler Fix For: JBossOSGi 1.0.1 Make sure folks like Matthew (http://community.jboss.org/message/619328) find what they need. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 2 months

1
2
0 / 0

[JBoss JIRA] Created: (JBOSGI-501) Retire standalone OSGi Runtime

by Thomas Diesler (JIRA)

Retire standalone OSGi Runtime ------------------------------ Key: JBOSGI-501 URL: https://issues.jboss.org/browse/JBOSGI-501 Project: JBoss OSGi Issue Type: Task Security Level: Public (Everyone can see) Components: Runtime Reporter: Thomas Diesler Assignee: Thomas Diesler -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 2 months

1
2
0 / 0

[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] (JBOSGI-521) Performace tests fail on felix/equinox

by Thomas Diesler (JIRA)

Thomas Diesler created JBOSGI-521: ------------------------------------- Summary: Performace tests fail on felix/equinox Key: JBOSGI-521 URL: https://issues.jboss.org/browse/JBOSGI-521 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 is probably related to build configuration changes due to ARQ updates -- 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, 2 months

2
3
0 / 0

[JBoss JIRA] (JBOSGI-526) The same org.jboss.osgi.metadata classes are present in jbosgi-repository-api and jbosgi-resolver-metadata

by Rostislav Svoboda (JIRA)

Rostislav Svoboda created JBOSGI-526: ---------------------------------------- Summary: The same org.jboss.osgi.metadata classes are present in jbosgi-repository-api and jbosgi-resolver-metadata Key: JBOSGI-526 URL: https://issues.jboss.org/browse/JBOSGI-526 Project: JBoss OSGi Issue Type: Bug Security Level: Public (Everyone can see) Components: Core Framework Reporter: Rostislav Svoboda Assignee: Thomas Diesler The same org.jboss.osgi.metadata classes are present in jbosgi-repository-api-1.0.4-redhat-0-todo.jar and jbosgi-resolver-metadata-1.0.11-redhat-0-todo.jar http://hudson.qa.jboss.com/hudson/view/EAP6/view/EAP6-Miscellaneous/job/e... Comment by Paul Gier: Since these are both upstream jars, this should be filed upstream in the JBoss OSGi project -- 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, 2 months

2
4
0 / 0

[JBoss JIRA] (JBOSGI-523) Unable to deploy without Bundle-Manifest Version or with Bundle-ManifestVersion: 1

by Rico Neubauer (JIRA)

Rico Neubauer created JBOSGI-523: ------------------------------------ Summary: Unable to deploy without Bundle-Manifest Version or with Bundle-ManifestVersion: 1 Key: JBOSGI-523 URL: https://issues.jboss.org/browse/JBOSGI-523 Project: JBoss OSGi Issue Type: Bug Security Level: Public (Everyone can see) Components: Core Framework Reporter: Rico Neubauer Assignee: Thomas Diesler Attachments: server.log Affects version 1.1.5, included in JBoss 7.1.final. OSGI-specification r4.core.pdf chapter 3.5.7 holds the rules for legacy (version 1) bundles. According to that a bundle without Bundle-ManifestVersion must be handles as Bundle-ManifestVersion: 1. Neither a bundle having Bundle-ManifestVersion: 1, not without a Bundle-ManifestVersion does deploy at all. You can only see "Starting deployment of ..." in the log, nothing else happens. See attached log file for a test showing the deployment of a bundle without/with version-1/with versio-2 ManifestVersion. -- 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, 2 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