You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@cxf.apache.org by na...@zero.allmail.net on 2010/07/02 19:14:12 UTC
JAX-RS, jaxbElementClassMap and a service's WADL
Hi again CXF cognoscenti,
I ran into a situation where I needed to use the jaxbElementClassMap property of JAXBElementProvider to get some unannotated classes to successfully marshal to XML. What I noticed is that when a return type is annotated with @XmlRootElement, the WADL for the service includes schema for that return type, but when I remove the annotation and use the jaxbElementClassMap instead, that schema is no longer provided. Is there some trick to accomplish this that I'm simply unaware of? Or is this an issue that could / should be remedied? If so, I'll happily create a feature request for it.
Thank you!
Peter Giles
Re: JAX-RS, jaxbElementClassMap and a service's WADL
Posted by Sergey Beryozkin <sb...@gmail.com>.
Hi - I applied a slightly modified patch on behalf of Matthew Smith, but it
can help with cases when say Response is returned but it is know what JAXB
class will be used as an entity.
The problem is that WADLGenerator does not know about the providers and
their configuration which will be used to deal with a given type.
Perhaps something can be done in cases when a given type (without
XMLRootElement) gets wrapped into a JAXBElement with the help of the XmlName
annotation - but I don't know if JAXB will properly generate a schema
*element* as opposed to a complex type definition, from such a syntesized
element
If you could experiment with JAXBContext alone and see if it could generate
a schema from a JAXBElement, then it would help to see if anything can be
done to address this case or not
cheers, Sergey
On Fri, Jul 2, 2010 at 6:14 PM, <na...@zero.allmail.net> wrote:
> Hi again CXF cognoscenti,
>
> I ran into a situation where I needed to use the jaxbElementClassMap
> property of JAXBElementProvider to get some unannotated classes to
> successfully marshal to XML. What I noticed is that when a return type is
> annotated with @XmlRootElement, the WADL for the service includes schema for
> that return type, but when I remove the annotation and use the
> jaxbElementClassMap instead, that schema is no longer provided. Is there
> some trick to accomplish this that I'm simply unaware of? Or is this an
> issue that could / should be remedied? If so, I'll happily create a feature
> request for it.
>
> Thank you!
> Peter Giles
>
>