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 38797] 5.5.12 and 5.5.15 emit different code on <jsp:getProperty>
Date Wed, 19 Aug 2009 15:55:42 GMT
https://issues.apache.org/bugzilla/show_bug.cgi?id=38797


Rich Naylor <rich.naylor@activevos.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|RESOLVED                    |REOPENED
         Resolution|FIXED                       |


--- Comment #7 from Rich Naylor <rich.naylor@activevos.com> 2009-08-19 08:55:38 PDT
---
(In reply to comment #6)
> This has been fixed in 5.5.x and will be in 5.5.28 onwards

I believe the code introduced org.apache.jasper.compiler.Generator has missed a
point and introduced another issue. If you look at the changes made to
GeneratorVisitor.visit(Node.GetProperty n), code was added to check if the
varInfoNames Set contains the variable name used in the getProperty. If this
variable name is not found, a JasperException is thrown. However, what I
believe is missing is a check of the parent hierarchy to see if it was declared
at a higher level. In the case I have an issue with, the jsp:getProperty does
not have any varInfoNames declarations, but the parent (which is a customTag)
does contain the proper declarations. The proper declaration would have been
found if the check had traversed to the parent.

-- 
Configure bugmail: https://issues.apache.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tomcat.apache.org
For additional commands, e-mail: dev-help@tomcat.apache.org


Mime
View raw message