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=10291>. 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 [EMAIL PROTECTED] changed: What |Removed |Added ---------------------------------------------------------------------------- Status|REOPENED |RESOLVED Resolution| |INVALID ------- Additional Comments From [EMAIL PROTECTED] 2002-07-18 21:50 ------- JSP.5.2.2 has the following: If the 'uri' value is of the form "urn:jsptld:<path>", then the TLD is determined following the mechanism described in section JSP.7.3.2. If the 'uri' value is a plain "uri", then a path is determined by consulting the mapping indicated in web.xml extended using the implicit maps in the packaged tag libraries [...]. I interpret this to say that <path> in "urn:jsptld:<path>" should be interpreted as the TLD resource path directly (without going through any mapping). In the 2nd case, the uri is mapped to the TLD resource path (using the taglib mapping), and only if the uri is not found in the mapping, it is interpreted as the TLD resource path directly. The spec does not seem to impose any constraints on the uri in this case. -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
