Hi Steve,
[Steve Loughran] wrote;
| I have a misconfigured app that causes axis to generate a 204, but the
axis
| client doesnt handle it (filed bugrep). I dont know what the WS-I stance
is
| on it, as the basic profile says nothing on the subject.
The HTTP 204 (OK) is quite the HTTP specific matter. So, the JAX-RPC
doesn't mention it, or rather, the spec says "The JAX-RPC specification
does not specify how a JAX-RPC runtime system implements one-way RPC mode
in terms of the underlying protocol and transport."
However, the spec gives us the directions how the runtime implements
one-way RPC mode with the general words as well. The key points of
suggestions are three things;
1) The runtime provides 'invokeOneWay' method for one-way RPC mode.
2) The client *MAY* handle the HTTP response with either success or
error code (but with no entity-body content).
3) The JAX-RPC client runtime system *MAY* achieve non-blocking behavior
by pipelining multiple HTTP requests without waiting for responses.
Please pay attention to the word of 'MAY' of 2) and 3), it means that
the description is a case-by-case approach. And the current impl of AXIS
might have chosen '3)' as the direction.
The described above is just for the client side point of view. In this
matter, we have to think it over with reviewing two specifications, HTTP
and JAX-RPC.
I'd like to continue this thread on your bugrep; Bug#18024, if there're
no problems with you.
Best Regards,
Toshi (Toshiyuki Kimura) <[EMAIL PROTECTED]>
R&D Headquarters
NTT DATA Corporation
-----Original Message-----
From: Steve Loughran [mailto:[EMAIL PROTECTED]
Sent: Friday, March 21, 2003 4:20 AM
To: [EMAIL PROTECTED]
Subject: Re: How to return HTTP 204 on Document perform()?
----- Original Message -----
From: "Toshiyuki Kimura" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Wednesday, March 19, 2003 20:47
Subject: Re: How to return HTTP 204 on Document perform()?
> | In some cases I need to return HTTP 204 (OK) with no message body.
>
> Why do you need that ?
>
> You might get the result specified above if you do the followings;
> - create a Web service with 'no response'
> [ ex) 'void perform(Document in)']
> - deploy the service as the 'One-way' RPC Mode
>
> However, I guess that AXIS or the other impl of the JAX-RPC runtime
> don't support the behavior. Additions, your original request is a
> dynamically change of the behavior with just 'return null'. I believe
> this is not allowed. Because if it's allowed, it means the interface
> between 'server' and 'client' is flexible.
I have a misconfigured app that causes axis to generate a 204, but the axis
client doesnt handle it (filed bugrep). I dont know what the WS-I stance is
on it, as the basic profile says nothing on the subject.
