You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tomcat.apache.org by bu...@apache.org on 2003/06/03 19:32:12 UTC
DO NOT REPLY [Bug 18967] -
NullPointerException instead of error message when running JspC
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://nagoya.apache.org/bugzilla/show_bug.cgi?id=18967>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=18967
NullPointerException instead of error message when running JspC
------- Additional Comments From cokelley@alumni.princeton.edu 2003-06-03 17:32 -------
This bug is especially serious since it can hide errors that are not
reproducible when precompilation is off. For instance, I added a taglib to my
project. Without precompilation, I get no errors. When I precompile, I get an
NPE with no explanation.
After I realized that the taglib was the problem, I added another step to my
build process (to pre-pre-compile the tags). However, since some time had
passed since I added the tags, it wasn't obvious.
In other words, this NPE hides errors that are difficult to fix (the "don't
precompile" workaround isn't always available) and makes precompilation risky
from a development standpoint.
---------------------------------------------------------------------
To unsubscribe, e-mail: tomcat-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tomcat-dev-help@jakarta.apache.org