Larry Isaacs wrote:
When applying Gareth Morgan's bug fix for JspRuntimeLibrary in the Tomcat MAIN
branch, a difference between the tomcat_32 and MAIN versions revealed that
Tomcat 3.2 still has the bug discovered by Glenn Nielsen. This is where:
jsp:setProperty name="bean"
I would argue that in such a case, the developer should not
use an "indexed" property, but rather a simple property that
takes a String array as argument.
(i.e. the only difference with an "indexed property" is that
the index setter method would not be defined).
I had not noticed the
Larry Isaacs wrote:
...
I'll try to commit a patch that fixes just the following:
1) Fix value="" without allowing param="..." to set.
2) For a String array property, make "?prop=prop=text" set the
property for property="*". Currently property="*" handling
assumes only simple
When applying Gareth Morgan's bug fix for JspRuntimeLibrary in the Tomcat MAIN
branch, a difference between the tomcat_32 and MAIN versions revealed that
Tomcat 3.2 still has the bug discovered by Glenn Nielsen. This is where:
jsp:setProperty name="bean" property="prop" value=""/
Larry Isaacs wrote:
I'm +1 on fixing the jsp:setProperty name="bean" property="prop" value=""/
bug in Tomcat 3.2.
+1
If the desired behavior for indexed properties can be
determined, I can try to fix that too.
Sent email to Eduardo to try to get a clarification.
-- Pierre
Larry Isaacs wrote:
When applying Gareth Morgan's bug fix for JspRuntimeLibrary in the Tomcat MAIN
branch, a difference between the tomcat_32 and MAIN versions revealed that
Tomcat 3.2 still has the bug discovered by Glenn Nielsen. This is where:
jsp:setProperty name="bean"
