Nelson, You can give them a client-config.wsdd (with logging handler enabled) which the clients can place in the directory from where they are running their command line soap client. Just add a logging handler in the global section so that it gets enabled for all communication in your environment and then send them the wsdd by email :) They won't have to do anything else other than drop the file.
-- dims On Thu, 7 Oct 2004 17:18:44 -0700, Nelson Minar <[EMAIL PROTECTED]> wrote: > What's the absolute simplest way for a SOAP client written with Axis > to capture the XML sent and received to an SSL service and display it > for debugging purposes? I'm looking for something I can use for user > support, so it needs to be really easy. > > Here are the ways I know to capture the XML and the drawbacks: > > tcpmon (or other packet sniffing approaches like SOAPScope): > Doesn't work for SSL. (SOAPScope has this ability but it's not > readily available.) > > SOAP Monitor: > Requires special access to the server > > logging configuration: > Requires user understands how to configure log4j / java.util.logging / > whatever on the client. This seems fairly complicated. > > What would be ideal for me is a single static method call, something > like "org.apache.axis.Foo.dumpXmlToStderr(true);". > > More options here: > http://nagoya.apache.org/wiki/apachewiki.cgi?AxisProjectPages/MonitorSOAPTraffic > -- Davanum Srinivas - http://webservices.apache.org/~dims/
