Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 89198 - "Unhandled exception" on every exception throwing method
Summary: "Unhandled exception" on every exception throwing method
Status: CLOSED FIXED
Alias: None
Product: WTP Source Editing
Classification: WebTools
Component: jst.jsp (show other bugs)
Version: 0.7   Edit
Hardware: PC Windows 2000
: P3 normal with 1 vote (vote)
Target Milestone: 1.0 M6   Edit
Assignee: Phillip Avery CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2005-03-27 18:11 EST by chily CLA
Modified: 2006-09-25 02:42 EDT (History)
0 users

See Also:

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 chily CLA 2005-03-27 18:11:50 EST 
WTP version: 1.0 M3

Hello,
the JSP source page editor marks every exception throwing method call in the 
page with "Unhandled exception of type ...", although the JSP servlet method 
has its own exception handling (e.g. redirecting to <%@ page errorPage="..."%>).

Chily
Comment 1 chily CLA 2005-03-28 14:35:24 EST 
Meanwhile I saw some cases where there are no error marks in the JSP at all.
I couldn't find out so far, what makes the difference for a page full of error 
marks and a page with none.

But here a simple example of a page with an error mark for the call of "bla();":

<%!
void bla() throws Exception {}
%>
<%
bla();
%>
Comment 2 David Williams CLA 2005-06-15 01:21:49 EDT 
Changed Version field given new release numbering.
Comment 3 Phillip Avery CLA 2005-07-11 16:13:07 EDT 
I think this has been fixed when we changed the JSPTranslation to follow the
spec better, user code is now wrapped in try/catch similar to how Jasper translates.

Please verify on a more recent build.
Comment 4 Phillip Avery CLA 2005-07-12 20:25:24 EDT 
updating milestone to M6.
Comment 5 David Williams CLA 2006-09-25 02:42:33 EDT 
This bug was moved to 'closed' state, since it is so old and it is assumed really fixed and no longer useful or need further attention. Feel free to re-open, or open a new bug, if this semi-automatic processing was done in error.