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

[JBoss JIRA] (JBOSGI-673) Invalid bundle deployment does not fail in domain

by Thomas Diesler (JIRA)

[ https://issues.jboss.org/browse/JBOSGI-673?page=com.atlassian.jira.plugin... ] Thomas Diesler updated JBOSGI-673: ---------------------------------- Comment: was deleted (was: Won't Fix - OSGi is going to get removed) > Invalid bundle deployment does not fail in domain > ------------------------------------------------- > > Key: JBOSGI-673 > URL: https://issues.jboss.org/browse/JBOSGI-673 > Project: JBoss OSGi > Issue Type: Bug > Reporter: Thomas Diesler > Priority: Minor > > Running org.jboss.as.test.integration.domain.suites.OSGiBundleLifecyleTestCase > Tests run: 2, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 35.653 sec <<< FAILURE! > on the server I see > {code} > 15:20:28,619 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-1) MSC00001: Failed to start service jboss.deployment.unit.bad-bundle.STRUCTURE: org.jboss.msc.service.StartException in service jboss.deployment.unit.bad-bundle.STRUCTURE: Failed to process phase STRUCTURE of deployment "bad-bundle" > at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:119) [jboss-as-server-7.1.2.Final-SNAPSHOT.jar:7.1.2.Final-SNAPSHOT] > at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1811) [jboss-msc-1.0.2.GA.jar:1.0.2.GA] > at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1746) [jboss-msc-1.0.2.GA.jar:1.0.2.GA] > at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) [rt.jar:1.6.0_29] > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) [rt.jar:1.6.0_29] > at java.lang.Thread.run(Thread.java:662) [rt.jar:1.6.0_29] > Caused by: java.lang.NumberFormatException: For input string: "bogus" > at java.lang.NumberFormatException.forInputString(NumberFormatException.java:48) [rt.jar:1.6.0_29] > at java.lang.Integer.parseInt(Integer.java:449) [rt.jar:1.6.0_29] > at java.lang.Integer.parseInt(Integer.java:499) [rt.jar:1.6.0_29] > at org.osgi.framework.Version.<init>(Version.java:125) > at org.osgi.framework.Version.parseVersion(Version.java:218) > at org.jboss.osgi.spi.BundleInfo.validateBundleManifest(BundleInfo.java:204) > at org.jboss.osgi.spi.BundleInfo.isValidBundleManifest(BundleInfo.java:153) > at org.jboss.as.osgi.deployment.OSGiManifestStructureProcessor.deploy(OSGiManifestStructureProcessor.java:63) > {code} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBOSGI-666) Cannot lookup owner context using standard naming API

by Thomas Diesler (JIRA)

[ https://issues.jboss.org/browse/JBOSGI-666?page=com.atlassian.jira.plugin... ] Thomas Diesler updated JBOSGI-666: ---------------------------------- Component/s: WildFly > Cannot lookup owner context using standard naming API > ----------------------------------------------------- > > Key: JBOSGI-666 > URL: https://issues.jboss.org/browse/JBOSGI-666 > Project: JBoss OSGi > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: JNDI, WildFly > Affects Versions: JBossOSGi 2.0.0 > Reporter: Thomas Diesler > > {code} > Context initialContext = new InitialContext(); > BundleContext context = (BundleContext) initialContext.lookup("osgi:framework/bundleContext"); > {code} > fails with > {code} > testTraditionalAPIOwnerContext(org.jboss.test.osgi.example.jndi.NamingStandaloneTestCase) Time elapsed: 0.062 sec <<< FAILURE! > java.lang.AssertionError: expected:<BundleContext[jndi-tests:0.0.0]> but was:<BundleContext[arquillian-osgi-bundle:2.0.0.CR4]> > {code} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBOSGI-536) OSGi implementation does not support framework extensions

by Thomas Diesler (JIRA)

[ https://issues.jboss.org/browse/JBOSGI-536?page=com.atlassian.jira.plugin... ] Thomas Diesler updated JBOSGI-536: ---------------------------------- Fix Version/s: Awaiting Volunteers > OSGi implementation does not support framework extensions > --------------------------------------------------------- > > Key: JBOSGI-536 > URL: https://issues.jboss.org/browse/JBOSGI-536 > Project: JBoss OSGi > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Core Framework > Affects Versions: JBossOSGi 1.0.0 > Environment: Mac OS X 10.7.3 > Reporter: Tim Diekmann > Fix For: Awaiting Volunteers > > > Installing a System Framework extension fails in AS 7.1.0.Final. > {code} > 10:27:35,179 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-4) MSC00001: Failed to start service jbosgi.bundle.8."com.tibco.tpcl.javax.system.exports"."5.0.300.004".INSTALLED: org.jboss.msc.service.StartException in service jbosgi.bundle.8."com.tibco.tpcl.javax.system.exports"."5.0.300.004".INSTALLED: Failed to start service > at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1767) [jboss-msc-1.0.2.GA.jar:1.0.2.GA] > at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) [classes.jar:1.6.0_29] > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) [classes.jar:1.6.0_29] > at java.lang.Thread.run(Thread.java:680) [classes.jar:1.6.0_29] > Caused by: java.lang.UnsupportedOperationException: Framework extension not supported > at org.jboss.osgi.framework.internal.BundleValidatorR4.validateBundle(BundleValidatorR4.java:141) > at org.jboss.osgi.framework.internal.UserBundleInstalledService.validateBundle(UserBundleInstalledService.java:93) > at org.jboss.osgi.framework.internal.UserBundleInstalledService.start(UserBundleInstalledService.java:65) > at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1811) [jboss-msc-1.0.2.GA.jar:1.0.2.GA] > at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1746) [jboss-msc-1.0.2.GA.jar:1.0.2.GA] > ... 3 more > {code} > I tried adding this through the cli, web console, and by adding this manually to the bundles folder and updating the configuration file. Same result. > Please note that framework extensions support is mandated by the Core specification to be a certified OSGi framework. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBOSGI-655) Cannot access jboss-osgi API docs

by Thomas Diesler (JIRA)

[ https://issues.jboss.org/browse/JBOSGI-655?page=com.atlassian.jira.plugin... ] Thomas Diesler updated JBOSGI-655: ---------------------------------- Fix Version/s: JBossOSGi 2.0.1 > Cannot access jboss-osgi API docs > ---------------------------------- > > Key: JBOSGI-655 > URL: https://issues.jboss.org/browse/JBOSGI-655 > Project: JBoss OSGi > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Distribution > Reporter: Thomas Diesler > Fix For: JBossOSGi 2.0.1 > > > http://docs.jboss.org/osgi/apidocs > 403 Forbidden > You don't have permission to access /osgi/apidocs on this server. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBOSGI-511) MultiChainActivationTestCase fails on jdk1.7

by Thomas Diesler (JIRA)

[ https://issues.jboss.org/browse/JBOSGI-511?page=com.atlassian.jira.plugin... ] Thomas Diesler resolved JBOSGI-511. ----------------------------------- Resolution: Won't Fix Won't Fix > MultiChainActivationTestCase fails on jdk1.7 > -------------------------------------------- > > Key: JBOSGI-511 > URL: https://issues.jboss.org/browse/JBOSGI-511 > Project: JBoss OSGi > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Core Framework > Reporter: Thomas Diesler > > testComplexGraph(org.jboss.test.osgi.framework.bundle.activation.MultiChainActivationTestCase): expected:<tbchain5:0.0.0> but was:<tbchain2:0.0.0> -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBOSGI-669) Cannot update OSGi WebApp

by Thomas Diesler (JIRA)

[ https://issues.jboss.org/browse/JBOSGI-669?page=com.atlassian.jira.plugin... ] Thomas Diesler updated JBOSGI-669: ---------------------------------- Component/s: WebApp > Cannot update OSGi WebApp > ------------------------- > > Key: JBOSGI-669 > URL: https://issues.jboss.org/browse/JBOSGI-669 > Project: JBoss OSGi > Issue Type: Bug > Components: WebApp, WildFly > Reporter: Thomas Diesler > -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBOSGI-519) InitialContextFactoryBuilder already registered in AS

by Thomas Diesler (JIRA)

[ https://issues.jboss.org/browse/JBOSGI-519?page=com.atlassian.jira.plugin... ] Thomas Diesler updated JBOSGI-519: ---------------------------------- Component/s: WildFly > InitialContextFactoryBuilder already registered in AS > ----------------------------------------------------- > > Key: JBOSGI-519 > URL: https://issues.jboss.org/browse/JBOSGI-519 > Project: JBoss OSGi > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: JNDI, WildFly > Reporter: Thomas Diesler > > In AS we see > {code} > 09:59:52,782 INFO [org.apache.aries.jndi.startup.Activator] (pool-4-thread-1) It was not possible to register an InitialContextFactoryBuilder with the NamingManager because another builder called org.jboss.as.naming.InitialContextFactoryBuilder was already registered. Support for calling new InitialContext() will not be enabled.: java.lang.IllegalStateException: InitialContextFactoryBuilder already set > at javax.naming.spi.NamingManager.setInitialContextFactoryBuilder(NamingManager.java:692) [rt.jar:1.6.0_29] > at org.apache.aries.jndi.startup.Activator.start(Activator.java:76) > at org.apache.aries.jndi.priv.Activator.start(Activator.java:38) > at org.jboss.osgi.framework.internal.HostBundleState.transitionToActive(HostBundleState.java:300) > at org.jboss.osgi.framework.internal.HostBundleState.startInternal(HostBundleState.java:223) > at org.jboss.osgi.framework.internal.AbstractBundleState.start(AbstractBundleState.java:488) > at org.jboss.test.osgi.NamingSupport.provideJNDIIntegration(NamingSupport.java:44) > at org.jboss.test.osgi.example.jndi.JNDITestCase.testOSGiNamingContext(JNDITestCase.java:91) > {code} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBOSGI-628) resteasy-jackson-provider exported org.jboss.resteasy.plugins.providers

by Thomas Diesler (JIRA)

[ https://issues.jboss.org/browse/JBOSGI-628?page=com.atlassian.jira.plugin... ] Thomas Diesler resolved JBOSGI-628. ----------------------------------- Resolution: Won't Fix Won't Fix > resteasy-jackson-provider exported org.jboss.resteasy.plugins.providers > ------------------------------------------------------------------------ > > Key: JBOSGI-628 > URL: https://issues.jboss.org/browse/JBOSGI-628 > Project: JBoss OSGi > Issue Type: Bug > Security Level: Public(Everyone can see) > Affects Versions: JBossOSGi 1.1.1 > Environment: JBoss 7.1.1.Final > Reporter: Arthur Tsang > > resteasy-jackson-provider exported org.jboss.resteasy.plugins.providers which it has no class in that package. Bundle importing org.jboss.resteasy.plugins.providers might bind to resteasy-jackson-provider instead of resteasy-jaxrs resulting in class not found exception. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBOSGI-669) Cannot update OSGi WebApp

by Thomas Diesler (JIRA)

[ https://issues.jboss.org/browse/JBOSGI-669?page=com.atlassian.jira.plugin... ] Thomas Diesler updated JBOSGI-669: ---------------------------------- Component/s: WildFly > Cannot update OSGi WebApp > ------------------------- > > Key: JBOSGI-669 > URL: https://issues.jboss.org/browse/JBOSGI-669 > Project: JBoss OSGi > Issue Type: Bug > Components: WildFly > Reporter: Thomas Diesler > -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBOSGI-668) Attribute read for uninstalled bundle breaks console

by Thomas Diesler (JIRA)

[ https://issues.jboss.org/browse/JBOSGI-668?page=com.atlassian.jira.plugin... ] Thomas Diesler updated JBOSGI-668: ---------------------------------- Component/s: WildFly > Attribute read for uninstalled bundle breaks console > ---------------------------------------------------- > > Key: JBOSGI-668 > URL: https://issues.jboss.org/browse/JBOSGI-668 > Project: JBoss OSGi > Issue Type: Bug > Components: WildFly > Reporter: Thomas Diesler > Attachments: unread_bundle_stacktrace.txt, unread_bundle_stacktrace_cli.txt > > -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 9 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

jboss-osgi-issues July 2013