At 11:10 AM 9/13/2005, Martin Gainty wrote:
Clark-
Ant has not upgraded the JSPC task for the JSP Servlet 2.0 spec as of yet
to quote
"There are known problems with Tomcat 5.x that won't get fixed in Ant,
please use Tomcat's jspc task instead."
Yup, been there, gotten it to work for a while now.
The real issue seems to be backwards compatibility when generating the java
code for taglibs that are adhering to version 1.1 of the JSP spec while
using the Tomcat 5.5 version of JasperC, which implements the 2.0 spec.
For instance,
using JasperC from Tomcat 4.x (which also required the custom ant config),
the following class would be generated:
private boolean
_jspx_meth_html_img_0(javax.servlet.jsp.tagext.Tag _jspx_th_html_link_0,
javax.servlet.jsp.PageContext pageContext)
throws Throwable
Now, using the Tomcat 5.5 jasperC, you get this class:
private boolean
_jspx_meth_html_link_0 (javax.servlet.jsp.tagext.JspTag _jspx_th_html_html_0,
PageContext _jspx_page_context)
throws Throwable
Now, same jsp, same taglib, same backing jar. The only difference is that
the version of JasperC changed.
The first example adheres to JSP 1.1, the second to JSP 2.0.
But, since the taglib, and its jar, where generated/compiled for jsp 1.1,
you get a "cannot be applied error" since the class hierarchy for the tags
themselves changed with jsp 2.0.
Since Tomcat 5.5 has been out for a year, I can not be the first person to
run into this, so what am I missing?
Thanks,
- clark.,
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
