I think it is worth it to add the JspWrapperException in lieu of waiting for the next Servlet spec. to further its adoption.
Hiding the original stack trace makes debugging tough. This is especially frustrating to new users. I did this to our copy of Struts last night, and it only took an hour. In six months or a year when everyone is using the latest version of the Servlet spec., it will only take an hour to switch to the new JspException constructor if so desired. BTW I volunteer to make the change. Rick Hightower Director of Development eBlox, Inc. Check out our new website! www.eblox.com Contact Info: eBlox Tucson phone: 520-615-9345 x103 fax: 520-529-5774 Rick's stuff: http://www.eblox.com/people_detail.php?id=52 http://www.geocities.com/rick_m_hightower/ http://www.brainbench.com/transcript.jsp?pid=2351036 -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of Craig R. McClanahan Sent: Friday, November 16, 2001 10:07 AM To: Struts Developers List Subject: Re: Exception handling --- suggestion for improvements ---- (e.g., template tag masks original exception) On Fri, 16 Nov 2001, Rick Hightower wrote: > Date: Fri, 16 Nov 2001 01:20:45 -0700 > From: Rick Hightower <[EMAIL PROTECTED]> > Reply-To: Struts Developers List <[EMAIL PROTECTED]> > To: [EMAIL PROTECTED] > Subject: Exception handling --- suggestion for improvements ---- (e.g., > template tag masks original exception) > > We have been using struts for a good while. We really dig the framework, > but... > > Often times the struts tags catch the original exception (e.g., > ClassCastException), and then throw a JspException; thus, losing the > original stack trace. This hides\masks the original exception. Hiding the > orginal stack trace makes it harder to debug the problem. > In JSP 1.2, the capability to add a root cause exception (the way ServletException does it) was added to JspException, so once we migrate to that platform as a minimum we'll be able to modify Struts to use it. How important is it to deal with this issue in the mean time? Craig -- 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]>
