[JBoss JIRA] Created: (EJBTHREE-1604) Do not create new WebServiceContext when already provided
by Alessio Soldano (JIRA)
Do not create new WebServiceContext when already provided
----------------------------------------------------------
Key: EJBTHREE-1604
URL: https://jira.jboss.org/jira/browse/EJBTHREE-1604
Project: EJB 3.0
Issue Type: Feature Request
Reporter: Alessio Soldano
Assignee: Alessio Soldano
The StatelessContainer's method invokeEndpoint(Method method, Object[] args, InvocationContextCallback invCtxCallback) currently get the WebServiceContext instance using the right jbossws-spi factory. This is an issue with the JBossWS-Metro stack as we should use the WebServiceContext it already provides.
This should be passed in as an attachment in the InvocationContextCallback.
Something like this should work:
...
WebServiceContext providedCtx = invCtxCallback.getAttachment(WebServiceContext.class);
if (providedCtx != null)
{
//use the provided one through a delegate
jaxwsContext = new WebServiceContextDelegate(providedCtx);
}
else
{
//do as we used to do
jaxwsContext = contextFactory.newWebServiceContext(InvocationType.JAXWS_EJB3, invCtxCallback.get(javax.xml.ws.handler.MessageContext.class));
}
...
This requires jbossws-spi 1.0.7 to be released and specified in the dependencies because of the WebServiceContextDelegate.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 7 months
[JBoss JIRA] Created: (AS7-921) Booting AS7 on a system without any network connection throws up an error from ModClusterService
by jaikiran pai (JIRA)
Booting AS7 on a system without any network connection throws up an error from ModClusterService
------------------------------------------------------------------------------------------------
Key: AS7-921
URL: https://issues.jboss.org/browse/AS7-921
Project: Application Server 7
Issue Type: Bug
Environment: AS7 upstream (dated May 30 2011)
Reporter: jaikiran pai
Assignee: Jean-Frederic Clere
Fix For: 7.0.0.CR1
Starting AS7 (upstream) on a system which doesn't have any network connection throws up the following error during startup:
{code}
15:38:22,766 ERROR [org.jboss.modcluster.ModClusterService] (MSC service thread 1-1) Error starting advertise listener: java.net.SocketException: No such device
at java.net.PlainDatagramSocketImpl.join(Native Method) [:1.6.0_21]
at java.net.PlainDatagramSocketImpl.join(PlainDatagramSocketImpl.java:172) [:1.6.0_21]
at java.net.MulticastSocket.joinGroup(MulticastSocket.java:277) [:1.6.0_21]
at org.jboss.modcluster.advertise.impl.AdvertiseListenerImpl.init(AdvertiseListenerImpl.java:181)
at org.jboss.modcluster.advertise.impl.AdvertiseListenerImpl.start(AdvertiseListenerImpl.java:193)
at org.jboss.modcluster.ModClusterService.init(ModClusterService.java:174)
at org.jboss.modcluster.catalina.CatalinaEventHandlerAdapter.init(CatalinaEventHandlerAdapter.java:335)
at org.jboss.modcluster.catalina.CatalinaEventHandlerAdapter.start(CatalinaEventHandlerAdapter.java:115)
at org.jboss.as.modcluster.ModClusterService.start(ModClusterService.java:188)
at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1675) [jboss-msc-1.0.0.Beta8.jar:1.0.0.Beta8]
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) [:1.6.0_21]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) [:1.6.0_21]
at java.lang.Thread.run(Thread.java:619) [:1.6.0_21]
{code}
Note that the server startup continues and starts up fine even with this error.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 7 months
[JBoss JIRA] Created: (JBEE-84) Release EJB 3.1 APIs which includes a change to the jax-rpc dependency (only)
by Shelly McGowan (JIRA)
Release EJB 3.1 APIs which includes a change to the jax-rpc dependency (only)
-----------------------------------------------------------------------------
Key: JBEE-84
URL: https://issues.jboss.org/browse/JBEE-84
Project: JBoss JavaEE APIs
Issue Type: Release
Reporter: Shelly McGowan
Assignee: Shelly McGowan
There is a jax-rpc release now available in the JBoss Java EE API specs project:
The EJB 3.1 pom has been changed to replace the dependency:
<dependency>
<groupId>javax.xml</groupId>
<artifactId>jaxrpc-api</artifactId>
<version>1.1</version>
</dependency>
with:
<dependency>
<groupId>org.jboss.spec.javax.xml.rpc</groupId>
<artifactId>jboss-jaxrpc-api_1.1_spec</artifactId>
<version>1.0.0.Final</version>
<scope>provided</scope>
</dependency>
Therefore, a 1.0.1 release will be done for consideration of inclusion in AS 7 to minimize incorrect transitive dependencies.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 7 months