DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT <http://nagoya.apache.org/bugzilla/show_bug.cgi?id=13149>. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE.
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=13149 Client requires servlet.jar [EMAIL PROTECTED] changed: What |Removed |Added ---------------------------------------------------------------------------- Status|REOPENED |RESOLVED Resolution| |WORKSFORME ------- Additional Comments From [EMAIL PROTECTED] 2002-10-10 16:25 ------- OK, I've pulled the 1.0 build and attempted to duplicate this problem. It's working just fine for me. My classpath: .;axis.jar;wsdl4j.jar;saaj.jar;jaxrpc.jar;commons-discovery.jar;commons- logging.jar;log4j-core.jar;junit.jar;xerces.jar My client works exactly as expected. If I enable DEBUG (log4j), I do see the exception in the log as a DEBUG message: java.lang.NoClassDefFoundError: javax/servlet/ServletConfig This *IS* expected behavior! Hmm.. let's see what happens when I drop log4j out of the picture and let it fall back to a simpler logger... Looks great. Debug message isn't being shown. SOO... Can we drop back to an assumption that those who are having problems with this have DEBUG enabled with whatever logger they are using, and the logger isn't displaying the message level? As usual, reopen if necessary... PLEASE provide details on your classpath, output (where you found it: screen, log file, ?), etc.
