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

[JBoss JIRA] (JBOSGI-567) Add support for manifest header related APIs on Module adaptors

by Thomas Diesler (JIRA)

[ https://issues.jboss.org/browse/JBOSGI-567?page=com.atlassian.jira.plugin... ] Thomas Diesler updated JBOSGI-567: ---------------------------------- Fix Version/s: Awaiting Volunteers > Add support for manifest header related APIs on Module adaptors > --------------------------------------------------------------- > > Key: JBOSGI-567 > URL: https://issues.jboss.org/browse/JBOSGI-567 > Project: JBoss OSGi > Issue Type: Task > Security Level: Public(Everyone can see) > Components: Core Framework > Reporter: Thomas Diesler > Fix For: Awaiting Volunteers > > -- 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-667) OSGi: "Export-EJB" header is not supported to install/start EJB3 bundle from repository

by Thomas Diesler (JIRA)

[ https://issues.jboss.org/browse/JBOSGI-667?page=com.atlassian.jira.plugin... ] Thomas Diesler updated JBOSGI-667: ---------------------------------- Fix Version/s: JBossOSGi 2.0.1 > OSGi: "Export-EJB" header is not supported to install/start EJB3 bundle from repository > --------------------------------------------------------------------------------------- > > Key: JBOSGI-667 > URL: https://issues.jboss.org/browse/JBOSGI-667 > Project: JBoss OSGi > Issue Type: Bug > Components: WildFly > Reporter: Igor Shulika > Fix For: JBossOSGi 2.0.1 > > > I am using the latest WildFly 8.0.0.Alpha2-SNAPSHOT server to install/start all of my OSGi bundles from Maven repository. The EJB 3 MDB is not starting if I am just declare capability in the standalone-osgi.xml file. > > Here is my capability configuration. > <capability name="org.test.ejb3.mdb:ejb-high-velocity-queue-mdb:1.0" startlevel="4"/> > > Note: When I just simply drop my EJB 3 MDB JAR file inside "deployments" directory the message driven bean starting successfully (see below). > INFO [org.jboss.as.ejb3] (MSC service thread 1-2) JBAS014142: Started message driven bean 'HighVelocityQueueMessageBean' with 'hornetq-ra' resource adapter. -- 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: ---------------------------------- Fix Version/s: JBossOSGi 2.0.1 > 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 > Fix For: JBossOSGi 2.0.1 > > 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

[JBoss JIRA] (JBOSGI-672) DuplicateServiceException on undertow deployment replace

by Thomas Diesler (JIRA)

[ https://issues.jboss.org/browse/JBOSGI-672?page=com.atlassian.jira.plugin... ] Thomas Diesler updated JBOSGI-672: ---------------------------------- Fix Version/s: JBossOSGi 2.0.1 > DuplicateServiceException on undertow deployment replace > -------------------------------------------------------- > > Key: JBOSGI-672 > URL: https://issues.jboss.org/browse/JBOSGI-672 > Project: JBoss OSGi > Issue Type: Bug > Components: Enterprise OSGi, WildFly > Reporter: Thomas Diesler > Fix For: JBossOSGi 2.0.1 > > > {code} > 07:21:52,095 INFO [org.jboss.as.server.deployment] (MSC service thread 1-1) JBAS015876: Starting deployment of "webapp-v101.wab" (runtime-name: "webapp-v101.wab") > 07:21:52,119 INFO [org.jboss.osgi.framework] (MSC service thread 1-3) JBOSGI011001: Bundle installed: webapp-v101.wab:1.0.1 > 07:21:52,119 INFO [org.wildfly.extension.undertow] (MSC service thread 1-1) JBAS018224: Unregister web context: /simple-bundle > 07:21:52,119 INFO [org.jboss.osgi.framework] (MSC service thread 1-4) JBOSGI011003: Bundle stopped: webapp-v100.wab:1.0.0 > 07:21:52,124 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-3) MSC000001: Failed to start service jboss.deployment.unit."webapp-v101.wab".INSTALL: org.jboss.msc.service.StartException in service jboss.deployment.unit."webapp-v101.wab".INSTALL: JBAS018733: Failed to process phase INSTALL of deployment "webapp-v101.wab" > at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:166) [wildfly-server-8.0.0.Alpha2-SNAPSHOT.jar:8.0.0.Alpha2-SNAPSHOT] > at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1942) [jboss-msc-1.2.0.Beta1.jar:1.2.0.Beta1] > at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1875) [jboss-msc-1.2.0.Beta1.jar:1.2.0.Beta1] > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) [rt.jar:1.7.0_13] > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) [rt.jar:1.7.0_13] > at java.lang.Thread.run(Thread.java:722) [rt.jar:1.7.0_13] > Caused by: org.jboss.msc.service.DuplicateServiceException: Service jboss.undertow.deployment.default-host./simple-bundle.UndertowDeploymentInfoService is already registered > at org.jboss.msc.service.ServiceRegistrationImpl.setInstance(ServiceRegistrationImpl.java:158) [jboss-msc-1.2.0.Beta1.jar:1.2.0.Beta1] > at org.jboss.msc.service.ServiceControllerImpl.startInstallation(ServiceControllerImpl.java:235) [jboss-msc-1.2.0.Beta1.jar:1.2.0.Beta1] > at org.jboss.msc.service.ServiceContainerImpl.install(ServiceContainerImpl.java:767) [jboss-msc-1.2.0.Beta1.jar:1.2.0.Beta1] > at org.jboss.msc.service.ServiceTargetImpl.install(ServiceTargetImpl.java:223) [jboss-msc-1.2.0.Beta1.jar:1.2.0.Beta1] > at org.jboss.msc.service.ServiceControllerImpl$ChildServiceTarget.install(ServiceControllerImpl.java:2382) [jboss-msc-1.2.0.Beta1.jar:1.2.0.Beta1] > at org.jboss.msc.service.ServiceTargetImpl.install(ServiceTargetImpl.java:223) [jboss-msc-1.2.0.Beta1.jar:1.2.0.Beta1] > at org.jboss.msc.service.ServiceControllerImpl$ChildServiceTarget.install(ServiceControllerImpl.java:2382) [jboss-msc-1.2.0.Beta1.jar:1.2.0.Beta1] > at org.jboss.msc.service.ServiceBuilderImpl.install(ServiceBuilderImpl.java:317) [jboss-msc-1.2.0.Beta1.jar:1.2.0.Beta1] > at org.wildfly.extension.undertow.deployment.UndertowDeploymentProcessor.processDeployment(UndertowDeploymentProcessor.java:235) > at org.wildfly.extension.undertow.deployment.UndertowDeploymentProcessor.deploy(UndertowDeploymentProcessor.java:102) > at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:159) [wildfly-server-8.0.0.Alpha2-SNAPSHOT.jar:8.0.0.Alpha2-SNAPSHOT] > {code} > http://teamcity.cafe-babe.org/viewLog.html?buildId=5380&tab=buildResultsD... -- 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-721) Separate feature provisioning service from OSGi

by Thomas Diesler (JIRA)

[ https://issues.jboss.org/browse/JBOSGI-721?page=com.atlassian.jira.plugin... ] Thomas Diesler updated JBOSGI-721: ---------------------------------- Fix Version/s: JBossOSGi 2.0.1 > Separate feature provisioning service from OSGi > ------------------------------------------------ > > Key: JBOSGI-721 > URL: https://issues.jboss.org/browse/JBOSGI-721 > Project: JBoss OSGi > Issue Type: Task > Components: Enterprise OSGi > Reporter: Thomas Diesler > Labels: repository > Fix For: JBossOSGi 2.0.1 > > -- 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-732) Populate repository with metadata from system modules/bundles

by Thomas Diesler (JIRA)

[ https://issues.jboss.org/browse/JBOSGI-732?page=com.atlassian.jira.plugin... ] Thomas Diesler updated JBOSGI-732: ---------------------------------- Fix Version/s: JBossOSGi 2.0.1 > Populate repository with metadata from system modules/bundles > ------------------------------------------------------------- > > Key: JBOSGI-732 > URL: https://issues.jboss.org/browse/JBOSGI-732 > Project: JBoss OSGi > Issue Type: Task > Components: Enterprise OSGi, WildFly > Reporter: Thomas Diesler > Labels: repository > Fix For: JBossOSGi 2.0.1 > > > The OSGi configuration supports ModuleIdentifiers. So for example > {code} > <capability name="javax.transaction.api"/> > {code} > references the JTA API module. This actually delegates to the repository implementations which in turn delegates to the ModuleIdentityArtifactProvider. > If the AppServer supports the notion of multiple directories where modules can get loaded from, the ServerEnvironment should reflect that properly. I cannot just load a module on trial/error basis because we use the Repository for impact ananlysis. i.e. Find the modules/bundles that provide the transitive set of capabilities for a given set of requirements (without modifying the runtime). -- 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-722) Remove support for legacy osgi subsystem namespaces

by Thomas Diesler (JIRA)

[ https://issues.jboss.org/browse/JBOSGI-722?page=com.atlassian.jira.plugin... ] Thomas Diesler updated JBOSGI-722: ---------------------------------- Fix Version/s: JBossOSGi 2.0.1 > Remove support for legacy osgi subsystem namespaces > --------------------------------------------------- > > Key: JBOSGI-722 > URL: https://issues.jboss.org/browse/JBOSGI-722 > Project: JBoss OSGi > Issue Type: Task > Components: WildFly > Reporter: Thomas Diesler > Fix For: JBossOSGi 2.0.1 > > -- 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-725) Add test coverage for ResourceProvisioner service

by Thomas Diesler (JIRA)

[ https://issues.jboss.org/browse/JBOSGI-725?page=com.atlassian.jira.plugin... ] Thomas Diesler updated JBOSGI-725: ---------------------------------- Fix Version/s: JBossOSGi 2.0.1 > Add test coverage for ResourceProvisioner service > ------------------------------------------------- > > Key: JBOSGI-725 > URL: https://issues.jboss.org/browse/JBOSGI-725 > Project: JBoss OSGi > Issue Type: Task > Components: Enterprise OSGi > Reporter: Thomas Diesler > Labels: repository > Fix For: JBossOSGi 2.0.1 > > -- 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-589) Support reference: URLs

by Thomas Diesler (JIRA)

[ https://issues.jboss.org/browse/JBOSGI-589?page=com.atlassian.jira.plugin... ] Thomas Diesler updated JBOSGI-589: ---------------------------------- Fix Version/s: JBossOSGi 2.0.1 > Support reference: URLs > ----------------------- > > Key: JBOSGI-589 > URL: https://issues.jboss.org/browse/JBOSGI-589 > Project: JBoss OSGi > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Core Framework > Affects Versions: JBossOSGi 1.1.1 > Reporter: Harald Wellmann > Fix For: JBossOSGi 2.0.1 > > > While this is not an official OSGi standard, Equinox, Felix and Knopflerfish all support {{reference:file:}} URLs for provisioning bundles in place, without copying them to the OSGi storage area. > This works both for JARs and for directories (exploded bundles), e.g. > {noformat} > reference:file:/path/to/my/bundle.jar > reference:file:target/classes/ > {noformat} > For interoperability of frameworks, it would be useful for JBoss OSGi to support this protocol. -- 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-731) Remove hard wired dependency on configadmin

by Thomas Diesler (JIRA)

[ https://issues.jboss.org/browse/JBOSGI-731?page=com.atlassian.jira.plugin... ] Thomas Diesler updated JBOSGI-731: ---------------------------------- Fix Version/s: JBossOSGi 2.0.1 > Remove hard wired dependency on configadmin > ------------------------------------------- > > Key: JBOSGI-731 > URL: https://issues.jboss.org/browse/JBOSGI-731 > Project: JBoss OSGi > Issue Type: Task > Components: Enterprise OSGi, WildFly > Reporter: Thomas Diesler > Fix For: JBossOSGi 2.0.1 > > > {code} > interface SystemPackagesIntegration { > String[] DEFAULT_SYSTEM_MODULES = new String[] { > "javax.api", > "javax.inject.api", > "org.apache.xerces", > "org.jboss.as.configadmin", > "org.jboss.as.controller-client", > "org.jboss.as.osgi", > "org.jboss.dmr", > "org.jboss.logging", > "org.jboss.modules", > "org.jboss.msc", > "org.jboss.osgi.framework", > "org.jboss.osgi.repository", > "org.jboss.osgi.resolver" > }; > {code} > A modular build that contains osgi must currently also contain configadmin -- 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