From dev-return-85023-archive-asf-public=cust-asf.ponee.io@sling.apache.org Fri Jan 5 09:28:04 2018 Return-Path: X-Original-To: archive-asf-public@eu.ponee.io Delivered-To: archive-asf-public@eu.ponee.io Received: from cust-asf.ponee.io (cust-asf.ponee.io [163.172.22.183]) by mx-eu-01.ponee.io (Postfix) with ESMTP id 78680180647 for ; Fri, 5 Jan 2018 09:28:04 +0100 (CET) Received: by cust-asf.ponee.io (Postfix) id 68486160C3B; Fri, 5 Jan 2018 08:28:04 +0000 (UTC) Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by cust-asf.ponee.io (Postfix) with SMTP id B69C3160C19 for ; Fri, 5 Jan 2018 09:28:03 +0100 (CET) Received: (qmail 84024 invoked by uid 500); 5 Jan 2018 08:28:02 -0000 Mailing-List: contact dev-help@sling.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@sling.apache.org Delivered-To: mailing list dev@sling.apache.org Received: (qmail 84004 invoked by uid 99); 5 Jan 2018 08:28:02 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd1-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 05 Jan 2018 08:28:02 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd1-us-west.apache.org (ASF Mail Server at spamd1-us-west.apache.org) with ESMTP id EECCCC2177 for ; Fri, 5 Jan 2018 08:28:01 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd1-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: -99.211 X-Spam-Level: X-Spam-Status: No, score=-99.211 tagged_above=-999 required=6.31 tests=[KAM_ASCII_DIVIDERS=0.8, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, USER_IN_WHITELIST=-100] autolearn=disabled Received: from mx1-lw-us.apache.org ([10.40.0.8]) by localhost (spamd1-us-west.apache.org [10.40.0.7]) (amavisd-new, port 10024) with ESMTP id kCgwLMh88jtn for ; Fri, 5 Jan 2018 08:28:01 +0000 (UTC) Received: from mailrelay1-us-west.apache.org (mailrelay1-us-west.apache.org [209.188.14.139]) by mx1-lw-us.apache.org (ASF Mail Server at mx1-lw-us.apache.org) with ESMTP id 1D9615F3B5 for ; Fri, 5 Jan 2018 08:28:01 +0000 (UTC) Received: from jira-lw-us.apache.org (unknown [207.244.88.139]) by mailrelay1-us-west.apache.org (ASF Mail Server at mailrelay1-us-west.apache.org) with ESMTP id A2B48E0383 for ; Fri, 5 Jan 2018 08:28:00 +0000 (UTC) Received: from jira-lw-us.apache.org (localhost [127.0.0.1]) by jira-lw-us.apache.org (ASF Mail Server at jira-lw-us.apache.org) with ESMTP id 617C7240E2 for ; Fri, 5 Jan 2018 08:28:00 +0000 (UTC) Date: Fri, 5 Jan 2018 08:28:00 +0000 (UTC) From: "Rahul Bhardwaj (JIRA)" To: dev@sling.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (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) MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/SLING-7346?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16312697#comment-16312697 ] Rahul Bhardwaj commented on SLING-7346: --------------------------------------- Updated PR-1[0] to incorporate review comments and also added test case to the same PR. Closed PR-2 https://github.com/apache/sling-org-apache-sling-servlets-post/pull/1 > 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 > 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 (v6.4.14#64029)