Hello, I am happy that this subject is clear now :) According some other discussions I had, it seems that there is 2 possibilities:
- Either the WS stack provides this kind of behavior - Or it is up to the end point service developer to make this behavior happen I am still confused and so still waiting for some clarifications regarding this topic ... Best Regards. From: Stadelmann Josef [mailto:josef.stadelm...@axa-winterthur.ch] Sent: mardi 7 août 2012 13:41 To: java-user@axis.apache.org Subject: AW: @OneWay interpretation and HTTP binding 100% clear, thanks Von: COURTAULT Francois [mailto:francois.courta...@gemalto.com] Gesendet: Dienstag, 31. Juli 2012 14:21 An: java-user@axis.apache.org<mailto:java-user@axis.apache.org> Betreff: RE: @OneWay interpretation and HTTP binding Hello Josef, I already know that. My goal is not to test the behavior of Web Service stack. For example, I have tested the following behavior stacks against @OneWay: - Metro/Glassfish - CXF - Weblogic Sorry I haven't enough time to test Axis 2 right now but I promise I will do so ;-) And I have seen some differences :( So, my goal is to see whether or not, a Web Service stack is compliant to the spec or not. This is why I want to know if it is mandatory or not (this is the question), for a Web Service stack, per spec, that "a oneway method returns the thread of control to the calling application prior to executing the actual business method" Is it clear enough this time ? Best Regards. From: Stadelmann Josef [mailto:josef.stadelm...@axa-winterthur.ch] Sent: mardi 31 juillet 2012 13:38 To: java-user@axis.apache.org<mailto:java-user@axis.apache.org> Subject: AW: @OneWay interpretation and HTTP binding Guess you can find that easy. Write a sleep(8*3600*1000) statement into your one way service method. If you get back the thread-of-control at the client after 8 hours only then you know the thread does not return up on delivery of the request but after the method has executed, but this time just without any result because it is a one way service. Josef Von: COURTAULT Francois [mailto:francois.courta...@gemalto.com] Gesendet: Montag, 30. Juli 2012 17:56 An: java-user@axis.apache.org<mailto:java-user@axis.apache.org> Betreff: @OneWay interpretation and HTTP binding Hello guys, I have read the JSR 181 spec and the @OneWay is not clear for me. Just want to have your interpretation.... In the spec, it is said that: "Indicates that the given web method has only an input message and no output. Typically, a oneway method returns the thread of control to the calling application prior to executing the actual business method" What typically means ? Does it mean MUST-SHALL, SHOULD or MAY according to you ? Still about the OneWay what is the HTTP binding for this annotation ? I have seen that some implementation returns a 202. Is it a standard HTTP status code value for OneWay ? Best Regards.
