Well, Wicket has a Session Object. You can create your own subclass and store stuff in there (WebApplication.newSession(...). If you want to share state between pages, it's a natural place to put the state. One question you can ask yourself is: how many instances of that panel would I have? If the answer is: "one per user", the state of the panel is session state. So you have multiple copies of the panel, but they all store their state into the session.
Thomas On Mon, Feb 2, 2009 at 11:22 AM, Newgro <per.new...@gmx.ch> wrote: > > Hi Thomas, > > can you please explain this a bit. What do you mean by "session state". How > can i use session state in my context? > > Cheers > Per > -- > View this message in context: > http://www.nabble.com/What-are-the-consequences-on-sharing-panels-between-pages--tp21772949p21787239.html > Sent from the Wicket - User mailing list archive at Nabble.com. > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org > For additional commands, e-mail: users-h...@wicket.apache.org > > -- Thomas Mäder www.devotek-it.ch
