Hi Andreas,
What do you mean by "But instead of sending a SOAPFault to the
sender the message is further processed by the engine." ?
Do you want engine not to invoke fault flow and send the message ? I
don't think its a good idea. There can be some processing that has to be
done by the handlers in the fault out flow. For example, the admin might
decide to log every fault message. And addressing out handler again
helps you to put the stuff in the msgCtxt to the SOAP message.
So due to that, its not good only to invoke TransportSender, once a
fault is thrown.
-- Chinthaka
Sensen, Andreas (external) wrote:
Hi Ali,
thanks for the quick and detailed response, it helped me a lot!
I have just one followup question which you might have an answer to:
I'd really like to keep the validation in a module. It throws an
AxisFault if an
incoming message is invalid. But instead of sending a SOAPFault to the
sender the message is further processed by the engine.
Do you have any idea why?
Andreas
-----Ursprüngliche Nachricht-----
*Von:* Ali Sadik Kumlali [mailto:[EMAIL PROTECTED]
*Gesendet:* Donnerstag, 23. März 2006 10:54
*An:* [email protected]
*Betreff:* Re: [Axis2] schema validation
Forgot to add sample for 3th item:
public
com.mycompany.service.test.schemas.account.OpenAccountResultDocument
OpenAccount(
com.mycompany.service.test.schemas.account.OpenAccountDocument
param0) throws AxisFault {
validate (param0);
...
}
