Hi, that didn't work for me. :( Is there any chance to get the soap message that caused the exception so that I can log it to my log-file or parse it for more detailed error-codes in my application? By the way, I don't have a fix endpoint.
Kind Regards, Tobse -- View this message in context: http://cxf.547215.n5.nabble.com/Re-Exception-in-webservice-communication-How-to-get-additional-informations-tp5744151p5744209.html Sent from the cxf-user mailing list archive at Nabble.com.
