Wicket's form handling with let the textfields write their values to
their models first. FormComponentPanel#updateModel() is called after that.
Sven
On 03/05/2013 04:12 PM, pureza wrote:
Just let the textFields work on their models as usual.
I can't do that, because if I set the Address to null the textfields will
try to update fields of a null object.
--
View this message in context:
http://apache-wicket.1842946.n4.nabble.com/Persisting-optional-fields-null-vs-empty-object-tp4656979p4656995.html
Sent from the Users forum mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org