I understand the words "Now one of my tests fails" to mean that you only want this output occasionally to see what's wrong? In that case, the tools I mentioned are the best choice, because they aren't intrusive.
To capture the output as part of the regular unit tests, you should subclass your transport and transport factory to produce that output for you. Jochen On Tue, Apr 13, 2010 at 10:46 AM, Lucio Crusca <lu...@sulweb.org> wrote: >> Use tcpdump, wireshark, or a similar tool. > > Er... it's not me wanting the xml stream, maybe I didn't make it clear > enough... my customer (the one who pays me) asked me a java test suite (not a > *nix script) to produce that kind of output. > > Besides, I suspect that the xmlrpc library uses some kind of OutputStream to > send the xml request, and I would be disappointed if the API gave no > opportunity to change that stream. > > However now I'm going to suggest my customer to use tcpdump, I hope he's in a > good mood... > > -- Germanys national anthem is the most boring in the world - how telling!
