Return-Path: Delivered-To: apmail-jakarta-tomcat-dev-archive@apache.org Received: (qmail 96022 invoked from network); 27 Jun 2002 16:19:32 -0000 Received: from unknown (HELO nagoya.betaversion.org) (192.18.49.131) by 209.66.108.5 with SMTP; 27 Jun 2002 16:19:32 -0000 Received: (qmail 26364 invoked by uid 97); 27 Jun 2002 16:19:34 -0000 Delivered-To: qmlist-jakarta-archive-tomcat-dev@jakarta.apache.org Received: (qmail 26264 invoked by uid 97); 27 Jun 2002 16:19:30 -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 26143 invoked by uid 50); 27 Jun 2002 16:19:29 -0000 Date: 27 Jun 2002 16:19:29 -0000 Message-ID: <20020627161929.26126.qmail@nagoya.betaversion.org> From: bugzilla@apache.org To: tomcat-dev@jakarta.apache.org Cc: Subject: DO NOT REPLY [Bug 10291] New: - JASPER fails to cause a fatal translaton error with incorrect taglib imports in the XML view of a JSP page X-Spam-Rating: 209.66.108.5 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=10291 JASPER fails to cause a fatal translaton error with incorrect taglib imports in the XML view of a JSP page Summary: JASPER fails to cause a fatal translaton error with incorrect taglib imports in the XML view of a JSP page Product: Tomcat 4 Version: Nightly Build Platform: All OS/Version: All Status: NEW Severity: Normal Priority: Other Component: Jasper AssignedTo: tomcat-dev@jakarta.apache.org ReportedBy: Ryan.Lubke@Sun.COM The example on page 92 pf the 1.2 spec shows the following: Notice that for all relative URLs 'urn:jsptld:' is prefixed to the URI. However, if just the the relative URI is used without the prefix, JASPER compiles the page and all works ok, but this shouldn't be the case. This is an issue in Jasper2 as well. -- To unsubscribe, e-mail: For additional commands, e-mail: