I'm not sure exactly what you're asking. Is it one of the following? - I have two apps in two JVMs - how do I transfer state from one app to the second when clicking a link from one to the other? - I have two apps in two JVMs - how do I expire state in the first when moving to the second?
-- Jeremy Thomerson http://www.wickettraining.com On Mon, Mar 2, 2009 at 7:26 AM, subbu_tce <subramanian.mur...@gmail.com>wrote: > > Hi, > > I have two wicket applications running in two different JVMs. > > If clicking on a link in the first wicket application that runs in the > first > JVM, is redirected to the second wicket application that runs in second > JVM, > What support does Wicket provide to manage the page map in the session for > the first wicket application other than manually invalidating the objects > in > the session when redirected to the second wicket application? > > Moreover, I understand the state of all wicket components are maintained in > the session. But does wicket provide any programmatic extension points to > have the partially/fully managed on the client side? > > And also please help me point to good materials/articles on session > management and custom session management in wicket. > > Thanks, > Subbu. > -- > View this message in context: > http://www.nabble.com/Wicket---Session-Management-tp22288083p22288083.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 > >
