In the case of throwing AxisFault (either from WSDoAllReceiver or WS method)
client receives plain soap:Fault without security headers. I can't test it right
now, but I think that it's proper server's behaviour - there is no <faultFlow>
defined! (axis documentation states nothing about this flow - I've found this
in wsdd.dtd on some wiki site).
If that works, it would be very clean and nice solution for the server side.
But then - what about client's view? Is this correct to invoke client's
WSDoAllReceiver defined in <responseFlow> (which happened in my test)
in the case of AxisFault? Shouldn't the client's <faultFlow> be used?
I will see if this works on Monday...
>> Werner: yes, anyhow we need to figure out how this could work
>> with Axis. Seems that we have a problem (or we don't understand)
>> with the Axis SOAP Fault handling.
Maybe proper definition and use of <faultFlow> in .wsdd file will help?
I have to try this approach.
With regards
Grzegorz Grzybek
