[
https://issues.apache.org/jira/browse/TRINIDAD-61?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12551944
]
Yee-Wah Lee commented on TRINIDAD-61:
-------------------------------------
Sorry, my patch didn't include code to set the Application timezone (from the
config file) onto the date parser. This would be an issue if the server JDK and
the Application timezone were different.
> tr:validateDateTimeRange validation fails on last day of valid range
> --------------------------------------------------------------------
>
> Key: TRINIDAD-61
> URL: https://issues.apache.org/jira/browse/TRINIDAD-61
> Project: MyFaces Trinidad
> Issue Type: Bug
> Components: Components
> Reporter: Thorsten Guenther
> Assignee: Matthias Weßendorf
> Fix For: 1.0.5-core, 1.2.5-core
>
> Attachments: screenshot-1.jpg, trin11_61.diff, trin12_61.diff
>
>
> When used without an given converter (tr:convertDateTime), a
> tr:validateDateTimeRange's javaScript-validation fails (when used with
> facelets? not tested.) if the last day of the valid date-range was choosen in
> the tr:inputDate. (see screenshot). Debugging the javaScript shows that the
> select date was converted into for example "20.09.2007 01:00:00" (depending
> on timeZone) and is checked against "20.09.2007 00:00:00". So the choosen
> date is bigger then the max date and the validation fails.
> Using a ValueBinding and setting the maxdate to "20.09.2007 23:59:59" does
> not solve the problem since the time component seems to be cut of from
> maxDate for javaScript validation.
> A <tr:convertDateTime pattern="dd.MM.yyyy"/> is a workaround.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
