Hello
On 05/08/2010 14:24, Willem Jiang wrote:
CXF WebFaultOutInterceptor did almost same thing as you do (checking
the annotation and write the detail info)
Basically you just need to throw the exception out in your processor.
I'm just wondering why it doesn't work for you case.
That's because WebFaultOutInterceptor calls the getFaultInfo method on
the exception. And, even thought it sounds weird, the default Exceptions
generated by the CXF codegen plugin leaves the variable returned by
getFaultInfo to null.
Hence, getFaultInfo returns null and the WebFaultOutInterceptor doesn't
have anything to analyze.
That's why I've done the workaround that analyzes the @WebFault
annotations as well.
Cheers
S. Ali Tokmen
[email protected]
Office: +33 4 76 29 76 19
GSM: +33 66 43 00 555
Bull, Architect of an Open World TM
http://www.bull.com
