Mailing-List: contact dev-help@camel.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@camel.apache.org
MIME-Version: 1.0
References: 
 <CAF8t5Xvp-kBsA4svL38=++RsTFfDA59H0pDYhgLCUvVpTbWtKA@mail.gmail.com>
In-Reply-To: 
 <CAF8t5Xvp-kBsA4svL38=++RsTFfDA59H0pDYhgLCUvVpTbWtKA@mail.gmail.com>
From: Henryk Konsek <hekonsek@gmail.com>
Date: Mon, 24 Aug 2015 14:37:35 +0000
Message-ID: 
 <CALhQg-aQw8ass6ShuWPpuoHssG8vMoD-USx6-yOqo7LjYHT1Uw@mail.gmail.com>
Subject: Re: Usefulness of the current Map or List to String conversion in
 Camel
To: "dev@camel.apache.org" <dev@camel.apache.org>
Content-Type: multipart/alternative; boundary=089e0122aefa86c456051e0f8f22

--089e0122aefa86c456051e0f8f22
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

+1

Actually we could remove toString() conversion at all, as it is useless
from the message handling point of view. Instead we could add the proper
conversions to the jackson or gson modules.

Cheers!

pon., 24.08.2015 o 13:54 u=C5=BCytkownik Aki Yoshida <elakito@gmail.com> na=
pisa=C5=82:

> Hi,
> Currently, the default conversion from Map or List to String is based
> on the JDK's default serialization. So, if you have a map having
> entries "name"=3D"peach", "taste"=3D"sweet", you get
>
> {name=3Dpeach, taste=3Dsweet}
>
> This representation is somewhat useless except for the logging
> purpose. This format does not handle special characters and it is not
> interoperable. So, I am wondering if we can instead use JSONObject's
> default serialization so that you will get instead
>
> {"name":"peach","taste":"sweet"}
>
> This string is interoperable and can be easily processed.
>
> If this conversion works directly (we could make it enabled or
> disabled using a property), I think that will be very practical for
> generic map and list objects.
>
> Comments appreciated.
>
> regards, aki
>
--=20
Henryk Konsek
http://about.me/hekonsek

--089e0122aefa86c456051e0f8f22--