Hi,
just my two cents, I don't like BadgerFish and generated JSON from objects,
because several requests might return different JSON representations,
http://stephan.reposita.org/archives/2008/04/04/rest-lean-json-and-xml-from-the-same-code/
http://stephan.reposita.org/archives/2008/03/18/experiments-for-nicely-generating-json/
Additionally I wrote a Message Body Writer which encapsulates the toJson()
call.
BadgerFish and full object graph dumps in JSON seem to contradict the
purpose
of JSON, a lean, fast to parse and read data format.
Regards
-stephan
On Fri, Apr 4, 2008 at 11:14 AM, Seamus Kerrigan (skerriga) <
skerriga_at_cisco.com> wrote:
> Hi,
>
> I've been doing some work with Jersey for the past while but yesterday I
> got to try out Jersey 0.7 and it looks as though Badgerfish notation is
> now the default JSON format again? I found that early Jersey versions
> were using Badgerfish by default but 0.6 was using the Mapped notation
> as it's default as outlined in Jakub's blog
> http://blogs.sun.com/japod/entry/better_json_available_in_jersey.
>
> I just have a couple of questions on this JSON formatting:
> - Is Badgerfish likely to be the preferred JSON notation in future
> Jersey releases?
> - Will XmlAttributes be supported in the Mapped/Mapped-Jettison
> formats?
> - The blog outlines a method of changing between JSON formats by
> defining a ContextResolver. Is still this valid in 0.7? I gave this a
> very quick try yesterday but was unsuccessful.
>
> Many thanks,
> Seamus
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe_at_jersey.dev.java.net
> For additional commands, e-mail: users-help_at_jersey.dev.java.net
>
>
--
Stephan Schmidt :: stephan_at_reposita.org
Reposita Open Source - Monitor your software development
http://www.reposita.org
Blog at http://stephan.reposita.org - No signal. No noise.