It could be easy if we just hack the Soap11FaultOutInterceptor and
Soap12FaultOutInterceptor
to deal with special exception which is throw from the user
interceptor.
On Tue Dec 27 18:09:51 2011, Son Tung Nguyen wrote:
Hi kobol,
I think you can put a flag in WebserviceContext object and continue the
flow as normally. And in your ws implementation method, you would check for
that flag and return the error code...
But i don't think by doing this all preceding interceptors will be unwind ..
If you use SOAP, SoapFault is much more standard for errors or exceptions
handling ...
2011/12/27 June Kobol<june.ko...@gmail.com>
Hi all,
In such a case, I need to authenticate the user's login information.
Luckily, CXF provides interceptors to deal with SOAP message. I can
implement the function using an interceptor. Generally, if the user is
invalid, then the interceptor may throw a Fault, or a derivative of a
Fault like the SoapFault. But in my program, I cannot throw a fault,
instead of returning an error code which woud be added into soap response
header. In the meantime, the InterceptorChain stops invoking and unwind it.
How can I accomplish mypurpose?
Excepting your reply.
regards,
kobol
--
Willem
----------------------------------
FuseSource
Web: http://www.fusesource.com
Blog: http://willemjiang.blogspot.com (English)
http://jnn.javaeye.com (Chinese)
Twitter: willemjiang
Weibo: willemjiang
