[jira] [Closed] (SLING-7346) Issues with custom fields in PostResponse as a result of fix for SLING-6681(Replace commons.json usage in org.apache.sling.servlets.post)

["Karl Pauls (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/SLING-7346?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Karl Pauls closed SLING-7346.
-----------------------------

> Issues with custom fields in PostResponse as a result of fix for SLING-6681(Replace commons.json usage in org.apache.sling.servlets.post)
> -----------------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: SLING-7346
>                 URL: https://issues.apache.org/jira/browse/SLING-7346
>             Project: Sling
>          Issue Type: Bug
>          Components: Servlets
>    Affects Versions: Servlets Post 2.3.22
>            Reporter: Rahul Bhardwaj
>            Assignee: Karl Pauls
>            Priority: Major
>             Fix For: Servlets Post 2.3.24
>
>
> If you set a value of type as map as a custom property in response type, instead of parsing properly, whole map is converted into one string and therefore, json response does not reach client side in an orderly fashion.
> This can be attributed to [0] which was merged as part of fix for SLING-6681(Replace commons.json usage in org.apache.sling.servlets.post)
> [0] -https://github.com/apache/sling/commit/a598bd4f6e9fc4f967e118de705643a04a47bc44#diff-2ff02a567147f2cbef2e344d5338dd14R106



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)