[
https://jira.jboss.org/jira/browse/JBWS-2739?page=com.atlassian.jira.plug...
]
Alessio Soldano commented on JBWS-2739:
---------------------------------------
This behaviour has been removed in 3.2.1, the reason being that to implement proper keep
alive connections reuse, we need to check http response headers, even for simple http
200/204 messages.
Make OneWay operation non-blocking (client side)
------------------------------------------------
Key: JBWS-2739
URL:
https://jira.jboss.org/jira/browse/JBWS-2739
Project: JBoss Web Services
Issue Type: Feature Request
Security Level: Public(Everyone can see)
Components: jbossws-native
Reporter: Alessio Soldano
Assignee: Alessio Soldano
Fix For: jbossws-native-3.2.0
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.
On client side, we'd need to fork thread for the call, whenever allowed (cfr.
maintain session prop)
--
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