Richard Opalka commented on JBWS-2406:
The first potential problem I can see is the following usecase required by jaxws spec:
See test: org.jboss.test.ws.jaxws.jbws1733 to see how session maintain property works.
Also note the following:
As you can see this feature is tested in TCK5 as well thus I'm affraid it won't be
possible to fix this issue without breaking TCK :(
Another option you have is to create hack checking whether SESSION_MAINTAIN_PROPERTY is
set to true and in such case don't do this one way methods invocations optimization.
Make OneWay Operations Non-Blocking
Project: JBoss Web Services
Issue Type: Feature Request
Security Level: Public(Everyone can see)
Affects Versions: jbossws-native-3.0.4
Reporter: Darran Lofthouse
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
- 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:
For more information on JIRA, see: http://www.atlassian.com/software/jira