I had the same problem. I solved this by providing a custom RequestHelper, say MyRequestHelper, which extends DefaultRequestHelper and overrides method getParameterMap() to simply return an empty map. Together with a corresponding MyRequestHelperFactory class and the line factory.requestHelper=MyRequestHelperFactory in displaytag.properties, only displaytag specific parameters will be included in urls constructed by the tag.
----- Original Message ----- From: <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Saturday, October 02, 2004 5:39 PM Subject: [displaytag-devel] [jira] Created: (DISPL-35) Enable / disable param forwarding > Message: > > A new issue has been created in JIRA. > > --------------------------------------------------------------------- > View the issue: > http://jira.codehaus.org/browse/DISPL-35 > > Here is an overview of the issue: > --------------------------------------------------------------------- > Key: DISPL-35 > Summary: Enable / disable param forwarding > Type: Improvement > > Status: Unassigned > Priority: Major > > Original Estimate: Unknown > Time Spent: Unknown > Remaining: Unknown > > Project: DisplayTag > Components: > Tag Library > Fix Fors: > 1.0 RC2 > Versions: > 1.0 RC1 > > Assignee: > Reporter: fabrizio giustina > > Created: Sat, 2 Oct 2004 11:38 AM > Updated: Sat, 2 Oct 2004 11:38 AM > > Description: > ==== > imported from sf tracker > id 984884 > submitted by James Chamberlain - james12670 > http://sourceforge.net/support/tracker.php?aid=984884 > ==== > > I am using displaytag in a portal environment (WebLogic, Pluto, > and eXo) and the forwarding of all current params has been a real > problem for me. I am using post in my forms, but I still experience > the problem. > > I patched displaytag so that in the TableTag.class in the initHref > method it only forwards params that are internal to displaytag > (this way the sorting and paging functionality can continue to > work). I did this by matching the params to the ones in the > TableTagParameters.class using reflection. It would be easy to > make this enabled or disabled via the properties file. > > I would really like to see this functionality included in displaytag. I > use displaytag in many portlet applications and this is essential for > it to work for me. Others have run into this same issue and have > had to come up with work-arounds. I struggle to find a senario > where I would want it to forward all current params (If I need to > forward one I just append it to the requestURI). > > What are thoughts on this from displaytag developers and other > users? Is this something that others are looking for? > > Regards, > > > --------------------------------------------------------------------- > JIRA INFORMATION: > This message is automatically generated by JIRA. > > If you think it was sent incorrectly contact one of the administrators: > http://jira.codehaus.org/secure/Administrators.jspa > > If you want more information on JIRA, or have a bug to report see: > http://www.atlassian.com/software/jira > > > > ------------------------------------------------------- > This SF.net email is sponsored by: IT Product Guide on ITManagersJournal > Use IT products in your business? Tell us what you think of them. Give us > Your Opinions, Get Free ThinkGeek Gift Certificates! Click to find out more > http://productguide.itmanagersjournal.com/guidepromo.tmpl > _______________________________________________ > displaytag-devel mailing list > [EMAIL PROTECTED] > https://lists.sourceforge.net/lists/listinfo/displaytag-devel > > ------------------------------------------------------- This SF.net email is sponsored by: IT Product Guide on ITManagersJournal Use IT products in your business? Tell us what you think of them. Give us Your Opinions, Get Free ThinkGeek Gift Certificates! Click to find out more http://productguide.itmanagersjournal.com/guidepromo.tmpl _______________________________________________ displaytag-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/displaytag-devel
