I use that continuously. Not only in Wicket but with swing too. It's a kind
of hack but it does its job.
The economic way is to use a converter because in the future you may use the
converter with other model classes. In the other hand if you use the same
model with different technologies (Swing, wicket, reporting...) then you can
always bind a field to known data type.
I use this too when I need to combine two fields in one. If you have a
Person class and name and surname fields, you can add a getter method to
read name+surname and bind that in a read only field or a report.
Cheers.
--
Marc Nuri

Reply via email to