> If the page is bookmarked, I don't care about retaining the filter.
> I just want the id for the item they want to view. But if they
> clicked the link from the list page (that has a list based on the filter),
> then when they return to the list page (save, cancel), I want
> to pass the filter b
If the page is bookmarked, I don't care about retaining the filter.
I just want the id for the item they want to view. But if they
clicked the link from the list page (that has a list based on the filter),
then when they return to the list page (save, cancel), I want
to pass the filter back.
Th
Having the link be both bookmarkable and having that object in the URL
without persisting seems largely contradictory. Relying on having the
object in the session also reduces the effect of making it bookmarkable.
The only option I see for making it really bookmarkable (stateless) is
serializing t
If I pass the id, I have to persist the filter someplace, like
the session. I try to avoid putting things on the session
since it inhibits performance of session replication in a clustered
environment.
If I could get to the requestCycle when the link is clicked, it seems
like I could pass it al
Put the Filter ID in the map.
On 9/18/07, Flavius <[EMAIL PROTECTED]> wrote:
>
>
> I have two pages, a list page and a detail. The list page
> can take a filter parameter, or has a default one if one
> is not passed (making it bookmarkable). When the user
> clicks to go to the detail page, I wan
It seems like in:
parameters.put("filter", filter);
the filter object is the instance of com.foo.bar.Filter class, I guess if
you implement toString() correctly within this object that might help, also
instead of com.foo.bar.Filter object, try supplying a String as an
alternate,
Good luck.
