[
https://issues.apache.org/jira/browse/DAFFODIL-1929?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Beckerle closed DAFFODIL-1929.
--------------------------------------
Resolution: Not A Problem
Turns out one can override calendarTimeZone="UTC" via calendarTimeZone="", and
that achieves the proper behavior.
This is functioning per the DFDL spec. Not a bug.
> Parse of date results in date+time-zone specifier - should be just date.
> ------------------------------------------------------------------------
>
> Key: DAFFODIL-1929
> URL: https://issues.apache.org/jira/browse/DAFFODIL-1929
> Project: Daffodil
> Issue Type: Bug
> Components: Back End
> Affects Versions: 2.1.0
> Reporter: Michael Beckerle
> Priority: Major
> Fix For: 2.2.0
>
>
> Parse of 9/26/2017 with pattern MM/d/yyyy results in 2017-09-26+00:00 which
> has timezone specifier on it.
> The timezone specifier is incorrect because the data does not say what the
> timezone is, nor is it otherwise specified, and it is unexpected in an
> xs:date.
> We should suppress a timezone specifier when timezone is unknown.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
