I'm using 3.4 snapshot..

Committed fix to 4.0 trunk at revision 40778 and to 3.3 EE maintenance branch at revision 40779. Added a utility function to parse time zone patterns when rendering the component.

The client-side calendar widget has a very limited support for time zones and no controls to specify time zones. Also, it doesn't support all the formats supported in Java. So, the time zone patterns (Z, z, and zzzz) are now parsed when rendering the component and passed to the client as literal text. These are parsed according to the locale and timeZone specified in the component.

IMPORTANT NOTE: using time zones in patterns only makes sense if the pattern includes the time as well. It won't be interpreted correctly by the client-side calendar widget if time is not included in the pattern string. So, the pattern in this JIRA description won't work anyway, since it doesn't make sense to display a time zone if time is not displayed as well. To test this, the pattern has to include, at least, the hour, like "d MMM yyyy h z", for example.

Confirmed fixed Icefaces 4 trunk and Icefaces ee-3.3.0 maintenance branch r40796. All browsers. The "d MMM yyyy h z" pattern has been added to the dateTimeEntry Attribute test applications.