[
https://issues.apache.org/jira/browse/SLING-7590?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16441462#comment-16441462
]
Jason E Bailey commented on SLING-7590:
---------------------------------------
[[email protected]] It only works in two out of three places if you
specifically use the ISO 8601 format. There is currently a pull request to fix
it for the ECMA format that the content parser uses.
[https://github.com/apache/sling-org-apache-sling-jcr-contentparser/pull/1]
which started this review.
Another option would be that instead of raising the JRE to 8 we could default
outputs and inputs to the ISO8601 standard.
> Content Loaders not respecting time zone for Dates
> --------------------------------------------------
>
> Key: SLING-7590
> URL: https://issues.apache.org/jira/browse/SLING-7590
> Project: Sling
> Issue Type: Improvement
> Reporter: Jason E Bailey
> Priority: Major
>
> When importing content, the JCR supports the setting of the time zone for a
> jcr Date. However we currently have several processes that fail to set the
> time zone correctly.
> org.apache.sling.jcr.contentparser.impl.ParserHelper
> org.apache.sling.jcr.contentloader.internal.DefaultContentCreator
> org.apache.sling.servlets.post.impl.helper.DateParser
> Take a String based time representation that includes a time offset and
> convert it to Date that looses that information, before conversion to a
> Calendar object.
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
