Actions
Bug #3464
closed
Incorrect results for saxon:timestamp() under JDK 8
Start date:
2017-10-02
Due date:
% Done:
100%
Estimated time:
Legacy ID:
Applies to branch:
9.8
Fix Committed on Branch:
9.8, trunk
Fixed in Maintenance Release:
Platforms:
Description
Under JDK 8, the extension function saxon:timestamp() is implemented by calling java.time.Instant. On this path, the timezone calculation is incorrect. Saxon takes the GMT date/time and then labels it with the local timezone (the implicit timezone from the dynamic context) without actually adjusting the value to be in that timezone.
Updated by Michael Kay about 7 years ago
- Status changed from New to Resolved
- Applies to branch 9.8 added
- Fix Committed on Branch 9.8, trunk added
Fix committed on the 9.8 and development branches.
Updated by O'Neil Delpratt about 7 years ago
- Status changed from Resolved to Closed
- % Done changed from 0 to 100
- Fixed in Maintenance Release 9.8.0.5 added
Bug fix applied in the Saxon 9.8.0.5 maintenance release.
Please register to edit this issue
Actions
.