tomcat-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From bugzi...@apache.org
Subject DO NOT REPLY [Bug 4236] New: - error in translation of tag attribute value, string assigned with ""
Date Wed, 17 Oct 2001 15:16:52 GMT
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://nagoya.apache.org/bugzilla/show_bug.cgi?id=4236>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

http://nagoya.apache.org/bugzilla/show_bug.cgi?id=4236

error in translation of tag attribute value,  string assigned with "" 

           Summary: error in translation of tag attribute value,  string
                    assigned with ""
           Product: Tomcat 4
           Version: 4.0.1 Final
          Platform: Other
        OS/Version: Windows NT/2K
            Status: NEW
          Severity: Critical
          Priority: Other
         Component: Jasper
        AssignedTo: tomcat-dev@jakarta.apache.org
        ReportedBy: mroderic@csc.com


We have upgraded from Tomcat 3.2.2 to 4.0.1 with a very strange effect. Now one 
and only one of our custom tag attributes <name>action</name> is assigned a 
string value including the "". 

FormTag.getAction() returns literally "do.vpms" rather than the string do.vpms. 
I would have expected the "" to cause problems in the Java class since they 
normally need to be escaped but the mutators work correctly. However, "" causes 
a call to HttpServletResponse.encodeURL(action) to create an incorrect action 
URI for our custom form tag. This behavior was actually already apparent in 4.0 
RC1.

We have a work around but this is very strange so I thought I would report it. 
No other attribute is assigned with the "". I think the problem must be related 
to Tomcat. We haven't changed jdk versions (we are using 1.3.1) so the same 
PropertyEditor class is responsible for introspection and assignment of tag 
attribute values. I have also changed the TLD to be JSP1.2 conformant but still 
have the same effect.

I have also reviewed Sun's Tag classes, the JavaBeans Specification, the JSP1.2 
Specification, the JSP1.2 TLD DTD , and Tomcat's reported bugs and have found 
no mention of  'action' being a reserved word (the only possible explanation I 
could come up with).

Looking forward to your feedback!
Mary

Mime
View raw message