btw, I installed java 6 update 18 and removed the jaxb 2.1.x from the
deployment package.. and it is working fine.. so I believe it is
required just for servers running on obsolete JVMs..
On Mon, Jan 18, 2010 at 12:35 PM, Paul Sandoz <Paul.Sandoz_at_sun.com> wrote:
>
> On Jan 16, 2010, at 12:47 AM, ycx4321 wrote:
>
> Hello,
>
> I cannot produce the "natural" JSON in Google App Engine using the Jersey
> example here:
> https://jersey.dev.java.net/nonav/documentation/latest/user-guide.html#d4e557
>
> Even though I called JSONConfiguration.natural().build() in my own
> ContextResolver, The JSON always has the xml root tag (i.e. the default) as
> if I have not extend ContextResolver. I noted that the JSON natural format
> in Jersey requires jaxb-impl.2.1.10 and above. I am using the Jersey
> 1.1.5-ea 20100104 build which bundles jaxb-impl.2.1.12. Is this because the
> jax-impl version in Google App Engine is not up to date to the version
> required by Jersey?
>
>
> I think so. Are you including the jaxb-impl.2.1.12 in the application
> deployment?
> I presume that the JAXB version utilized on GAE deployment will be the same
> version in the JDK 6 version they recommend.
> I would have expected that you would have got an exception on GAE deployment
> if you attempted to do:
> JSONConfiguration.natural().build()
> as Jersey would not have been able to detect the required JAXB version. If
> not and you are including the jaxb-impl.2.1.12 in the deployment then all i
> can suggest is some class loading differences such that even though Jersey
> detects certain classes in jaxb-impl.2.1.12 that version is in fact not
> used.
> Paul.
--
------------------------------------------
Felipe Gaúcho
10+ Java Programmer
CEJUG Senior Advisor