No problem. Thanks for clarifying.
There anyway still seem to be people experiencing
some backwards compatibility issues related to JSON format.
I am curious, what kind of environment/configuration
settings could cause this. Could you provide some details
on what was wrong at your end? Was it different container
behaving different way than GlassFish?
Thanks,
~Jakub
On 12/03/2010 02:48 PM, Ronak Patel wrote:
> I take it back....this is working as expected....there's another
> problem that's going on from my end. Thanks.
>
> ------------------------------------------------------------------------
> *From:* Ronak Patel <ronak2121_at_yahoo.com>
> *To:* users_at_jersey.java.net
> *Sent:* Fri, December 3, 2010 4:10:59 AM
> *Subject:* [Jersey] JSON Mapped Style different on Glassfish V2/V3
>
> Hello everyone,
>
> Has anyone noticed that the default Mapped JSON style is different
> between Glassfish Version 2 and Glassfish Version 3? They have
> different versions of JAXB...could that be the reason why?
>
> I recently upgraded from Glassfish V2 to Glassfish V3 and since I
> still have clients that depend on the usage of the old mapped JSON
> style, I thought setting a mapped provider (or choosing the defaults)
> would be enough...but the JSON string is different...
>
> Is there any way to make the JSON be the same between the two app
> server/JAXB versions?
>
> Ronak
>
>