Hi, Sounds like that could be it -seeing as it affects all instances. Not to sound too stupid, but i take it that this can be addressed by applying a timezone object to the inputDate through the use of the convertDateTime tag?
Regards, Andrew ----- Original Message ---- From: Simon Lessard <[EMAIL PROTECTED]> To: MyFaces Discussion <[email protected]> Sent: Sunday, 16 September, 2007 4:36:45 PM Subject: Re: tr:inputDate My hunch would be the timezone setting. I don't have access to SVN and source right now to check, but if the TimeZone use the 3-char format (i.e. EST or PST), then daylight saving is ignored (and we're currently under daylight saving), resulting in hour hour lost. Since we set the date using midnight (0:00:00,000), losing 1 hours means going back one day. I plan to check out on that while fixing the first day of week issue to see if there's a way to prevent such issues. Regards, ~ Simon On 9/16/07, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote: It also happens with the live demos, which is weird... ----- Original Message ---- From: Leonardo Uribe < [EMAIL PROTECTED]> To: MyFaces Discussion <[email protected]> Sent: Sunday, 16 September, 2007 12:00:19 AM Subject: Re: tr:inputDate and also if i click the first available date (in this case 16/09/2007), it populates the field with 15/09/2007. I remember this issue. Are you using java.sql.Date as the type for the property in the bean? I just changed it for java.util.Date and all works well for me. Regards Leonardo Uribe
