I usually enclose my actions code with try catch and shove in a ex.printStackTrace and then rethrow the exception again. Its a lot more helpful than the meaningless errors tomcat gives, and saves fooling round with log files. (At the end of development though such things should be removed!) Im a big fan of nested exceptions, recursion, and longwinded code buried under many layers of function calls. Some of my (nested) stacktraces are 10 pages long. All good clean fun ;-)
-----Original Message----- From: Galbreath, Mark [mailto:[EMAIL PROTECTED]] Sent: Friday, October 11, 2002 21:41 To: 'Struts Users Mailing List' Subject: RE: Error message - not sure of meaning or significance. Learn the mystical art of "System.out.println()." :-( -----Original Message----- From: Ryan Cuprak [mailto:[EMAIL PROTECTED]] Sent: Friday, October 11, 2002 9:33 AM BTW: How do I get exception traces for servlet errors. I am trying to track down a "servlet exception" in one of my tiles - all I get on the page is a "servlet exception and the path to the tile (jsp page). Looking through the logs in jboss I don't see any exception trace. I am not sure if the above error is related. -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]> -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
