[
https://jira.jboss.org/jira/browse/JBWS-2406?page=com.atlassian.jira.plug...
]
Richard Opalka commented on JBWS-2406:
--------------------------------------
We need to check the JAX-WS spec as well for exception handling when there's exception
on server side.
The question is whether such exceptions have to be propagated to client.
Make OneWay Operations Non-Blocking
-----------------------------------
Key: JBWS-2406
URL:
https://jira.jboss.org/jira/browse/JBWS-2406
Project: JBoss Web Services
Issue Type: Feature Request
Security Level: Public(Everyone can see)
Components: jbossws-native
Affects Versions: jbossws-native-3.0.4
Reporter: Darran Lofthouse
Fix For: jbossws-native-3.0.6
Currently the @OneWay operations block while the business logic executes on the server
and does not return a response until processing is complete.
This feature request is to modify one-way operations to be non-blocking.
There are various options to be investigated: -
- As soon as server knows it is a valid message send HTTP response but thread continue
to process.
- Fork a new thread server side to call business method.
- Fork thread client side for the call.
(This is not an exhaustive list just some of the current suggestions)
--
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