Hi, We have two JSP documents a.jsp and b.jsp. Suppose that some custom library is defined correctly under the prefix "x". There is a tag library validator associated with the TLD. The same bug is observed in Tomcat 5 while it is working on Tomcat 4. ---- a.jsp ----- <?xml version="1.0" encoding="UTF-8"?> <jsp:root version="2.0" xmlns:jsp="http://java.sun.com/JSP/Page" xmlns:x="http://some/tld" > <jsp:directive.include file="b.jsp"/> </jsp:root> ---- b.jsp ---- <?xml version="1.0" encoding="UTF-8"?> <jsp:root version="2.0" xmlns:jsp="http://java.sun.com/JSP/Page" > <x:doAction/> </jsp:root> When I try to request a.jsp i receive this exception: org.apache.jasper.JasperException: b.jsp(%row%,%column%) The prefix "x" for element "x:doAction" is not bound. But when I add the namespace to the jsp:root of the b.jsp the validator of the taglibrary complains with: Validation error messages from TagLibraryValidator for trx null: org.xml.sax.SAXParseException: Attribute "x" bound to namespace "http://www.w3.org/2000/xmlns/" was already specified for element "jsp:root". This is against JSP 2.0, 2.1 specification: JSP.10.3.5 Collective Application of Inclusion Semantics. This makes inclusion of JSP documents with custom tag libraries that validate the XML view impossible. Best regards, Todor Mollov
*** Bug 35252 has been marked as a duplicate of this bug. ***
Created attachment 19315 [details] Patch to update host-manager webapp to use servlet 2.4 xsd
Created attachment 19316 [details] Patch to update servlets-examples webapp to use servlet 2.4 xsd
Very weird...I posted a comment to 40507 and then when I went to post patches I somehow got punted to this bug without realizing it. The patches are for 40507, not this bug. Sorry for the dupes.
40507 has been fixed, using the patches you sent in Chris -- thanks.
This works for me with the latest 5.5.x code as well as trunk.