Return-Path: X-Original-To: apmail-devicemap-dev-archive@www.apache.org Delivered-To: apmail-devicemap-dev-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id C9E93CF4A for ; Tue, 30 Dec 2014 15:38:10 +0000 (UTC) Received: (qmail 65657 invoked by uid 500); 30 Dec 2014 15:38:11 -0000 Delivered-To: apmail-devicemap-dev-archive@devicemap.apache.org Received: (qmail 65616 invoked by uid 500); 30 Dec 2014 15:38:11 -0000 Mailing-List: contact dev-help@devicemap.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@devicemap.apache.org Delivered-To: mailing list dev@devicemap.apache.org Received: (qmail 65604 invoked by uid 99); 30 Dec 2014 15:38:08 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 30 Dec 2014 15:38:08 +0000 X-ASF-Spam-Status: No, hits=1.5 required=5.0 tests=HTML_MESSAGE,RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of werner.keil@gmail.com designates 209.85.214.171 as permitted sender) Received: from [209.85.214.171] (HELO mail-ob0-f171.google.com) (209.85.214.171) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 30 Dec 2014 15:38:03 +0000 Received: by mail-ob0-f171.google.com with SMTP id uz6so45154344obc.2 for ; Tue, 30 Dec 2014 07:37:42 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; bh=51pKJaQ63vwEmJ2AqliM6DtEe4bCE6Ke+xaPGOM6UUc=; b=C3YBychi394RRm6WSvoYHs6e7m6/aATnbDBCQWZv+LXGVKL7CMV6V5kF95SSpyZ9yM NPp2tK4SryPkU9YMxyOfewzVr07H7mHaR5Pi3wWJ4KR2AX/KjN05MVM3uZblKO3pejaH O7+1r92LGOsZ6dWKzlhqEB2NHPTN1OcpUAg9EGP9vNBhQUAYz3HhGTpIvvdGZ9zXW5Vy Hu8cGWN9xb5IwIaIkD+7+vPfhGZUthJ9/vAEAnPFukskuDODo3qA0JVPyADlhQW2OFhU LThxbU1bcFL+7DbpVxLfYbKb4Bow9mxD3nfveTihLPKfaNd8lI8fSkYk5D0CRC3R4qnm S4og== MIME-Version: 1.0 X-Received: by 10.60.144.194 with SMTP id so2mr33163540oeb.65.1419953862725; Tue, 30 Dec 2014 07:37:42 -0800 (PST) Received: by 10.202.129.131 with HTTP; Tue, 30 Dec 2014 07:37:42 -0800 (PST) In-Reply-To: References: Date: Tue, 30 Dec 2014 16:37:42 +0100 Message-ID: Subject: Re: JSON toString methods in data classes From: Werner Keil To: dev@devicemap.apache.org Content-Type: multipart/alternative; boundary=047d7b3a94fe95d6e5050b70c5c6 X-Virus-Checked: Checked by ClamAV on apache.org --047d7b3a94fe95d6e5050b70c5c6 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Maybe we can abstract that a bit, e.g. a formatter/renderer that offers multiple output options. Whatever is best as default could be used behind toString() if JSON is best, why not, but it would be good to abstract data from the output/representation. Werner On Tue, Dec 30, 2014 at 2:19 PM, Reza Naghibi < reza.naghibi@yahoo.com.invalid> wrote: > JSON is used in our servlet, spring, and console examples. > > > >
-------- Original message --------
From: Volkan Yaz=C4=B1c= =C4=B1 < > volkan.yazici@gmail.com>
Date:12/30/2014 5:02 AM (GMT-05:00) >
To: dev@devicemap.apache.org
Cc: >
Subject: JSON toString methods in data classes
>
Hi, > > Is there a particular reason for why are we returning JSON formatted outp= ut > from toString() methods of o.a.d.data.* classes? This convention is not > followed by .NET/VB clients, if I am not mistaken. > > Best. > --047d7b3a94fe95d6e5050b70c5c6--