On Tue, Jul 7, 2009 at 7:13 AM, Stephan Windmüller<stephan.windmuel...@cs.tu-dortmund.de> wrote: > Hello!
Hi! > There is a page in my current project for which I want to pass an object > between the requests and maintain it's state, but it should not be > displayed. Also I do not want to store the data in the session, so > putting it in a hidden field seems the best option. What about cookies? They are accessed in Tapestry through the Cookies service. > Unfortunately I am unable to find a standard way for tapestry which > generates the streamed data needed by ValueEncoder. I'm not following you here. ValueEncoder does not need streamed data. It just does mapping between object and a string representation of it and vice-versa. This mapping is implemented by you. If the given object has a primary key field, it's the easiest solution. > The wiki tells about DataSqueezer[0] but that seems quite outdated. This is part of Tapestry 4, not 5. > The persistence guide[1] > mentions a "client strategy" which allows "an extra hidden field in each > form" but I do not know how to force hidden fields instead of URL encoding. AFAIK, it's impossible to do what you want this way. How would you pass parameters from one page to another without using the session, cookies, form submission or information in the URL? -- Thiago --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org For additional commands, e-mail: users-h...@tapestry.apache.org
