users@jersey.java.net

Re: [Jersey] Problem unmarshalling json with XSD using elementformdefault=qualified

From: Jakub Podlesak <Jakub.Podlesak_at_Sun.COM>
Date: Fri, 22 May 2009 11:18:57 +0200

On Thu, May 21, 2009 at 08:27:04PM -0600, davidj_at_lynxlogic.com wrote:
> I have an XSD I'm using to generate JAXB annotated java classes, and I'm
> attempting to use jersey's natural notation implementation to unmarshal
> JSON with them. If elementFormDefault on my XSD is set to unqualified,
> the JSON is correctly unmarshalled. However, if I set it to qualified,
> then only the attributes on the root element are unmarshalled; any child
> elements and their attributes are null on the unmarshalled object.
>
> I've looked around the source code and javadoc and there don't appear to
> be any configuration settings relating to namespace for the natural
> notation. Is there a known issue with this or something I'm missing?

Namespace support for Jersey internal notations is missing at the moment.
I am working on adding this. For the natural notation
there is a feature missing in stable JAXB RI at the moment,
which will prevent this to work until the next JAXB RI version 2.1.12
is available (i was told, it should be released in the late summer/early autumn).

~Jakub

>
> Thanks,
> David Johnson
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe_at_jersey.dev.java.net
> For additional commands, e-mail: users-help_at_jersey.dev.java.net
>