One thing I do to help debugging: I put all method code (including all variable declarations) in a try block, catch Throwable, and write a stack trace to standard error.
Scott --- Andrew Trieger <[EMAIL PROTECTED]> wrote: > yeah, that is a good idea. The servlet.jar I > compiled against was the same for all tests > as I forgot to change it, which is the servlet.jar > in tomcat4.0. So in theory Iplanet > could have a problem with that, but: > > 1. the test fails in tomcat as well as soon as I add > the SOAPContext arg to the method. > 2. the messaging works fine in iplanet if I just > dont ask for the SOAPContext in the > helloworld method... it was accidently compiled > against the wrong servlet.jar which I'll > fix and retry and doubt will fix it. > > any other ideas?? > > you're correct, I'm not getting any exceptions that > spew to stdout, in tomcat I watch > catalina.out where my _log(blabla) messages go > (System.out.println()) and all I see is > the constructor is called and returns and the first > _log message of my helloworld method > is never printed, nor any errors. just a fault > returned to the xml client. > > Thanks, Drew > __________________________________________________ Do You Yahoo!? Yahoo! Tax Center - online filing with TurboTax http://taxes.yahoo.com/