Hello All,
To the point, how can I catch transport error (eg: 404 error, host not
found, etc) as a message fault inside a custom handler.

I am creating a custom logging module to logs all transaction messages to
database.
The design & example is very clear and now I can log outbound, inbound,
in/out faults messages to the database.

But I am facing a problem where there is a transport error, its not going to
any of my logging handler/phase, and so I can't log any transport error, is
that correct?
It is just thrown as an AxisFault as parameter
of AxisCallback.onError(Exception ex) (I am doing non blocking invocation
here).
Is there any reason why it is not send back as fault message, and processed
through all inFaultFlow?

Regards,
Sukma

Reply via email to