[
https://jira.jboss.org/jira/browse/JBWS-2406?page=com.atlassian.jira.plug...
]
Darran Lofthouse commented on JBWS-2406:
----------------------------------------
I do not see how that automatically makes this feature impossible, all I see is some
additional requirements.
So when 'proxy.callOneWayMethod(); ' returns the client needs the session cookie
so this suggests the implementation needs to be on the server side and needs to return the
HTTP response before the business method begins.
The only other restriction that this would imply is that the HTTP session would need to be
created before the first one-way business method.
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