Shapefile timezone parameter corrupted on catalog save
------------------------------------------------------
Key: GEOS-4801
URL: https://jira.codehaus.org/browse/GEOS-4801
Project: GeoServer
Issue Type: Bug
Components: Configuration
Affects Versions: 2.1.2
Reporter: Ian Schneider
Assignee: Ian Schneider
Fix For: 2.1.3
To duplicate, add a shapefile datastore and look at catalog datastore.xml. This will contain something like:
<entry key="timezone">sun.util.calendar.ZoneInfo[id="America/New_York",offset=-18000000,dstSavings=3600000,useDaylight=true,transitions=235,lastRule=java.util.SimpleTimeZone[id=America/New_York,offset=-18000000,dstSavings=3600000,useDaylight=true,startYear=0,startMode=3,startMonth=2,startDay=8,startDayOfWeek=1,startTime=7200000,startTimeMode=0,endMode=3,endMonth=10,endDay=1,endDayOfWeek=1,endTime=7200000,endTimeMode=0]]</entry>
To make matters more confusing to the novice observer, the serialization is done by a geotools Converter and on deserialization, the lovely TimeZone.getTimeZone(String) contained in ShapefileDataStoreFactory.DBFTIMEZONE, silently fails and returns the GMT time zone.
See: GEOT-3913
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira