I find CXF to be very easy to set up and use to create web services clients and servers. And so now I'm moving on to testing my client under real-world failure conditions. For example, the server is down or otherwise unreachable.
I can catch the exception and extract the descriptive information that I need. That works fine. But CXF still continues to emit the entire exception call stack trace to stderr. I could just direct all JVM stderr to /dev/null, but that's kind of a brute-force overkill workaround. Is there some way to suppress (or capture and not emit) that stderr exception stack trace information? I've looked at the docs and samples for interceptors, but they all seem to focus on detecting servers that return improperly generated responses... which I can do fine. And all of the questions I can find are people running into this kind of error but not expecting it... I definitely am expecting it because I willfully ran the client against a non-existent server to test the client's error detection/handling. I just need to suppress the stderr stack trace. -- View this message in context: http://cxf.547215.n5.nabble.com/Capturing-stderr-from-a-CXF-client-s-exceptions-tp4518653p4518653.html Sent from the cxf-user mailing list archive at Nabble.com.
