June 2013 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-992) Cannot restart ejb3 bundle after activation failure

by Thomas Diesler (JIRA)

[ https://issues.jboss.org/browse/WFLY-992?page=com.atlassian.jira.plugin.s... ] Thomas Diesler resolved WFLY-992. --------------------------------- Resolution: Won't Fix Won't Fix - OSGi is going to get removed > Cannot restart ejb3 bundle after activation failure > --------------------------------------------------- > > Key: WFLY-992 > URL: https://issues.jboss.org/browse/WFLY-992 > Project: WildFly > Issue Type: Bug > Components: EJB, OSGi > Reporter: Thomas Diesler > Assignee: Bartosz Baranowski > > {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, 10 months

1
0
0 / 0

[JBoss JIRA] (WFLY-1382) OSGi: "Export-EJB" header is not supported to install/start EJB3 bundle from repository

by Thomas Diesler (JIRA)

[ https://issues.jboss.org/browse/WFLY-1382?page=com.atlassian.jira.plugin.... ] Thomas Diesler resolved WFLY-1382. ---------------------------------- Resolution: Won't Fix Won't Fix - OSGi is going to get removed > OSGi: "Export-EJB" header is not supported to install/start EJB3 bundle from repository > --------------------------------------------------------------------------------------- > > Key: WFLY-1382 > URL: https://issues.jboss.org/browse/WFLY-1382 > Project: WildFly > Issue Type: Bug > Components: OSGi > Affects Versions: 8.0.0.Alpha2 > Reporter: Igor Shulika > > 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, 10 months

1
0
0 / 0

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

by Thomas Diesler (JIRA)

[ https://issues.jboss.org/browse/WFLY-477?page=com.atlassian.jira.plugin.s... ] Thomas Diesler resolved WFLY-477. --------------------------------- Resolution: Won't Fix Won't Fix - OSGi is going to get removed > Provide a Bundle version of the javax.persistence API > ----------------------------------------------------- > > Key: WFLY-477 > URL: https://issues.jboss.org/browse/WFLY-477 > Project: WildFly > Issue Type: Task > Components: JPA / Hibernate, OSGi > Reporter: Thomas Diesler > Assignee: Scott Marlow > Fix For: 8.0.0.Alpha3 > > > 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, 10 months

1
0
0 / 0

[JBoss JIRA] (WFLY-1256) HttpService configurable virtual host/port

by Thomas Diesler (JIRA)

[ https://issues.jboss.org/browse/WFLY-1256?page=com.atlassian.jira.plugin.... ] Thomas Diesler resolved WFLY-1256. ---------------------------------- Resolution: Won't Fix Won't Fix - OSGi is going to get removed > HttpService configurable virtual host/port > ------------------------------------------ > > Key: WFLY-1256 > URL: https://issues.jboss.org/browse/WFLY-1256 > Project: WildFly > Issue Type: Sub-task > Components: OSGi > 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, 10 months

1
0
0 / 0

[JBoss JIRA] (WFLY-1226) Populate repository with metadata from system modules/bundles

by Thomas Diesler (JIRA)

[ https://issues.jboss.org/browse/WFLY-1226?page=com.atlassian.jira.plugin.... ] Thomas Diesler resolved WFLY-1226. ---------------------------------- Resolution: Won't Fix Won't Fix - OSGi is going to get removed > Populate repository with metadata from system modules/bundles > ------------------------------------------------------------- > > Key: WFLY-1226 > URL: https://issues.jboss.org/browse/WFLY-1226 > Project: WildFly > Issue Type: Task > Components: OSGi, Server > Reporter: Thomas Diesler > > 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, 10 months

1
0
0 / 0

[JBoss JIRA] (WFLY-1232) Complete implementation of the FrameworkFactory

by Thomas Diesler (JIRA)

[ https://issues.jboss.org/browse/WFLY-1232?page=com.atlassian.jira.plugin.... ] Thomas Diesler resolved WFLY-1232. ---------------------------------- Resolution: Won't Fix Won't Fix - OSGi is going to get removed > Complete implementation of the FrameworkFactory > ----------------------------------------------- > > Key: WFLY-1232 > URL: https://issues.jboss.org/browse/WFLY-1232 > Project: WildFly > Issue Type: Task > Components: OSGi > Reporter: David Bosschaert > Labels: roadmap > > The OSGi CT is currently run with the JBoss OSGi framework standalone. It should also be possible to run the CT with the AS7 integration. -- 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, 10 months

1
0
0 / 0

[JBoss JIRA] (WFLY-557) Complete support for Bundle update

by Thomas Diesler (JIRA)

[ https://issues.jboss.org/browse/WFLY-557?page=com.atlassian.jira.plugin.s... ] Thomas Diesler resolved WFLY-557. --------------------------------- Resolution: Won't Fix Won't Fix - OSGi is going to get removed > Complete support for Bundle update > ---------------------------------- > > Key: WFLY-557 > URL: https://issues.jboss.org/browse/WFLY-557 > Project: WildFly > Issue Type: Sub-task > Components: OSGi, Server > Reporter: Thomas Diesler > Assignee: Thomas Diesler > Fix For: 9.0.0.CR1 > > > A Bundle can have multiple revisions. A call to Bundle.update(…) creates a new revision. There is only ever one current revision (the latest update) associated with a Bundle. Stale revisions continue to exist in the runtime until an explicit refresh of the transitive dependency graph. > Approach #1 - bundle revisions are represented as individual deployments > Each bundle update deploys the revision as a new deployment > The association of revisions to bundle happens in the OSGi layer only > Management sees disconnected deployments with no notion of stale/current or belonging together > Approach #2 - deployment API supports the notion of multiple revisions > deployments, their revisions and respective mapping would be modelled more closely on OSGi requirements > some deployment types might not support revisions -- 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, 10 months

1
0
0 / 0

[JBoss JIRA] (WFLY-1187) Allow OSGi configuration to get modified before subsystem start

by Thomas Diesler (JIRA)

[ https://issues.jboss.org/browse/WFLY-1187?page=com.atlassian.jira.plugin.... ] Thomas Diesler resolved WFLY-1187. ---------------------------------- Resolution: Won't Fix Won't Fix - OSGi is going to get removed > Allow OSGi configuration to get modified before subsystem start > --------------------------------------------------------------- > > Key: WFLY-1187 > URL: https://issues.jboss.org/browse/WFLY-1187 > Project: WildFly > Issue Type: Feature Request > Components: OSGi > Reporter: Thomas Diesler > > It should be possible to > * start the server > * modify framework properties > * start the osgi subsystem with the updated properties -- 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, 10 months

1
0
0 / 0

[JBoss JIRA] (WFLY-1253) HttpService MimeType, ContentLength, etc

by Thomas Diesler (JIRA)

[ https://issues.jboss.org/browse/WFLY-1253?page=com.atlassian.jira.plugin.... ] Thomas Diesler resolved WFLY-1253. ---------------------------------- Resolution: Won't Fix Won't Fix - OSGi is going to get removed > HttpService MimeType, ContentLength, etc > ---------------------------------------- > > Key: WFLY-1253 > URL: https://issues.jboss.org/browse/WFLY-1253 > Project: WildFly > Issue Type: Sub-task > Components: OSGi > 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, 10 months

1
0
0 / 0

[JBoss JIRA] (WFLY-1076) Optimize OSGi subsystem bootstrap

by Thomas Diesler (JIRA)

[ https://issues.jboss.org/browse/WFLY-1076?page=com.atlassian.jira.plugin.... ] Thomas Diesler resolved WFLY-1076. ---------------------------------- Resolution: Won't Fix Won't Fix - OSGi is going to get removed > Optimize OSGi subsystem bootstrap > --------------------------------- > > Key: WFLY-1076 > URL: https://issues.jboss.org/browse/WFLY-1076 > Project: WildFly > Issue Type: Feature Request > Components: OSGi > 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, 10 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira June 2013