Return-Path: Delivered-To: apmail-jakarta-tomcat-dev-archive@apache.org Received: (qmail 67243 invoked from network); 3 Jun 2003 17:30:16 -0000 Received: from exchange.sun.com (192.18.33.10) by daedalus.apache.org with SMTP; 3 Jun 2003 17:30:16 -0000 Received: (qmail 6473 invoked by uid 97); 3 Jun 2003 17:32:31 -0000 Delivered-To: qmlist-jakarta-archive-tomcat-dev@nagoya.betaversion.org Received: (qmail 6466 invoked from network); 3 Jun 2003 17:32:31 -0000 Received: from daedalus.apache.org (HELO apache.org) (208.185.179.12) by nagoya.betaversion.org with SMTP; 3 Jun 2003 17:32:31 -0000 Received: (qmail 66203 invoked by uid 500); 3 Jun 2003 17:29:58 -0000 Mailing-List: contact tomcat-dev-help@jakarta.apache.org; run by ezmlm Precedence: bulk List-Unsubscribe: List-Subscribe: List-Help: List-Post: List-Id: "Tomcat Developers List" Reply-To: "Tomcat Developers List" Delivered-To: mailing list tomcat-dev@jakarta.apache.org Received: (qmail 66133 invoked from network); 3 Jun 2003 17:29:57 -0000 Received: from exchange.sun.com (192.18.33.10) by daedalus.apache.org with SMTP; 3 Jun 2003 17:29:57 -0000 Received: (qmail 6439 invoked by uid 50); 3 Jun 2003 17:32:13 -0000 Date: 3 Jun 2003 17:32:12 -0000 Message-ID: <20030603173212.6438.qmail@nagoya.betaversion.org> From: bugzilla@apache.org To: tomcat-dev@jakarta.apache.org Cc: Subject: DO NOT REPLY [Bug 18967] - NullPointerException instead of error message when running JspC X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT . 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