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

[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 moved WFLY-843 to JBOSGI-681: -------------------------------------------- Project: JBoss OSGi (was: WildFly) Key: JBOSGI-681 (was: WFLY-843) Workflow: jira (was: GIT Pull Request workflow ) Component/s: (was: OSGi) > Cannot restart webapp bundle after activation failure > ----------------------------------------------------- > > Key: JBOSGI-681 > URL: https://issues.jboss.org/browse/JBOSGI-681 > Project: JBoss OSGi > Issue Type: Bug > Reporter: Thomas Diesler > > {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, 4 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 moved WFLY-787 to JBOSGI-678: -------------------------------------------- Project: JBoss OSGi (was: WildFly) Key: JBOSGI-678 (was: WFLY-787) Workflow: jira (was: GIT Pull Request workflow ) Component/s: JPA/JDBC (was: JPA / Hibernate) (was: OSGi) > 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: JPA/JDBC > Reporter: Thomas Diesler > > {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, 4 months

1
0
0 / 0

[JBoss JIRA] (JBOSGI-685) OSGi requirements for AS9

by Thomas Diesler (JIRA)

[ https://issues.jboss.org/browse/JBOSGI-685?page=com.atlassian.jira.plugin... ] Thomas Diesler moved WFLY-540 to JBOSGI-685: -------------------------------------------- Project: JBoss OSGi (was: WildFly) Key: JBOSGI-685 (was: WFLY-540) Workflow: jira (was: GIT Pull Request workflow ) Component/s: (was: OSGi) > OSGi requirements for AS9 > ------------------------- > > Key: JBOSGI-685 > URL: https://issues.jboss.org/browse/JBOSGI-685 > Project: JBoss OSGi > Issue Type: Feature Request > Reporter: Thomas Diesler > > [jboss-as7-dev] [Resolving AS8/OSGi deployment disconnects|http://lists.jboss.org/pipermail/jboss-as7-dev/2013-April/007...] -- 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, 4 months

1
0
0 / 0

[JBoss JIRA] (JBOSGI-691) Optimize OSGi subsystem bootstrap

by Thomas Diesler (JIRA)

[ https://issues.jboss.org/browse/JBOSGI-691?page=com.atlassian.jira.plugin... ] Thomas Diesler moved WFLY-1076 to JBOSGI-691: --------------------------------------------- Project: JBoss OSGi (was: WildFly) Key: JBOSGI-691 (was: WFLY-1076) Workflow: jira (was: GIT Pull Request workflow ) Component/s: (was: OSGi) > Optimize OSGi subsystem bootstrap > --------------------------------- > > Key: JBOSGI-691 > URL: https://issues.jboss.org/browse/JBOSGI-691 > Project: JBoss OSGi > Issue Type: Feature Request > Reporter: Thomas Diesler > > The OSGi subsystem in AS7 is alrady activated lazily. However, in many cases users only want to deploy a simple artefact that "happens to be" an OSGi bundle (i.e. a JDBC driver) and do not want to deploy a large set of interconnected bundles that make up a complex modular enterprise application. For those cases the OSGi subsystem should bootstrap in a jiffy and we should not see a performance impact that is worth talking about. -- 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, 4 months

1
0
0 / 0

[JBoss JIRA] (JBOSGI-688) Complete runtime support for Karaf based products

by Thomas Diesler (JIRA)

[ https://issues.jboss.org/browse/JBOSGI-688?page=com.atlassian.jira.plugin... ] Thomas Diesler moved WFLY-1108 to JBOSGI-688: --------------------------------------------- Project: JBoss OSGi (was: WildFly) Key: JBOSGI-688 (was: WFLY-1108) Workflow: jira (was: GIT Pull Request workflow ) Component/s: (was: OSGi) > Complete runtime support for Karaf based products > ------------------------------------------------- > > Key: JBOSGI-688 > URL: https://issues.jboss.org/browse/JBOSGI-688 > Project: JBoss OSGi > Issue Type: Feature Request > Reporter: Thomas Diesler > Labels: roadmap > > Provide complete support for Karaf based products -- 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, 4 months

1
0
0 / 0

[JBoss JIRA] (JBOSGI-686) Allow detection caller management operation

by Thomas Diesler (JIRA)

[ https://issues.jboss.org/browse/JBOSGI-686?page=com.atlassian.jira.plugin... ] Thomas Diesler moved WFLY-1142 to JBOSGI-686: --------------------------------------------- Project: JBoss OSGi (was: WildFly) Key: JBOSGI-686 (was: WFLY-1142) Workflow: jira (was: GIT Pull Request workflow ) Component/s: (was: Domain Management) (was: OSGi) > Allow detection caller management operation > ------------------------------------------- > > Key: JBOSGI-686 > URL: https://issues.jboss.org/browse/JBOSGI-686 > Project: JBoss OSGi > Issue Type: Feature Request > Reporter: Thomas Diesler > > Currently we have a hack in place where we detect a running management operation using a ThreadLocal. The called code can take an alternative route and not execute a nested management operation which would deadlock. > See usages of org.jboss.as.osgi.management.OperationAssociation -- 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, 4 months

1
0
0 / 0

[JBoss JIRA] (JBOSGI-687) Allow OSGi services to be registered as JAX-WS endpoints

by Thomas Diesler (JIRA)

[ https://issues.jboss.org/browse/JBOSGI-687?page=com.atlassian.jira.plugin... ] Thomas Diesler moved WFLY-1280 to JBOSGI-687: --------------------------------------------- Project: JBoss OSGi (was: WildFly) Key: JBOSGI-687 (was: WFLY-1280) Workflow: jira (was: GIT Pull Request workflow ) Component/s: WebServices (was: OSGi) (was: Web Services) > Allow OSGi services to be registered as JAX-WS endpoints > -------------------------------------------------------- > > Key: JBOSGI-687 > URL: https://issues.jboss.org/browse/JBOSGI-687 > Project: JBoss OSGi > Issue Type: Feature Request > Components: WebServices > Reporter: Thomas Diesler > > It should be possible to register a WS endpoint similar to this > {code} > public void start(BundleContext context) { > HelloService helloService = new HelloServiceImpl(); > Dictionary props = new Hashtable(); > props.put("service.exported.interfaces", "*"); > props.put("service.exported.configs", "org.apache.cxf.ws"); > props.put("org.apache.cxf.ws.address", "http://localhost:8090/soap"); > registration = context.registerService(HelloService.class.getName(), helloService, props); > } > {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, 4 months

1
0
0 / 0

[JBoss JIRA] (JBOSGI-690) Complete support for OSGi JMX

by Thomas Diesler (JIRA)

[ https://issues.jboss.org/browse/JBOSGI-690?page=com.atlassian.jira.plugin... ] Thomas Diesler moved WFLY-1121 to JBOSGI-690: --------------------------------------------- Project: JBoss OSGi (was: WildFly) Key: JBOSGI-690 (was: WFLY-1121) Workflow: jira (was: GIT Pull Request workflow ) Component/s: JMX (was: JMX) (was: OSGi) > Complete support for OSGi JMX > ----------------------------- > > Key: JBOSGI-690 > URL: https://issues.jboss.org/browse/JBOSGI-690 > Project: JBoss OSGi > Issue Type: Feature Request > Components: JMX > Reporter: Thomas Diesler > Labels: roadmap > > R5 TCK compliance for JMX -- 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, 4 months

1
0
0 / 0

[JBoss JIRA] (JBOSGI-684) Enforce OSGi wiring symmetry across nodes

by Thomas Diesler (JIRA)

[ https://issues.jboss.org/browse/JBOSGI-684?page=com.atlassian.jira.plugin... ] Thomas Diesler moved WFLY-1075 to JBOSGI-684: --------------------------------------------- Project: JBoss OSGi (was: WildFly) Key: JBOSGI-684 (was: WFLY-1075) Workflow: jira (was: GIT Pull Request workflow ) Component/s: (was: Clustering) (was: OSGi) > Enforce OSGi wiring symmetry across nodes > ----------------------------------------- > > Key: JBOSGI-684 > URL: https://issues.jboss.org/browse/JBOSGI-684 > Project: JBoss OSGi > Issue Type: Feature Request > Reporter: Thomas Diesler > > Using a distributed cache in a multinode environment would require a mapping for the classloader. With symetric wiring only the top level cl needs to be mapped. Unsymentric wiring may lead to a number of unforeseeable issues. -- 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, 4 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 moved WFLY-993 to JBOSGI-669: -------------------------------------------- Project: JBoss OSGi (was: WildFly) Key: JBOSGI-669 (was: WFLY-993) Workflow: jira (was: GIT Pull Request workflow ) Component/s: (was: OSGi) > Cannot update OSGi WebApp > ------------------------- > > Key: JBOSGI-669 > URL: https://issues.jboss.org/browse/JBOSGI-669 > Project: JBoss OSGi > Issue Type: Bug > 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, 4 months

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

jboss-osgi-issues July 2013