[ https://jira.jboss.org/jira/browse/JBWS-2406?page=com.atlassian.jira.plug... ] 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 * ee/w2j/rpc/literal/httpservletmsgctxpropstest/Client.java: requestContext.put(BindingProvider.SESSION_MAINTAIN_PROPERTY, Boolean.FALSE); As you can see above this feature requirement 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. -- 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

[ https://jira.jboss.org/jira/browse/JBWS-2406?page=com.atlassian.jira.plug... ] 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. -- 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

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

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

[ https://jira.jboss.org/jira/browse/JBWS-2406?page=com.atlassian.jira.plug... ] Alessio Soldano updated JBWS-2406: ---------------------------------- Fix Version/s: jbossws-native-3.1.2 -- 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

[ https://jira.jboss.org/jira/browse/JBWS-2406?page=com.atlassian.jira.plug... ] Richard Opalka updated JBWS-2406: --------------------------------- Assignee: (was: Richard Opalka) -- 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

[ https://jira.jboss.org/jira/browse/JBWS-2406?page=com.atlassian.jira.plug... ] Alessio Soldano updated JBWS-2406: ---------------------------------- Summary: Make OneWay Operations Non-Blocking (server side) (was: Make OneWay Operations Non-Blocking) Description: 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. (This is not an exhaustive list just some of the current suggestions) was: 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) The client side of this has been moved to JBWS-2739 as that's going to the 3.2.0.GA release. -- 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

[ https://jira.jboss.org/jira/browse/JBWS-2406?page=com.atlassian.jira.plug... ] Alessio Soldano updated JBWS-2406: ---------------------------------- Fix Version/s: (was: jbossws-native-3.3.0) -- 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