A minor point, as far as I know there is no difference between bookmarkable pages and regular pages. To be a bookmarkable page a page has to either provide an empty constructor or a constructor that takes page params, but that's it, and that is only so that it can be instantiated through the pagefactory.
-Igor > -----Original Message----- > From: [EMAIL PROTECTED] [mailto:wicket-develop- > [EMAIL PROTECTED] On Behalf Of Michael Jouravlev > Sent: Thursday, September 08, 2005 9:13 AM > To: [email protected] > Subject: Re: [wicket-Develop] Reusing pages and models > > On 9/8/05, Johan Compagner <[EMAIL PROTECTED]> wrote: > > I still think that you just don't generate a bookmarkable link > > But a PageLink to you signin page. And that link you place on the other > > pages you are displaying > > And in that pageLink you can do anything at the moment a getPage() is > > asked for. (like reset) > > I guess you are right, I have to change my mindset from URLs to > objects. So, can I create a PageLink to a concrete instance of > bookmarkable page? If yes, then all I need to change in framework > boils down to the home page. > > > with homepage you are right. I think we can maybe pool that one somehow. > > so if you access / then a homepage is created if not present > > if a homepage instance is there it is reused. > > You are right, I created all this code only because SignIn example > contains only bookmarkable pages. If you handle the home page, then my > changes will not be needed. > > > I don't like changing the way bookmarkable pages work.. Those are just > > entry points inside a application. > > Internally you should use use PageLinks to pages you want to keep state > > with. > > Ok, I will try that. > > On 9/8/05, Igor Vaynberg <[EMAIL PROTECTED]> wrote: > > Im confused. Are we talking about making the page a singleton bounded by > > session or application? If we are talking about making it bounded by > > application, I don't like it as it makes it too easy to share state > between > > users when unintended. If we are talking about bounding it by session > isn't > > it easy to serialize a page into a session variable and then just use it > as > > a response page in a Link ? > > I want to bind it to session. To reuse page as response I need to find > it somehow, do I? Seems that Johan already gave me a pointer how to do > that. > > Ok guys, sorry for disturbance ;-) > > Still, I think that home page is needed to be handled somehow, so that > I would be able to have only one instance of it or one instance of > page where it redirects to, like SignIn. > > Michael. > > > ------------------------------------------------------- > SF.Net email is Sponsored by the Better Software Conference & EXPO > September 19-22, 2005 * San Francisco, CA * Development Lifecycle > Practices > Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA > Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf > _______________________________________________ > Wicket-develop mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/wicket-develop > ------------------------------------------------------- SF.Net email is Sponsored by the Better Software Conference & EXPO September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf _______________________________________________ Wicket-develop mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/wicket-develop
