> by the way this is a bit more dangerous now:
>
> protected void convertInput()
> {
> setConvertedInput(dateField.getConvertedInput());
> }
>
> this goes ok because we visit child post order. and because dateField is a
> child it works
> But getConvertedInput and convertInput() are called in different flows.
Yeah, I noticed that. I couldn't really think of a better solution
though. Either you tell users to override a method that can (will) be
called multiple times - getConvertedInput - and there isn't even a
guarantee when that is, or, like we do now, we tell users to override
a method that will only be called once and at a clear point in the
processing.
WDYT Johan?
Eelco
-------------------------------------------------------------------------
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
