state from page
to page? Thanks for the help.
Tim
--
View this message in context:
http://www.nabble.com/Passing-LoadableDetachableModels-tp19068126p19068126.html
Sent from the Wicket - User mailing list archive at Nabble.com
--
View this message in context:
http://www.nabble.com/Passing-LoadableDetachableModels-tp19068126p19069915.html
Sent from the Wicket - User mailing list archive at Nabble.com.
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional
for the help.
Tim
--
View this message in context:
http://www.nabble.com/Passing-LoadableDetachableModels-tp19068126p19069915.html
Sent from the Wicket - User mailing list archive at Nabble.com.
-
To unsubscribe, e
the DetachableModel approach how do I persist the model's state from
page to page? Thanks for the help.
Tim
--
View this message in context:
http://www.nabble.com/Passing-LoadableDetachableModels-tp19068126p19069915.html
Sent from the Wicket - User mailing list archive at Nabble.com
On Wed, Aug 20, 2008 at 12:19 PM, Martijn Dashorst
[EMAIL PROTECTED] wrote:
Not quite true: first Wicket will attach the model, which will load
the data from the database. When the form input is valid, this data
will be propagated to the attached model. = the data will reflect the
input.
If
On Wed, Aug 20, 2008 at 6:27 PM, James Carman
[EMAIL PROTECTED] wrote:
If you don't commit the changes (and you wouldn't want to typically in
a wizard) to the object between pages, then the original data will
merely be loaded from the database and your previous edits will be
lost.
erhm...
On Wed, Aug 20, 2008 at 12:39 PM, Martijn Dashorst
[EMAIL PROTECTED] wrote:
On Wed, Aug 20, 2008 at 6:27 PM, James Carman
[EMAIL PROTECTED] wrote:
If you don't commit the changes (and you wouldn't want to typically in
a wizard) to the object between pages, then the original data will
merely
