[TRINIDAD-1967] DateTimeRangeValidator gives false failure if server specifies timezone attribute or timezone specified in trinidad-config.xml

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 1.2.13-core
• Fix Version/s: 2.0.0-beta-1
• Component/s: Components
• Assignee: Unassigned
• Reporter: Yee-Wah Lee
• Created: 02/Dec/10 21:23
• Updated: 13/Jan/11 11:56
• Resolved: 04/Dec/10 01:05

Description

This is a regression caused by Trinidad-1920. In that fix, an ISO-Date format was used to create minISO/maxISO strings on the validator so the min/maxDate could be sent down without loss of information. However the DateFormat was not created with the timezone of the component converter, so it would send down strings that specified different values causing false validation.

1. Modify the following example in trinidad-demo/clientConvert.jspx and run it (this example uses Europe/Stockholm timezone, any TZ different from server JDK timezone will suffice).
<tr:inputText id="mdf5" value="#

{date.date2}

"
label="date converter and a validator that sets a maximum date of tonight">
<tr:convertDateTime type="both" timezone="Europe/Stockholm"/>
<tr:validateDateTimeRange maximum="#

{date.tonightNearMidnight}

"/>
</tr:inputText>

2. If you have a hint on the validator, it would display max with the timezone of the converter. For example, if server is PST, and I'm running on 2010-12-2, the maxDate created is 2010-12-2 11:59 pm PST which converts to 2010-12-3 8:59am (GMT+1). So the maximum I can enter on the client is 12/3/2010 8:59am.

3. In the input box, type in the max and Submit. Get an error about failing validation although it is within bounds.