Hi,
you may (or may not) have noticed my posting some days ago regarding a
problem with Tomcat3.1 and a custom tag library. Since no one solved
this problem, I had to solve it myself. Here's what I found out:
When using a custom tag lib, Tomcat obviously insists on a certain order
of tags in the web.xml file. Tags must appear in this order:
<servlet>
<servlet-mapping>
<taglib>
Any deviation of this order yields an error when calling the JSP page.
The error can easily be reproduced with the web.xml file of the example
webapp provided with tomcat. Re-arranging the order of tags within that
file breaks the "simpletag" example. (The JSP file must be compiled anew
after making the change to view the effect).
Error message:
>Unable to open taglibrary http://java.apache.org/tomcat/examples-taglib :
>Parse Error in the tag library descriptor: Element "web-app" does not allow
>"servlet-mapping" here.
I have only checked for this error in conjuction with tag libs, so I
don't know if it occurs otherwise, too.
Is this a real bug, or is the order of tags in web.xml specified
anywhere (can't imagine that's the case, though)?
cu
Heiko
===========================================================================
To unsubscribe: mailto [EMAIL PROTECTED] with body: "signoff JSP-INTEREST".
Some relevant FAQs on JSP/Servlets can be found at:
http://java.sun.com/products/jsp/faq.html
http://www.esperanto.org.nz/jsp/jspfaq.html
http://www.jguru.com/jguru/faq/faqpage.jsp?name=JSP
http://www.jguru.com/jguru/faq/faqpage.jsp?name=Servlets
