The following comment has been added to this issue:
Author: Mike Robinson
Created: Sun, 21 Nov 2004 8:13 PM
Body:
Is this patch to be applied to the RC2 code base?
---------------------------------------------------------------------
View this comment:
http://jira.codehaus.org/browse/DISPL-125?page=comments#action_27006
---------------------------------------------------------------------
View the issue:
http://jira.codehaus.org/browse/DISPL-125
Here is an overview of the issue:
---------------------------------------------------------------------
Key: DISPL-125
Summary: Preserve The Current Page And Sort Across Sessions (patch included)
Type: New Feature
Status: Unassigned
Priority: Minor
Original Estimate: Unknown
Time Spent: Unknown
Remaining: Unknown
Project: DisplayTag
Components:
Paging/Sorting
Versions:
1.0 RC2
Assignee:
Reporter: fabrizio giustina
Created: Fri, 19 Nov 2004 4:43 PM
Updated: Sun, 21 Nov 2004 8:13 PM
Description:
====
imported from sf tracker
id 980723
submitted by David E - halcy
http://sourceforge.net/support/tracker.php?aid=980723
====
Here is another enhancement for the project. It adds
the attribute
"preserveSortAndPage" to the table tag in both EL and
standard versions.
The idea is that (at least from usage on our own site)
someone can sort a
large list and get it exactly as they like it, then perhaps
navigate away to
something else, and would like to when they return see
it the same way they
left it (potentially, the data could change). However
navigating back to it
they likely wouldnt have the request parameters needed
to sort it as it was,
so when the preserveSortAndPage attribute is set to
true, the current
sort/page/sort order (and potentially previous sort/sort
order) are all
saved into session attributes named the same as they
would as request
parameters.
When the tag is executed and the preserveSortAndPage
attribute is set to
true it will first check the request parameters for the
necessary
information, and if it returns null from there it will
fallback to session,
then eventually to defaults.
There is an inherent limitation to this, if someone had a
list somewhere
else on the site and it was using the same name
variables for its list, and
it also had the preserveSortAndPage attribute set the
variables could clash,
thats a limitation of the parameter encoder. I thought
about tweaking the
parameter encoder to also encode perhaps the current
request.uri which would
be unique to that list because it would be on a different
page from another
list, however we use struts and when I watched that
value with the debugger
it was just pointing to my base tiles layout.. (which was
surprising to
me).. so that wouldnt uniquely define the list either. So
my conclusion is
it should be a documented limitation for people that
want to use this
feature, they need to name their lists differently if they
are going to use
them across the site.
---------------------------------------------------------------------
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
-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://productguide.itmanagersjournal.com/
_______________________________________________
displaytag-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/displaytag-devel
