When you get an exception in a JSP tag, you have quite a bit of unrolling to do. The stack trace just shows you the stack of the last exception that was thrown. If you want to know the "root cause" you need to "unroll" it. The most obvious case is what tomcat for intance does when it shows you an exception and the root cause. Now, if you write a tag you can only throw a JspException cause that's what the method's signature tells you, you can throw. So you wrap the tag in the JSPException and throw it.
When we print an exception, we unroll all the exceptions so that we can figure out the details. This works fine, except that it take a loooong time, 15 seconds, and more. To make things even worse, I'm looking at an XSL exception, and they're doing something similar in their code, and I'm ending up with an exception that's over 1400 lines. I'm not worried about the length, but waiting 15 seconds or more can be a pain. Anyone's run into this problem. Any brilliant suggestions? Dror -- Dror Matalon Zapatec Inc 1700 MLK Way Berkeley, CA 94709 http://www.zapatec.com =========================================================================== To unsubscribe: mailto [EMAIL PROTECTED] with body: "signoff JSP-INTEREST". For digest: mailto [EMAIL PROTECTED] with body: "set JSP-INTEREST DIGEST". Some relevant FAQs on JSP/Servlets can be found at: http://archives.java.sun.com/jsp-interest.html http://java.sun.com/products/jsp/faq.html http://www.esperanto.org.nz/jsp/jspfaq.jsp http://www.jguru.com/faq/index.jsp http://www.jspinsider.com
