[
https://issues.apache.org/jira/browse/SLING-7844?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16588863#comment-16588863
]
Jason E Bailey commented on SLING-7844:
---------------------------------------
Having spent years on the receiving side of these minor changes that breaks
everything under the sun. I appreciate that thought. And yes, someone somewhere
wrote a custom piece of code to parse that specific format to do something very
specific and highly important. However on the other side of that, anyone coming
to Sling or writing something new to access that legacy date string will have
to write something custom, or in the case of a browser rely on the default
failover handling once it fails to parse as an ISO8601.
I'm not against the changing of the default value, I just don't agree. If my
disagreement prevents a change going in that others want, I'll change it to a
frown.
> Format change in JSON date format due to SLING-7670
> ---------------------------------------------------
>
> Key: SLING-7844
> URL: https://issues.apache.org/jira/browse/SLING-7844
> Project: Sling
> Issue Type: Bug
> Components: Servlets
> Affects Versions: Servlets Get 2.1.32
> Reporter: Carsten Ziegeler
> Assignee: Robert Munteanu
> Priority: Major
> Fix For: Servlets Get 2.1.34
>
>
> SLING-7670 changes the default rendering of a date in JSON by default which
> is an incompatible change and potentially breaks clients.
> The default of the servlet should generate the old format, the new format
> must require a config change.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
