[
https://issues.apache.org/jira/browse/SLING-4258?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14278766#comment-14278766
]
ASF GitHub Bot commented on SLING-4258:
---------------------------------------
GitHub user santiagozky opened a pull request:
https://github.com/apache/sling/pull/54
Sling 4258
SLING-4258
-fix how the json servlet delivers dates with timezones.
-add test cases for some dates with different timezones
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/santiagozky/sling SLING-4258
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/sling/pull/54.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #54
----
commit 4074dfbd488516be730e5db007d18726bceb961c
Author: santiago garcia pimentel <[email protected]>
Date: 2015-01-15T15:00:41Z
fix json representation of timezones
commit 79635f2771577cdb234c7fa3c245c10a8d498a86
Author: santiago garcia pimentel <[email protected]>
Date: 2015-01-15T15:03:19Z
Merge branch 'trunk' into SLING-4258
----
> Please document better how dates are handled by the Post servlet
> ----------------------------------------------------------------
>
> Key: SLING-4258
> URL: https://issues.apache.org/jira/browse/SLING-4258
> Project: Sling
> Issue Type: Improvement
> Components: Documentation
> Reporter: santiago garcía pimentel
>
> Im currently doing some things with dates in Sling that involve timezones and
> I find that the documentation regarding it is not particularly clear.
> according to
> https://sling.apache.org/documentation/bundles/manipulating-content-the-slingpostservlet-servlets-post.html#date-properties
> several formats are defined.
> I found that the only format that saves a provided timezone is the ISO8601
> format, rest of them relies in a Date object, which does not have timezones.
> Could this be clearly stated?
> Also, the ISO8601 parser is problematic. It relies on the Jackrabbit parser
> which uses format "±YYYY-MM-DDThh:mm:ss.SSSTZD", but according to
> http://www.w3.org/TR/NOTE-datetime the ISO format does not have milliseconds
> on it ("SSS"). So it is very hard to find a way to keep the timezone
> information (I had to dig through the code to figure it out)
> Could we please replace ISO8601 with the actual format
> "±YYYY-MM-DDThh:mm:ss.SSSTZD" so it is clearer?
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
