Hi Francesco, This isn't expected behaviour, it's spec'ed behaviour. This tag is special in my eyes because I think the spec is wrong and should change and this tag is representative of what it should be. The behaviour that Francesco is seeing is the same behaviour everyone is seeing and I'm sure everyone wastes a lot of time trying to find a bug in their own code when it turns out it's speced to be that way. Unless of course you live in the GMT zone, but the world does not revolve around that zone. ;)
I understand Brendan's concerns and they make sense for almost everything, but I think this is a special case. In any case, I'll change the name or add an attribute if that's what people would prefer. Quick vote? Travis On 11/1/05, Francesco Consumi <[EMAIL PROTECTED]> wrote: > Quoting Travis Reeder <[EMAIL PROTECTED]>: > > > I think the JSF spec silently altered the assumptions that most people > > have so this converter fixes that. This simply gives you the > > opportunity to choose which converter you'd like to use. > > > > I agree with you, are the JSF specs that alter the data. I don't > understand why servlet has to alter my dates. > > For example, I have a lot of pages linked to DB queries, with some > filter that the user can select, and I ask dates to user with > t:inputDate controls. For every post of page, the user obtains the > filtered data table and, at the top of page, the t:inputDate with > chosen dates. Using the webapp here (Florence, Italy), every time that > user submits page with filters, date shifts back one day. Following the > specs, does the user to reinsert at every post the right dates ? > I don't think this is the expected behaviour..... > > > -- > Francesco Consumi > Ufficio Sistemi informativi > Istituto degli Innocenti > Piazza SS.Annunziata, 12 > 50122 Firenze > consumi at istitutodeglinnocenti.it > Tel. +39 055 2037320 > ICQ# 12516133 > > >
