One style of Wicket development is to use a single page for the entire application, switching components within the page. If you did that, your "pages" could be large components chosen by the single master page. You could keep these "page" components in application or session storage to be re-used.
-----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of [EMAIL PROTECTED] Sent: Friday, November 03, 2006 1:31 AM To: [email protected] Subject: [Wicket-user] Strategy to avoid new instances of pages and panels Hi all! I am looking for a pattern, strategy or code example how to avoid creation of new page Instances when a user reloads a page. Can someone give my a hint how to achieve following behaviour: - "static" pages which have only a single instance during whole application lifecycle ? - some kind of page and/or factory or proxy to reuse instances? Any best practice or some examples would be nice. Thank you very much, Maciej Bednarz ------------------------------------------------------------------------ - Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642 _______________________________________________ Wicket-user mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/wicket-user ------------------------------------------------------------------------- Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642 _______________________________________________ Wicket-user mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/wicket-user
