At 12:58 PM 9/13/2005, you wrote:
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.
What I failed to explicitly point out is that the first argument of the
generated call has changed.
javax.servlet.jsp.tagext.JspTag is new has of JSP 2.0
(see
http://java.sun.com/j2ee/1.4/docs/api/javax/servlet/jsp/tagext/JspTag.html)
Any tags that are not compiled against the J2EE 1.4 libraries appear to not
be useable with the latest version of JasperC.
- clark.
g
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
