Hello. I am currently having a problem with WS security currently being handled in a different message string.
I have a related question that is different enough to merit its own subject. I keep getting a soap fault (presumably from the WSS4JInInterceptor in the service, when calling with a client: <soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/";><soap:Body><soap:Fault><faultcode>soap:Client</faultcode><faultstring>Security processing failed.</faultstring></soap:Fault></soap:Body></soap:Envelope> This is not all that informative. Is there any way to configure the interceptors to relay whatever exception caused them to fail back through the soap:Fault message so you can actually see the parent exception in writing? Is this already being logged somewhere else? I haven't been able to find it. Come to think of it. I have yet to find a comprehensive list of configuration options for these interceptors. Does anyone know where to find one? -Thank you -Martin -- View this message in context: http://cxf.547215.n5.nabble.com/Debugging-in-CXF-security-WSS4JInInterceptor-WSS4JOutInterceptor-returning-exceptions-through-service-tp5534346p5534346.html Sent from the cxf-user mailing list archive at Nabble.com.
