What Marico says below seems to be true. I've gotten this far and it's a dead end. Does 2.2 have a way around this? If not, is there any planed improvement in this model?
Maybe the new lenient="false" tag will solve my immediate problem but I don't think a framework should change the users input so fundamentally without offering the developers a hook to alter that behavior. A reasonable for this purpose hook wouldn't involve recompiling the JAR files. Perhaps this would all be OK if I could put in a fd:conversion tag at the widget level? Yours, Ed Elhauge * Merico Raffaele <[email protected]> wrote on [2009-02-05 02:26]: > Hi Ed > > > > As I guess ... > > > > Since the value container of a date field/widget is a java.util.Date object > it not possible (or I do not know how to) to set the wrong entered date by > the user and re-display it. > > > > To avoid that the bad entered and converted date value will be re-entered by > the user you could probably use a regular expression provided as follows: > > > > <fd:validation> > > <fd:javascript> > > return checkFormInputDate(widget, "\.(19|20)[0-9]{2}$"); > > </fd:javascript> > > </fd:validation> -- Edward Elhauge <[email protected]> "The right dose differentiates a poison and a remedy." -- Paracelsus (1493 - 1541) --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
