Sorry, I am still a bit unclear: 1.say I go to an app at localhost/MyApp/app 2.App's home page is HomePage.class; its' constructor executes 3.I do browser reload, HomePage's contructor is executed again (so I'm getting a new object and not one costructed in #2)
How can I get Wicket to reuse object from #2 in step 3? thanks -nikita Johan Compagner wrote: > > pages are stored in the session (if they are statefull, that means they > have > callbacks) > > A stateless page could maybe been seen as a request scope object. > > there is no such thing as a combination of those 2. > > johan > > > > On 10/3/07, dukehoops <[EMAIL PROTECTED]> wrote: >> >> >> Hi, >> >> I'm evaluating Wicket as a potential replacement for JSF and have a >> question >> (tried searching, read wiki): >> >> What is the lifespan of a WebPage / Panel subclass instance? In JSF, >> page-backing beans can be request/session/app scoped. I read that Wicket >> is >> an "unmanaged" framework. Does that mean the objects are request-scoped? >> >> If so, how how does one implement a session-persistent header (as Panel) >> + >> request-scoped body scenario? >> >> If this is documented in reference, please kindly point me to the >> specific >> section - I could not find anything relevant.... >> >> thanks >> -nikita >> -- >> View this message in context: >> http://www.nabble.com/webpage-instance-scope--tf4564224.html#a13027317 >> Sent from the Wicket - User mailing list archive at Nabble.com. >> >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: [EMAIL PROTECTED] >> For additional commands, e-mail: [EMAIL PROTECTED] >> >> > > -- View this message in context: http://www.nabble.com/webpage-instance-scope--tf4564224.html#a13029062 Sent from the Wicket - User mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
