conversation scope in wicket is simply passing this data from page to
page. eg setresponsepage(new step2page(data));
-igor
On Fri, May 22, 2009 at 5:53 PM, janneru wrote:
> i wouldn't be happy to put such data into the session where it will lie
> around all the time; it doesnt belong to the user
i wouldn't be happy to put such data into the session where it will lie
around all the time; it doesnt belong to the user but to a usecase which
consists of just some pages; a perfect application for conversation scope;
when you use wicket with seam, seam can handle these conversation scopes for
yo
I would suggest that this would be the "wicket way" as well. This
sounds like the data is session scoped - it belongs to the user. It
doesn't really "belong" to a page. Just OO.
--
Jeremy Thomerson
http://www.wickettraining.com
On Fri, May 22, 2009 at 7:40 AM, Lorenzo Bolzani wrote:
> Yes,
2009/5/22 Dipu :
> can't you store the List in the session when you move to other page's
> and get it from session when you get back.
>
Yes, I can, but it doesn't look very "wicket style", so I suspect I'm
missing something about Wicket (PageMaps, RequestTarget, ecc.) and
that there is a very clea
can't you store the List in the session when you move to other page's
and get it from session when you get back.
-dipu
On Fri, May 22, 2009 at 12:46 PM, Lorenzo Bolzani wrote:
> Hi, I'm trying to keep a page state between requests.
>
> I know this should be a very simple thing, but it's puzzling
Hi, I'm trying to keep a page state between requests.
I know this should be a very simple thing, but it's puzzling me.
I have a field, a List, in my page where some data from the user is
accumulated. This data is generated from a "monitoring" system.
The user starts the monitoring and the events
