Mailing-List: contact user-help@abdera.apache.org; run by ezmlm
Precedence: bulk
Reply-To: user@abdera.apache.org
Received-SPF: pass (athena.apache.org: domain of jasnell@gmail.com designates
 209.85.214.42 as permitted sender)
MIME-Version: 1.0
In-Reply-To: <CAA0FFFC.B9EF%matthewj@oclc.org>
References: <CAA0FFFC.B9EF%matthewj@oclc.org>
Date: Thu, 22 Sep 2011 12:54:29 -0700
Message-ID: 
 <CABP7Rbc4Kz=uT6rh05cjnHmqCn0qeaBpCZrYadmcvhwkDyXx2g@mail.gmail.com>
Subject: Re: Question about JSON output from Abdera
From: James Snell <jasnell@gmail.com>
To: user@abdera.apache.org
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

Well, that's the way it was originally implemented, yes... but that
doesn't necessarily means that's the way it should work. There's never
been a single, generally accepted best practice for Atom serialized as
JSON so it's difficult to say for sure what the behavior should be. It
definitely might be time to revisit this in the new abdera2 codebase.

On Thu, Sep 22, 2011 at 12:08 PM, matthewj <matthewj@oclc.org> wrote:
> Hi,
>
> I am using Abdera in a web service to output Atom in both xml and json. =
=A0The
> xml is fine, but I have a question about the json representation. =A0I am
> serializing an object into an Entry=B9s content element, which is not a
> problem with xml. =A0However, when I request JSON I expect {=B3id=B2:=B2a=
sdf=B2,
> =B3title=B2:=B2title=B2, =B3content=B2: {=B3something=B2: =B3foobar=B2}},=
 but get:
>>>
>>> {
>>> =A0"id":"asdf",
>>> =A0"title":"title",
>>> =A0"content":"{\"something\":\"foobar\"}",
>>> =A0"updated":"2011-09-15T18:13:39.401Z"
>>> }
>>>
>>>
> Is this the appropriate result in JSON (the content element represented a=
s
> text)?
>
> Thanks,
> Jack Matthews
>