RE: Debugging SOAP Application

[Chris Means]

Title: Message

Michael,   The simplest approaches are to use the System.out.println/System.err.println methods.   Another option, is to step through the code....   Test your method calls by calling them inside the main method of your Java/SOAP object, then run it like a normal Java object, rather than deal with the complexity of writting both the client and the server code.  This way you can test the server side code, before you write the client code (SOAP client that is).  So if/when you start running into problems on the client side, you can be reasonably confident that they're client side problems, and not a bug on the server side <g>.   HTH.   -Chris -----Original Message----- From: Michael Timpe [mailto:[EMAIL PROTECTED]] Sent: Saturday, January 05, 2002 8:07 AM To: [EMAIL PROTECTED] Subject: Re: Debugging SOAP Application Thank you for this hiint.   But sorry, I'm really new in these topics - so I don't understand what you are meaning with "usual methods of debugging servlets".   Do you know any good tutorials on debugging Servlets and JSP on Sun's Java-Site.   Thanx a lot for your help.   Michael       ----- Original Message ----- From: William Brogden To: [EMAIL PROTECTED] ; 'Michael Timpe' Sent: Saturday, January 05, 2002 3:02 PM Subject: RE: Debugging SOAP Application In addition to the usual methods for debugging servlets, it is handy to be able to snoop on the exact text of SOAP messages. I wrote a utility for this that you can download from:   http://www.lanw.com/books/javasoap/ -----Original Message----- From: Michael Timpe [mailto:[EMAIL PROTECTED]] Sent: Saturday, January 05, 2002 4:23 AM To: SOAP Mailing List Subject: Debugging SOAP Application Hi SOAPies!   How is it possible to debug a SOAP-Application?   I am using NetBeans 3.3 as IDE and Tomcat 4.0 for driving soap.     Greetings   Michael     -------------------------------------------------------------------------------- Michael Timpe Melchiorstr. 24 50670 K�ln eMail: [EMAIL PROTECTED]