[
https://issues.apache.org/jira/browse/DAFFODIL-2671?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17828051#comment-17828051
]
Steve Lawrence commented on DAFFODIL-2671:
------------------------------------------
Actually, DFDL allows minInclusive/maxExclusiv/etc to be define for calendar
types, so the invalidRestrictionPolicy does not come into play for this
particular bug. This bug is to just implement something that DFDL says we
should support. We might still need to come up with an answer for how to handle
DFDL-invalid restrictions where we don't support the "validate" policy, but
it's not needed for this bug.
> support minInclusive maxInclusive on date/time/dateTime
> -------------------------------------------------------
>
> Key: DAFFODIL-2671
> URL: https://issues.apache.org/jira/browse/DAFFODIL-2671
> Project: Daffodil
> Issue Type: New Feature
> Components: Back End
> Affects Versions: 3.2.1
> Reporter: Mike Beckerle
> Assignee: Mike Beckerle
> Priority: Minor
>
> I am trying to use this simple type:
> {code:java}
> <simpleType name="msDateTime">
> <restriction base="xs:dateTime">
> <maxInclusive value="2094-12-31T23:59:59"/>
> <minInclusive value="1995-01-01T00:00:00"/>
> </restriction>
> </simpleType>{code}
> I get this diagnostic message:
> {code:java}
> Schema Definition Error: Failed to parse (1995-01-01T00:00:00) to dateTime
> (uuuu-MM-dd'T'HH:mm:ss.SSSSSSxxx) due to Character array is missing "e"
> notation exponential mark. (after Unparseable date:
> "1995-01-01T00:00:00").{code}
> The other facets (minExclusive, maxExclusive), and the other calendar types
> (date, time) should also be tested.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
