Details
-
Type:
Bug
-
Status: Closed
-
Priority:
Minor
-
Resolution: Fixed
-
Affects Version/s: 1.6.1
-
Component/s: ICE-Components
-
Labels:None
-
Environment:All
-
Affects:Sample App./Tutorial
Description
I noticed that the selectInputDate's inputText and the popup calendar used different timezones. This was because the SimpleDateFormat used for the inputText, and the Calendar used for the calendar had different rules for their default timezone. This led me to realise that we didn't have a mechanism for specifying a timezone that both could adhere to.
Also, it appeared that the Converter wasn't being consistently employed, since some logic was dependent on the popupDateFormat, and some used the Converter.
So, the decision was made to route everything through the javax.faces.convert.DateTimeConverter, which could specify both the timezone and the pattern for the inputText representation of the Date. The popupDateFormat attribute is no longer necessary, but for backwards compatiblity, if specified, it will override the DateTimeConverter's pattern.
Also, it appeared that the Converter wasn't being consistently employed, since some logic was dependent on the popupDateFormat, and some used the Converter.
So, the decision was made to route everything through the javax.faces.convert.DateTimeConverter, which could specify both the timezone and the pattern for the inputText representation of the Date. The popupDateFormat attribute is no longer necessary, but for backwards compatiblity, if specified, it will override the DateTimeConverter's pattern.
Activity
- All
- Comments
- History
- Activity
- Remote Attachments
- Subversion