Hi,
I don't think there's any oneway confirmation.
If operation have fault message, then this operation couldn't be
oneway, oneway means no output, no fault, and your client doesn't
care what will happen after send out the request, that's the expected
oneway behavior.
As you already know, if your operation have fault but no output, then
your client still get chance to have some fault back.
Freeman
On 2011-5-27, at 下午4:34, ext2 wrote:
Hi:
Recently I encounter a web-service which operation contains only input
message and fault message;
It may looks like:
<operation>
<input message....>
<fault message ../>
</operation>
If the service execute successful, a http ok response will returned;
And if
it failed, a soap-fault will be returned;
And now we need know if server's result is successful or failure at
client
side.
But cxf will never receive the failure response from service, as
cxf use
fire-forget mechanism to deal with one-way operation by default.
So I am wondering if cxf support some one-way confirm feature? If so
client
could confirm whether server successful or failed.
Thanks any suggestion;
---------------------------------------------
Freeman Fang
FuseSource
Email:[email protected]
Web: fusesource.com
Twitter: freemanfang
Blog: http://freemanfang.blogspot.com
Connect at CamelOne May 24-26
The Open Source Integration Conference
