users@jersey.java.net

Re: Re: [Jersey] RE: array handling in JAXB to JSON conversion

From: Jakub Podlesak <Jakub.Podlesak_at_Sun.COM>
Date: Mon, 09 Mar 2009 16:47:25 +0100

Hi Moiz,

You have hit an edge case, and i am afraid i have no good news for you.
Jersey JSON provider takes what JAXB gives out, and the information
about the emtpy array is obviously missing.

One option would be to try out the provider mentioned by Tatu.
Have you had a chance to test it yet?

Another option would be to use the low-level JSONObect/JSONArray
providers (used in bookmark example [1].

~Jakub

[1]http://download.java.net/maven/2/com/sun/jersey/samples/bookmark/1.0.3-SNAPSHOT/bookmark-1.0.3-SNAPSHOT-project.zip


On Fri, Mar 06, 2009 at 07:21:51AM -0800, Moiz Dohadwala wrote:
> I have tried that too, but hasn't worked either.
>
> -Moiz
>
> From: Wilhelmsen Tor Iver [mailto:TorIverW_at_arrive.no]
> Sent: Friday, March 06, 2009 5:01 AM
> To: users_at_jersey.dev.java.net
> Subject: Re: [Jersey] RE: array handling in JAXB to JSON conversion
>
> Try adding required=true to this:
>
> @XmlElement(name="items")
> List<Item> items;
>
> or else tell JAXB to treat nulls and empty collections differently. We ran into the same issue where null/empty elements were absent from the XML and thus a JAXB client would generate classes missing these properties.