[ https://jira.jboss.org/jira/browse/JBSEAM-3089?page=com.atlassian.jira.pl... ] Dan Allen commented on JBSEAM-3089: ----------------------------------- This is one of those features that would be so nice to have in Seam. Every time a developer has to add a time zone choice list to their app, they waste like an entire day researching time zones, trying to steal a list from the web, finding out that there isn't one, then stealing it from some forums somewhere. Granted, no list will please everyone. So here is my idea. We provide a flat file of timezones that map to offsets. We read that list from the classpath in a startup component (if configure in components.xml, say <international:time-zone-config/>). The developer can override that list with a file on their classpath or somewhere else. But the format would be the same. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://jira.jboss.org/jira/browse/JBSEAM-3089?page=com.atlassian.jira.pl... ] Dan Allen commented on JBSEAM-3089: ----------------------------------- Well, that function is really where the problem starts. It's the most unnormalized and ridiculously verbose list I have ever seen. I mean there are 24 possible time zones (in terms of hour offsets) yet that list has 550+ entries. The list should have less than 100 entries, and more like 50. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://jira.jboss.org/jira/browse/JBSEAM-3089?page=com.atlassian.jira.pl... ] Dan Allen commented on JBSEAM-3089: ----------------------------------- Peter Hilton contributed a time zone component which uses a simple but effective filter to get the list down to just country names. I implemented a TimeZone wrapper type that makes the TimeZone object easier to use from a display perspective. We are going to go with this solution for now. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://jira.jboss.org/jira/browse/JBSEAM-3089?page=com.atlassian.jira.pl... ] Dan Allen updated JBSEAM-3089: ------------------------------ Attachment: timezone-list.txt Just in case we think about providing our own list of time zone ids, I have attached a normalized list. This would need to be validated before making it part of Seam. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://jira.jboss.org/jira/browse/JBSEAM-3089?page=com.atlassian.jira.pl... ] Dan Allen resolved JBSEAM-3089. ------------------------------- Fix Version/s: 2.1.2.CR1 (was: The future) Resolution: Done Assignee: Dan Allen -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://jira.jboss.org/jira/browse/JBSEAM-3089?page=com.atlassian.jira.pl... ] Dan Allen resolved JBSEAM-3089. ------------------------------- Resolution: Done Oops! Corrected the package name. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira