Hi,
Thanks for the stack trace. That definitely proves it! Thankfully this
is an easy fix :-)
On Oct 23, 2009, at 9:10 PM, Rod Fitzsimmons Frey wrote:
>> One work around is switch to the natural JSON convention. I checked
>> the StAX writer for that and it does not have the same issue with
>> exceptions.
>>
>> Paul.
>
> I'm afraid I don't know what you mean by the natural JSON convention.
>
See here:
https://jersey.dev.java.net/nonav/apidocs/1.1.2-ea/jersey/com/sun/jersey/api/json/package-summary.html
https://jersey.dev.java.net/nonav/documentation/1.1.2-ea/user-guide.html
#d4e579
Note that it might give you slightly different JSON output.
Also Note that there is another issue with enabling the natural JSON
convention with SE 6 and GlassFish when Jersey is installed with
GlassFish that we are currently trying to resolve. If you are using
Tomcat with Jersey jars in the war there should not be an issue.
Paul.