Re: Passing Parameters to Bookmarkable Page

2007-09-25 Thread Eelco Hillenius
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.

Re: Passing Parameters to Bookmarkable Page

2007-09-20 Thread Flavius
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

Re: Passing Parameters to Bookmarkable Page

2007-09-20 Thread Evan Chooly
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

Re: Passing Parameters to Bookmarkable Page

2007-09-20 Thread Flavius
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.

Re: Passing Parameters to Bookmarkable Page

2007-09-19 Thread chickabee
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.