wicket's recommended way of interactining with form components is through the models. IModel interface is very flexible and you can easily create decorators for existing models that pre and post process data, as well as create your own implementations entirely. this is one of the central concepts of wicket and i can guarantee it is a good investment of your time to understand how it works if you want to use wicket.
-Igor
On 2/22/06, Frank Silbermann <[EMAIL PROTECTED]> wrote:
In most of the component examples we use a PropertyModel so the model is
automatically updated. I presume that with the DropDownList the model
would be set to the selected string.
What is the purpose of its "void updateModel()" method? Is this
something to override so that instead of setting the model object to the
selected string we can compute some other value (a value typically
computed _using_ on the selected string?
-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems? Stop! Download the new AJAX search engine that makes
searching your log files as easy as surfing the web. DOWNLOAD SPLUNK!
http://sel.as-us.falkag.net/sel?cmdlnk&kid3432&bid#0486&dat1642
_______________________________________________
Wicket-user mailing list
Wicket-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wicket-user
