I found the usage of the name attribute a bit confusing in the latest EL version. I
understood that I needed to change all my JSPs to use the EL syntax ( ${results} ) --
but could not get it to work correctly.
I finally realized that my JSP container (Tomcat 5) was interpreting the EL before
passing it to the tag. Therefore, I needed to escape the $, like so \${results} (I
know that I can also use <%@ page isELIgnored="true"%> but then I can't use EL in my
other JSP code.
This is a big inconvenience since it seems that the EL version will always require the
${ syntax. Why not add it inside the TableTag code? Is there any reason to distinguish
between name="results" and name="\${results}"?
I got around it easily by subclassing org.displaytag.tags.el.TableTag like so:
package mypackage;
public class TableTag extends org.displaytag.tags.el.TableTag {
public void setName(String arg0) {
super.setName("${"+arg0+"}");
}
}
and changing the reference in the TLD.
Is there a chance that RC1 will implement it this way? It would minimize the number of
changes to exisiting JSPs.
Thanks. Great product! Kudos to Matt and Fabrizio.
-------------------------------------------------------
This SF.Net email is sponsored by: IBM Linux Tutorials
Free Linux tutorial presented by Daniel Robbins, President and CEO of
GenToo technologies. Learn everything from fundamentals to system
administration.http://ads.osdn.com/?ad_id70&alloc_id638&op=click
_______________________________________________
displaytag-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/displaytag-devel
