Sorry the session won't work as you most likely would log in twice.
You can store global settings within your Application class but there might be better approaches too... I know for our product licensing I used the Application class so that it would update for all users across all sessions. ~ Thank you, Paul Bors -----Original Message----- From: Paul Bors [mailto:[email protected]] Sent: Wednesday, June 26, 2013 10:51 AM To: [email protected] Subject: RE: Inter-Page Communication in Wicket I would store such data in the user's session or persist it and read it from the other page. ~ Thank you, Paul Bors -----Original Message----- From: eugenebalt [mailto:[email protected]] Sent: Wednesday, June 26, 2013 10:48 AM To: [email protected] Subject: Inter-Page Communication in Wicket Is there a way in Wicket to maintain different open pages that may be open in different windows? For example, make updates from one page that affect components on a different page. (Note: we are using Wicket 1.4.7) Thanks -- View this message in context: http://apache-wicket.1842946.n4.nabble.com/Inter-Page-Communication-in-Wicke t-tp4659816.html Sent from the Users forum mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
