Its been a over a year since patches have been submitted and this feature is still not correct e.g. http://jira.codehaus.org/browse/DISPL-304
The tutorial is incorrect in that ParamEncoder does not have an "encode" method. http://displaytag.sourceforge.net/11/tut_externalSortAndPage.html However, in light of these bugs/typos, I think the major problem is that the current implementation wants the back end to depend on display tag. Why should the back end need to depend on ParamEncoder or displaytag constants? Or even the "ID" attribute of the table on the jsp page. Doesn't this seem backwards? Instead, why not tell display tag the name of the "getter" on the backend. e.g. currentPageKey="pageNumber" and use that to decorate the links. Otherwise you are requiring servlets/actions etc to jump through hoops for display tag. They should not even be aware that displaytag was used on the front-end. thoughts? flames? Matt ------------------------------------------------------- This SF.Net email is sponsored by xPML, a groundbreaking scripting language that extends applications into web and mobile media. Attend the live webcast and join the prime developer group breaking into this new coding territory! http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642 _______________________________________________ displaytag-devel mailing list displaytag-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/displaytag-devel
