[jbossws-issues] [JBoss JIRA] Commented: (JBWS-2406) Make OneWay Operations Non-Blocking

[Richard Opalka (JIRA)]

    [ https://jira.jboss.org/jira/browse/JBWS-2406?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12439807#action_12439807 ] 

Richard Opalka commented on JBWS-2406:
--------------------------------------

The first potential problem I can see is the following usecase required by jaxws spec:

((BindingProvider)proxy).getRequestContext().put(BindingProvider.SESSION_MAINTAIN_PROPERTY, true);
proxy.callOneWayMethod();
proxy.callReqResMethod();

See test: org.jboss.test.ws.jaxws.jbws1733 to see how session maintain property works.

Also note the following:

[/home/opalka][/home/opalka/svn/tck/tck5/trunk/src/com/sun/ts/tests/jaxws]>grep -r SESSION_MAINTAIN_PROPERTY *
api/javax_xml_ws/BindingProvider/Client.java:	    requestContext.put(BindingProvider.SESSION_MAINTAIN_PROPERTY, new Boolean("false"));
ee/w2j/rpc/literal/httpservletmsgctxpropstest/Client.java:         requestContext.put(BindingProvider.SESSION_MAINTAIN_PROPERTY, Boolean.FALSE);
ee/w2j/rpc/literal/httpservletmsgctxpropstest/Client.java:         requestContext.put(BindingProvider.SESSION_MAINTAIN_PROPERTY, Boolean.TRUE);

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
> -----------------------------------
>
>                 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
>
> 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