1. you just need log4j in the classpath where axis.jar can see it. The stack traces are not caused by log4 being missing so much as axis being too verbose
2. the latest CVS version of axis prints a lot less faults 3. the latest docs also cover how to set up log4j to print less http://cvs.apache.org/viewcvs.cgi/~checkout~/xml-axis/java/docs/reference.ht ml#axis_logging ----- Original Message ----- From: <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Monday, January 06, 2003 00:49 Subject: AW: AxisFault or Exception are always printing stack trace BTW a happy new year to all of you!!! Hi Toshi, I ensured to have the log4j (1.2.4) everywhere in classpathes and directories of client and server. For my client thjis does work now. No stacktrace is printed and with this working also my problem with the stopping of the process in handled. If something goes wrong, e.g. no valid database-connection, I throw an AxisFault, can set the FaultCode and with this I know on the client-side whats up. But: In my Tomcat the stacktrace is still printed. I think that means, that on server-side he still does not have the log4j correctly. I read about, that you should place some jars inside the Tomcat/common/lib. But this I would not not like, so I have all the jars in web-inf/lib. Do I have to put log4j to common/lib? If yes, could anybody tell me why? And which jars else are absolutely neede in that directory? thanks in advance Seppo
