Justin Deoliveira ha scritto:
>> Is there any reason why you forced GMT timezone for
>> dates? I think 2007-07-04+02:00 or simply 2007-07-04
>> would be both more correct.
> I don't think this is something that is done explicitly... i think its
> just the behaviour of the encoder.
Hmm.... something is happening here, just don't know where...
Tried out with the stripped jaxme converter:
Date d = new Date();
Calendar c = Calendar.getInstance();
c.setTime(d);
c.set(Calendar.HOUR, 0);
c.set(Calendar.MINUTE, 0);
c.set(Calendar.SECOND, 0);
c.set(Calendar.MILLISECOND, 0);
System.out.println(converter.printDateTime(c));
System.out.println(converter.printDate(c));
The output is:
2007-07-20T00:00:00+02:00
2007-07-20+02:00
As you can see the timezone has been preserved... maybe it's
jaxb that's behaving differently, or something in the
chain between the db and the xml that's doing fun things...
We'll have to check.
Cheers
Andrea
-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2005.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
Geotools-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/geotools-devel
