axis-java-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Stadelmann Josef" <josef.stadelm...@axa-winterthur.ch>
Subject AW: @OneWay interpretation and HTTP binding
Date Tue, 31 Jul 2012 11:38:05 GMT
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.COURTAULT@gemalto.com] 
Gesendet: Montag, 30. Juli 2012 17:56
An: 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.


Mime
View raw message