Bug 19049 - Nested Exceptions result in confusing error messages
Summary: Nested Exceptions result in confusing error messages
Status: RESOLVED FIXED
Alias: None
Product: Tomcat 4
Classification: Unclassified
Component: Jasper 2 (show other bugs)
Version: Nightly Build
Hardware: Other All
: P3 major (vote)
Target Milestone: ---
Assignee: Tomcat Developers Mailing List
URL: http://p1.selectacast.net/~jks/pci-pa...
Keywords:
Depends on:
Blocks:
 
Reported: 2003-04-15 23:30 UTC by Joseph Shraibman
Modified: 2004-11-16 19:05 UTC (History)
1 user (show)


Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Joseph Shraibman 2003-04-15 23:30:36 UTC 
Just reusing the message from the nested Exception loses the context of the
message.  This is making it impossible to debug certain Errors.  For example
"java.lang.NoClassDefFoundError: com/x/y/ClassName" turns into:
"javax.servlet.ServletException: com/x/y/ClassName" which is much less helpful.
 This patch is just the first step, the second is to have the dynamically
generated error page unnest all levels of Throwables, right now it just unnests one.
Comment 1 Mark Thomas 2004-04-09 16:44:16 UTC 
This patch has been committed to TC4 and TC5.