Bug 35114 - Jasper JSPC does not support a failonerr from Ant
Jasper JSPC does not support a failonerr from Ant
Status: RESOLVED FIXED
Product: Tomcat 5
Classification: Unclassified
Component: Jasper
5.5.7
Other other
: P2 normal (vote)
: ---
Assigned To: Tomcat Developers Mailing List
:
Depends on:
Blocks:
  Show dependency tree
 
Reported: 2005-05-28 17:07 UTC by ziweth
Modified: 2005-07-21 15:24 UTC (History)
0 users



Attachments
Implementation of "failonerror" option for JspC when used as an Ant task. (528 bytes, patch)
2005-05-28 19:07 UTC, ziweth
Details | Diff

Note You need to log in before you can comment on or make changes to this bug.
Description ziweth 2005-05-28 17:07:50 UTC
When using org.apache.jasper.JspC as a taskdef Ant tag, if there is a failure 
in the compilation the whole compilation aborts.

Although in some working environments it is required to stop the whole process 
after the first error, there are cases where it is needed to have the whole 
list of errors instead of stopping at the first one.

A typical case is when migrating from WebLogic to JBoss. WebLogic's JSPC 
forgives so much that develpers do not notice they are entering faulty JSP 
expressions. When compiling with Jasper for migration it is needed to be able 
to get all the errors to distribute the job among the developers.

I recommend a "failonerr" capability to JspC and modify the unconditional re-
throw of exceptions catched by JspC.execute().
Comment 1 ziweth 2005-05-28 19:07:00 UTC
Created attachment 15195 [details]
Implementation of "failonerror" option for JspC when used as an Ant task.

This patch was done for tomcat-5.5.7.
Comment 2 Yoav Shapira 2005-07-21 23:24:46 UTC
Implemented.  Thanks for the idea and contribution.  Next time, please use a
diff -u format.