Hi Greg,
What you describe is JSON data using Badgerfish[1] notation (see [2]).
Such a JSON is produced/consumed by Jersey JAXB entity providers.
They allow you to produce JSON and/or XML from the very same JAXB bean.
I know that the produced JSON format is somehow not convenient to work with
for JavaScript developers.
Beside the above, by using JSON specific entity providers (see [3]),
you can easily control what is being generated and you are
not only constrained to the Badgerfish.
However, we plan to further work on JAXB providers to support more
JSON notations to be produced out of JAXB.
I would welcome any examples of JSON data you would like to be generated.
And also any specific requirements on the desired JSON notation.
CCing the dev list so that others have a chance to communicate their
requirements as well.
Thanks,
~Jakub
[1]
http://badgerfish.ning.com/
[2]
http://blogs.sun.com/japod/entry/json_representation_of_jaxb_object
[3]
http://blogs.sun.com/japod/entry/json_entity_providers_in_jersey
On Tue, Oct 16, 2007 at 12:42:22AM -0700, Greg Murray wrote:
> Hi Jakub,
>
> The JSON format is in essence serialized XML which is not friendly or
> favorable to JavaScript developers.
>
> Arun has worked with Jersey a bit more than myself and may be able to
> help with the details.
>
> Arun, if you have time with all the traveling could you help out
> identifying the issues again? I need to sleep ;-)
>
> Thanks in advance.
>
> -G
>