[JBoss JIRA] (JBOSGI-743) Cannot restart webapp bundle
by Thomas Diesler (JIRA)
[ https://issues.jboss.org/browse/JBOSGI-743?page=com.atlassian.jira.plugin... ]
Thomas Diesler updated JBOSGI-743:
----------------------------------
Component/s: webapp
(was: wildfly)
> Cannot restart webapp bundle
> ----------------------------
>
> Key: JBOSGI-743
> URL: https://issues.jboss.org/browse/JBOSGI-743
> Project: JBoss OSGi
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: webapp
> Reporter: Thomas Diesler
> Fix For: JBossOSGi 2.1.1
>
>
> {code}
> testBundleWithWebContextPath(org.jboss.test.osgi.example.webapp.WebAppTestCase) Time elapsed: 0.437 sec <<< ERROR!
> java.lang.IllegalStateException: JBAS017345: Cannot activate context: service jboss.undertow.deployment.default-host./bundle-d
> at org.jboss.msc.inject.RetainingInjector.inject(RetainingInjector.java:50)
> at org.wildfly.extension.undertow.deployment.UndertowJSRWebSocketDeploymentProcessor$1.ready(UndertowJSRWebSocketDeploymentProcessor.java:240)
> at io.undertow.websockets.jsr.WebSocketDeploymentInfo.containerReady(WebSocketDeploymentInfo.java:64)
> at io.undertow.websockets.jsr.Bootstrap.handleDeployment(Bootstrap.java:50)
> at io.undertow.servlet.core.DeploymentManagerImpl.handleExtensions(DeploymentManagerImpl.java:209)
> at io.undertow.servlet.core.DeploymentManagerImpl.deploy(DeploymentManagerImpl.java:133)
> at org.wildfly.extension.undertow.deployment.UndertowDeploymentService.startContext(UndertowDeploymentService.java:83)
> at org.wildfly.extension.undertow.deployment.UndertowDeploymentService$ContextActivatorImpl.startContext(UndertowDeploymentService.java:154)
> at org.jboss.as.osgi.web.WebContextLifecycleInterceptor.invoke(WebContextLifecycleInterceptor.java:96)
> at org.jboss.osgi.deployment.interceptor.AbstractLifecycleInterceptorService.handleStateChange(AbstractLifecycleInterceptorService.java:264)
> at org.jboss.osgi.framework.internal.AbstractBundleState.changeState(AbstractBundleState.java:252)
> at org.jboss.osgi.framework.internal.AbstractBundleState.changeState(AbstractBundleState.java:241)
> at org.jboss.osgi.framework.internal.UserBundleState.startInternalNow(UserBundleState.java:635)
> at org.jboss.osgi.framework.internal.UserBundleState.startInternal(UserBundleState.java:524)
> at org.jboss.osgi.framework.internal.BundleManagerPlugin.startBundle(BundleManagerPlugin.java:572)
> {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
10 years, 8 months
[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:
----------------------------------
Component/s: ejb3
(was: wildfly)
> 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: ejb3
> 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
10 years, 8 months
[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 updated JBOSGI-687:
----------------------------------
Comment: was deleted
(was: Won't Fix - OSGi is going to get removed)
> 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: jaxws
> 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
10 years, 8 months
[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:
----------------------------------
Labels: (was: wildfly)
> 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: ejb3
> Reporter: Thomas Diesler
>
> {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
10 years, 8 months