Eelco Hillenius wrote: > > When fixing issues 500[1] and 522[2] I found that the best way of > fixing this is to override getConvertedInput (which was declared as > final). For anyone using FormComponentPanel, please take note that if > you want this component to work properly with validators and form > validators you should override getConvertedInput rather then > updateModel. Please see the implementations of DateField and > DateTimeField and the updated JavaDoc of FormComponentPanel. >
I am making a ComboBox component that extends FormComponentPanel. I did as you said, and I override getConvertedInput(), but the body of the method scans a List to find a matching item. With only a few items, this isn't too bad, but I'm afraid of performance problems as the list size grows. Also, that method is already called twice and I am planning on writing a Validator for it, which will cause it to be called at least three times per update cycle. I was wondering if you could suggest a caching strategy for me to try? I can store the converedInput on the Component, but what about cleaning up that cached value? Will I need to worry about stale data being returned by getConvertedInput? or will the Component's normal lifecycle protect me from that? Thanks for any insight you can offer. Chuck -- View this message in context: http://www.nabble.com/Use-getConverterInput-rather-than-updateModel-in-FormComponentPanel-tf3873952.html#a11395618 Sent from the Wicket - User mailing list archive at Nabble.com. ------------------------------------------------------------------------- This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/ _______________________________________________ Wicket-user mailing list Wicket-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wicket-user
