Hi,
You need to do some work on the ClientFaultConverter to turn the
ApplicationFault to the exception which the client proxy can be thrown.
<ApplicationFault xmlns="urn:mysystems.com:2004-05.Faults"
xmlns:i="http://www.w3.org/2001/XMLSchema-instance";>
<Type>System.NullReferenceException</Type>
</ApplicationFault>
On Thu Dec 15 19:29:38 2011, simran wrote:
Thanks for your reply Willem...
Your blog shows when example when you know what type of exception will be
thrown, but in our case the webservice is throwing UndeclaredThrowable
exception and we have not rights to make any change in customer's
webservice. Just to handle everything on client side (map/supress etc)...
Can we cast undeclaredthrowable to soapexception or other type and then
fetch the information from that?
or any other way to handle this type of case?
Thanks a lot...
--
View this message in context:
http://cxf.547215.n5.nabble.com/Customized-SOAP-faults-tp5075038p5077208.html
Sent from the cxf-user mailing list archive at Nabble.com.
--
Willem
----------------------------------
FuseSource
Web: http://www.fusesource.com
Blog: http://willemjiang.blogspot.com (English)
http://jnn.javaeye.com (Chinese)
Twitter: willemjiang
Weibo: willemjiang
