Hi Michael,
Michael Chandler wrote
> To conclude, my issues stemmed from not properly linking from page to
> page. I did a lot of this:
>
> BookmarkablePageLink
> <String>
> ("link", MyClass.class);
>
> Instead of this:
>
> Link
> <String>
> ("link") {
> public void onClick() {
> setResponsePage(new MyClass());
> }
> }
>
> Oopsy!
Oopsy is not necessary :-) Depending on the Use Case, both ways are fully
okay.
If you pass MyClass.class then, as stated before, Wicket creates a fresh
page for you. If 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.1842946.n4.nabble.com/Fundamental-forms-models-issue-tp4656511p4656537.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]
