DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT <http://issues.apache.org/bugzilla/show_bug.cgi?id=29881>. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE.
http://issues.apache.org/bugzilla/show_bug.cgi?id=29881 Problems using datatype type="date" variant="time" ------- Additional Comments From [EMAIL PROTECTED] 2004-07-03 17:09 ------- Colin, with some small changes to the FormattingDateConvertor class I think your issues would be solved. First, to avoid any confusion, I'd like to point out there's no time-variant of the date datatype. There's only one date datatype, corresponding to the java.util.Date class, which holds both date and time information. It is then by using the "formatting" convertor for dates that you can choose to only show/parse the date and/or time component. The variant (date, time, datetime) that you specify to the formatting convertor is just a hint as to retrieve a default formatting (for some locale). If you specify the pattern explicitely, then this doesn't influence the display/parse of the date anymore. However, the variant is still useful to show a more specific error message to the user, and to show the calendar popup only when it makes sense. So all that's needed is some small changes to FormattingDateConvertor: - in generateSaxFragment(), add a variant attribute - in convertFromString(), use a more specific i18n key (and add them to the resource bundles as well) Not a big change, but I don't have time for it right now. Patches welcome. PS: the attribute datatype="date" on the fd:convertor element has no meaning when used in the form definition.
