Bug 31248 - Problem with TagAttributeInfo
Summary: Problem with TagAttributeInfo
Status: RESOLVED INVALID
Alias: None
Product: Tomcat 5
Classification: Unclassified
Component: Servlet & JSP API (show other bugs)
Version: 5.0.26
Hardware: PC Linux
: P3 blocker (vote)
Target Milestone: ---
Assignee: Tomcat Developers Mailing List
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2004-09-15 16:05 UTC by Gleise Segatto
Modified: 2004-11-16 19:05 UTC (History)
0 users



Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Gleise Segatto 2004-09-15 16:05:30 UTC
I'm using Tomcat 4.1 to hosting my client's applications and I was testing the
Tomcat 5.0 on another server.
Applications developed with Struts and Webwork had problems with the
javax.servlet.jsp.tagext.TagAttributeInfo.
The constructor of this class is different from Tomcat4.1's JSP API to
Tomcat5.0's JSP API.
I believe that the old constructor must have been kept.

------------------------------
java.lang.NoSuchMethodError:
javax.servlet.jsp.tagext.TagAttributeInfo.<init>(Ljava/lang/String;ZLjava/lang/String;ZZ)V
	org.apache.jasper.compiler.TagLibraryInfoImpl.createAttribute(TagLibraryInfoImpl.java:568)
	org.apache.jasper.compiler.TagLibraryInfoImpl.createTagInfo(TagLibraryInfoImpl.java:401)
	org.apache.jasper.compiler.TagLibraryInfoImpl.parseTLD(TagLibraryInfoImpl.java:248)
	org.apache.jasper.compiler.TagLibraryInfoImpl.<init>(TagLibraryInfoImpl.java:162)
	org.apache.jasper.compiler.Parser.parseTaglibDirective(Parser.java:418)
(...)
------------------------------
Comment 1 Yoav Shapira 2004-09-15 16:09:20 UTC
Going from 4.1 to 5.0 is a major version change.  We do not guarantee binary 
compatibility between these versions.  You should at a minimum always make sure 
your apps compile against the new version.  
Comment 2 Tim Funk 2004-09-15 16:18:39 UTC
If you pre-compiled using tomcat 4 and wish to deploy on 5, you must copy tomcat
4's jasper runtime to the WEB-INF/lib dir.