Details
Description
The timeZone attribute on the DateSpinner and TimeSpinner has no effect. The timeZone can be changed on the component with no change to the bound date object, which appears to always use the default server time zone.
The use of this attribute is also confusing as the component is used with the <f:convertDateTime/> tag, which has its own timeZone attribute:
<mobi:dateSpinner useNative="true" id="date"
value="#{dateBean.dateInput}"
timeZone="#{dateBean.timeZone}">
<f:convertDateTime type="date" pattern="yyyy-MM-dd" timeZone="#{dateBean.timeZone}"/>
</mobi:dateSpinner>
The use of this attribute is also confusing as the component is used with the <f:convertDateTime/> tag, which has its own timeZone attribute:
<mobi:dateSpinner useNative="true" id="date"
value="#{dateBean.dateInput}"
timeZone="#{dateBean.timeZone}">
<f:convertDateTime type="date" pattern="yyyy-MM-dd" timeZone="#{dateBean.timeZone}"/>
</mobi:dateSpinner>
Activity
- All
- Comments
- History
- Activity
- Remote Attachments
- Subversion
This component still has to be brought into core rendering strategy. All jira's for these components will be dealt with at that time.