you pass an instance, then wicket uses that instance. The
2nd approach can for instance be used if you have state (i.e. a model or
something else) to pass to the new page, but not necessarily.
-
--
Regards,
Hans
http://cantaa.de
--
View this message in context:
http://apache-wicket.1
om: Paul Bors [mailto:p...@bors.ws]
> Sent: Monday, February 18, 2013 10:08 AM
> To: users@wicket.apache.org
> Subject: Re: Fundamental forms/models issue
>
> What are you really trying to accomplish here?
>
>
>
> I think you're on the right path only one thing I would mention,
Bors [mailto:p...@bors.ws]
Sent: Monday, February 18, 2013 10:08 AM
To: users@wicket.apache.org
Subject: Re: Fundamental forms/models issue
What are you really trying to accomplish here?
I think you're on the right path only one thing I would mention, the page
constructor is not called
rs.ws]
Sent: Monday, February 18, 2013 10:08 AM
To: users@wicket.apache.org
Subject: Re: Fundamental forms/models issue
What are you really trying to accomplish here?
I think you're on the right path only one thing I would mention, the page
constructor is not called only once per applic
What are you really trying to accomplish here?
I think you're on the right path only one thing I would mention, the page
constructor is not called only once per application life cycle. Same page
can be constructed multiple times if you have a link going to that page
and you calll setResponsePage
Since a Wicket WebPage has it's constructor invoked only one time in the
application lifecycle
Usually a new page instance is created each time you visit a bookmarkable url.
WebPages are never shared between clients.
Sven
On 02/18/2013 06:47 PM, Michael Chandler wrote:
Good morning/afterno
On Mon, 18 Feb 2013 17:47:16 +
Michael Chandler wrote:
> Good morning/afternoon everyone.
>
> I'm having a basic problem fully deciphering how to best manage my
> forms, specifically related to Models that are attached to forms.
> Since a Wicket WebPage has it's constructor invoked only one
Good morning/afternoon everyone.
I'm having a basic problem fully deciphering how to best manage my forms,
specifically related to Models that are attached to forms. Since a Wicket
WebPage has it's constructor invoked only one time in the application
lifecycle, I'm failing to fully understand
