Why don't you trace the soap message on TCP level using a tool like ngrep or ethereal?
On Fri, 2005-04-08 at 16:05 +0530, Venkat Reddy wrote: > You can write a tiny logging handler to do something like - > > Transformer transformer = TransformerFactory.newInstance().newTransformer(); > StringWriter stringWriter = new StringWriter(128); > transformer.transform(new DOMSource(env), new StreamResult(stringWriter)); > StringBuffer buffer = stringWriter.getBuffer(); > > - venkat > > On Apr 8, 2005 3:55 PM, Jin-Ha Tchoe <[EMAIL PROTECTED]> wrote: > > Hi, > > > > we use Axis 1.2 Alpha with Tomcat 4.0.3 and Castor 0.95 for a > > SOAP-Service. Sometimes we have customers you are not accustomed to SOAP > > and have lots of problems using our Service. The problems range from > > simple typos and wrong namespaces to forgetting the SOAP-Envelope. > > > > Whenever Axis and Castor are unable to determine the right Service or > > (Un-)marshal the message, the most the customers can see (and therefore > > us) is a simple AxisFault. Unfortunately that does not help us see what > > exactly is going wrong. So, is there a way for Axis to dump the complete > > raw SOAP Envelope _before_ doing its work, so that we can something? > > > > Many thanks in advance, > > > > Jin-Ha Tchoe > > -- > > Jin-Ha Tchoe <[EMAIL PROTECTED]> > > > > > > -- Peter Maas Application Architect / Streaming Noterik Multimedia BV Prins Hendrikkade 120 1011 AM Amsterdam The Netherlands Tel: +31 (0)205929966 Fax: +31 (0)204688405 Gsm: +31 (0)616096324 Web: www.noterik.nl -------------------------------------- Take a look at our streaming solutions: http://www.streamedit.com/demo.html Get firefox: http://www.mozilla.org/products/firefox/ --------------------------------------- :wq!
