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

[JBoss JIRA] (JBOSGI-734) Provide a Bundle version of the javax.persistence API

by Thomas Diesler (JIRA)

[ https://issues.jboss.org/browse/JBOSGI-734?page=com.atlassian.jira.plugin... ] Thomas Diesler updated JBOSGI-734: ---------------------------------- Fix Version/s: Awaiting WildFly Support > Provide a Bundle version of the javax.persistence API > ----------------------------------------------------- > > Key: JBOSGI-734 > URL: https://issues.jboss.org/browse/JBOSGI-734 > Project: JBoss OSGi > Issue Type: Task > Components: Enterprise OSGi, WildFly > Reporter: Thomas Diesler > Labels: jdbc, jpa > Fix For: Awaiting WildFly Support > > > This API is currently provided by hibernate-jpa-2.0-api-1.0.1.Final > Here is an [example|http://mvnrepository.com/artifact/org.eclipse.persistence/javax.p...] -- 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: ---------------------------------- Fix Version/s: Awaiting WildFly Support > Cannot update OSGi WebApp > ------------------------- > > Key: JBOSGI-669 > URL: https://issues.jboss.org/browse/JBOSGI-669 > Project: JBoss OSGi > Issue Type: Bug > Components: Enterprise OSGi, WildFly > Reporter: Thomas Diesler > Fix For: Awaiting WildFly Support > > -- 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-678) Cannot restart jpa bundle after activation failure

by Thomas Diesler (JIRA)

[ https://issues.jboss.org/browse/JBOSGI-678?page=com.atlassian.jira.plugin... ] Thomas Diesler updated JBOSGI-678: ---------------------------------- Fix Version/s: Awaiting WildFly Support > Cannot restart jpa bundle after activation failure > -------------------------------------------------- > > Key: JBOSGI-678 > URL: https://issues.jboss.org/browse/JBOSGI-678 > Project: JBoss OSGi > Issue Type: Bug > Components: Enterprise OSGi, WildFly > Reporter: Thomas Diesler > Labels: jdbc, jpa > Fix For: Awaiting WildFly Support > > > {code} > Caused by: java.lang.IllegalStateException: JBAS014666: Duplicate resource persistence-bundle-b.jar#simple-persistence > at org.jboss.as.controller.registry.AbstractModelResource$DefaultResourceProvider.register(AbstractModelResource.java:225) > at org.jboss.as.controller.registry.AbstractModelResource.registerChild(AbstractModelResource.java:135) > at org.jboss.as.jpa.processor.PersistenceUnitServiceHandler.addManagementConsole(PersistenceUnitServiceHandler.java:727) > at org.jboss.as.jpa.processor.PersistenceUnitServiceHandler.deployPersistenceUnit(PersistenceUnitServiceHandler.java:406) > at org.jboss.as.jpa.processor.PersistenceUnitServiceHandler.addPuService(PersistenceUnitServiceHandler.java:274) > at org.jboss.as.jpa.processor.PersistenceUnitServiceHandler.handleJarDeployment(PersistenceUnitServiceHandler.java:142) > at org.jboss.as.jpa.processor.PersistenceUnitServiceHandler.deploy(PersistenceUnitServiceHandler.java:117) > at org.jboss.as.jpa.processor.PersistenceCompleteInstallProcessor.deploy(PersistenceCompleteInstallProcessor.java:48) > at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:120) [jboss-as-server-7.2.0.Alpha1-SNAPSHOT.jar:7.2 > {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-681) Cannot restart webapp bundle after activation failure

by Thomas Diesler (JIRA)

[ https://issues.jboss.org/browse/JBOSGI-681?page=com.atlassian.jira.plugin... ] Thomas Diesler updated JBOSGI-681: ---------------------------------- Fix Version/s: Awaiting WildFly Support > Cannot restart webapp bundle after activation failure > ----------------------------------------------------- > > Key: JBOSGI-681 > URL: https://issues.jboss.org/browse/JBOSGI-681 > Project: JBoss OSGi > Issue Type: Bug > Components: WildFly > Reporter: Thomas Diesler > Fix For: Awaiting WildFly Support > > > {code} > Caused by: java.lang.IllegalStateException > at org.jboss.msc.value.InjectedValue.getValue(InjectedValue.java:47) [jboss-msc-1.0.2.GA.jar:1.0.2.GA] > at org.jboss.as.connector.deployers.ra.processors.CachedConnectionManagerSetupProcessor$CachedConnectionManagerSetupAction.setup(CachedConnectionManagerSetupProcessor.java:74) > at org.jboss.as.web.ThreadSetupBindingListener.bind(ThreadSetupBindingListener.java:50) > at org.apache.catalina.core.StandardContext.bindThread(StandardContext.java:4234) > at org.apache.catalina.core.StandardContext.start(StandardContext.java:3740) > at org.jboss.as.web.deployment.WebDeploymentService.start(WebDeploymentService.java:102) > {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-674) Cannot restart ejb3 bundle after activation failure

by Thomas Diesler (JIRA)

[ https://issues.jboss.org/browse/JBOSGI-674?page=com.atlassian.jira.plugin... ] Thomas Diesler updated JBOSGI-674: ---------------------------------- Fix Version/s: Awaiting WildFly Support > Cannot restart ejb3 bundle after activation failure > --------------------------------------------------- > > Key: JBOSGI-674 > URL: https://issues.jboss.org/browse/JBOSGI-674 > Project: JBoss OSGi > Issue Type: Bug > Components: Enterprise OSGi, WildFly > Reporter: Thomas Diesler > Fix For: Awaiting WildFly Support > > > {code} > Caused by: org.jboss.as.server.deployment.DeploymentUnitProcessingException: JBAS011030: Could not configure component SampleSFSB > at org.jboss.as.ee.component.deployers.EEModuleConfigurationProcessor.deploy(EEModuleConfigurationProcessor.java:91) > at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:120) [jboss-as-server-7.2.0.Alpha1-SNAPSHOT.jar:7.2.0.Alpha1-SNAPSHOT] > ... 5 more > Caused by: java.lang.IllegalArgumentException: JBAS011085: Can't add org.jboss.as.ejb3.component.stateful.StatefulSessionSynchronizationInterceptor$Factory@6f9e0e7b, priority 0x500 is already taken by org.jboss.as.ejb3.component.stateful.StatefulSessionSynchronizationInterceptor$Factory@6f9e0e7b > at org.jboss.as.ee.component.interceptors.OrderedItemContainer.add(OrderedItemContainer.java:58) > at org.jboss.as.ee.component.ComponentConfiguration.addComponentInterceptor(ComponentConfiguration.java:181) > at org.jboss.as.ejb3.component.stateful.StatefulComponentDescription$2.configure(StatefulComponentDescription.java:153) > at org.jboss.as.ee.component.deployers.EEModuleConfigurationProcessor.deploy(EEModuleConfigurationProcessor.java:80) > {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-675) Cannot replace jar that bundle depends on

by Thomas Diesler (JIRA)

[ https://issues.jboss.org/browse/JBOSGI-675?page=com.atlassian.jira.plugin... ] Thomas Diesler updated JBOSGI-675: ---------------------------------- Fix Version/s: Awaiting WildFly Support > Cannot replace jar that bundle depends on > ----------------------------------------- > > Key: JBOSGI-675 > URL: https://issues.jboss.org/browse/JBOSGI-675 > Project: JBoss OSGi > Issue Type: Bug > Components: WildFly > Reporter: Thomas Diesler > Fix For: Awaiting WildFly Support > > > With an OSGi webapp that depends on a jar the jar cannot be replaced. > See BundleReplaceTestCase.testDependentJarReplace() -- 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-487) Add an introduction to Enterprise OSGi to the Wiki

by Thomas Diesler (JIRA)

[ https://issues.jboss.org/browse/JBOSGI-487?page=com.atlassian.jira.plugin... ] Thomas Diesler updated JBOSGI-487: ---------------------------------- Fix Version/s: Awaiting Volunteers > Add an introduction to Enterprise OSGi to the Wiki > -------------------------------------------------- > > Key: JBOSGI-487 > URL: https://issues.jboss.org/browse/JBOSGI-487 > Project: JBoss OSGi > Issue Type: Task > Security Level: Public(Everyone can see) > Components: Distribution > Reporter: Thomas Diesler > Fix For: Awaiting Volunteers > > > Add EOSGi-4.2 coverage to https://docs.jboss.org/author/display/JBOSGI/Introduction -- 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-541) Document how bundle configurations can be edited

by Thomas Diesler (JIRA)

[ https://issues.jboss.org/browse/JBOSGI-541?page=com.atlassian.jira.plugin... ] Thomas Diesler resolved JBOSGI-541. ----------------------------------- Resolution: Won't Fix Won't Fix - This should be done via Felix WebConsole > Document how bundle configurations can be edited > ------------------------------------------------ > > Key: JBOSGI-541 > URL: https://issues.jboss.org/browse/JBOSGI-541 > Project: JBoss OSGi > Issue Type: Task > Security Level: Public(Everyone can see) > Components: Distribution > 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-698) Provide access to OSGiMetaData for server, web, etc

by Thomas Diesler (JIRA)

[ https://issues.jboss.org/browse/JBOSGI-698?page=com.atlassian.jira.plugin... ] Thomas Diesler updated JBOSGI-698: ---------------------------------- Fix Version/s: Awaiting Volunteers > Provide access to OSGiMetaData for server, web, etc > --------------------------------------------------- > > Key: JBOSGI-698 > URL: https://issues.jboss.org/browse/JBOSGI-698 > Project: JBoss OSGi > Issue Type: Feature Request > Components: WildFly > Reporter: Thomas Diesler > Fix For: Awaiting Volunteers > > > Currently we have a policy that server does not have a dependency on OSGi API and as a result to OSGiMetaData. > In several places we do a check like this > {code} > if (depUnit.hasAttachment(Attachments.OSGI_MANIFEST)) { > ... > } > {code} > This however implies that the Manifest is the only possible source of valid OSGi metadata. The OSGi webapp spec allows for metadata to be specified as part of a "webbundle://" URI (see AS7-6006) > To make this work, the integration code currently generates a Manifest and later OSGiMetaData from it. The above code still works even if the deployment content does not have a Manifest. > I propose to move the OSGiMetaData one level down so that > {code} > if (depUnit.hasAttachment(Attachments.OSGI_METADATA)) { > ... > } > {code} > is the deciding criteria. As a additional benefit web would no longer need to produce/consume the raw Manifest headers and OSGi metadata would be treated like all other metadata structures. -- 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-677) Some javax.* bundles show version 0.0.0 in AS7

by Thomas Diesler (JIRA)

[ https://issues.jboss.org/browse/JBOSGI-677?page=com.atlassian.jira.plugin... ] Thomas Diesler updated JBOSGI-677: ---------------------------------- Fix Version/s: JBossOSGi 2.0.1 > Some javax.* bundles show version 0.0.0 in AS7 > ---------------------------------------------- > > Key: JBOSGI-677 > URL: https://issues.jboss.org/browse/JBOSGI-677 > Project: JBoss OSGi > Issue Type: Bug > Components: WildFly > Reporter: Thomas Diesler > Fix For: JBossOSGi 2.0.1 > > > Some javax bundles that we configure by default do not show valid bundle version info > javax.jws.api:0.0.0 > javax.ws.rs.api:0.0.0 > The javax.persistence.api has its metadata defined in jbosgi-xservice.properties like this > {code} > Bundle-SymbolicName: hibernate-jpa-2.0-api > Bundle-Version: 1.0.1.Final > Export-Package: javax.persistence.spi;version="2.0.0",javax.persistence.criteria;version="2.0.0",javax.persistence;version="2.0.0",javax.persistence.metamodel;version="2.0.0" > {code} > This should be replaced by metadata coming from the artefacts manifest. > Generally, all javax api artefacts should have valid OSGi metadata -- 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