cxf-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Daniel Kulp (JIRA)" <>
Subject [jira] Commented: (CXF-926) JAX-WS code first fault mapping is not using @XmlRootElement names from detail type
Date Wed, 29 Aug 2007 19:26:31 GMT


Daniel Kulp commented on CXF-926:

Actually, according to JAX-WS spec (section 2.5), we are NOT supposed to use the XmlRootElement
at all and instead use the element name generated from the WebFault annotation.   Thus, this
is a problem with the serialization of the fault as we need to specify the proper QName instead
of using the XmlRootElement qname.

> JAX-WS code first fault mapping is not using @XmlRootElement names from detail type
> -----------------------------------------------------------------------------------
>                 Key: CXF-926
>                 URL:
>             Project: CXF
>          Issue Type: Bug
>          Components: Core, JAX-WS Runtime, JAXB Databinding
>    Affects Versions: 2.0.1
>            Reporter: Daniel Kulp
>             Fix For: 2.0.2
> See:
> When getting a list of expected element names, it's not using the information from the
@XmlRootElement to determine the element names.  It's only  using the WebFault information.
  Unfortunately, it's not really using that correctly either.   If the @WebFault annotation
doesn't put the proper namespace in, it will have issues with as well.
> There is a semi-workaround:
> If you completely specify the @WebFault annotation (including the targetNamespace), and
then remove the @XmlRootElement annotation on the details, it would work.   Or, make sure
the data in the @WebFault matches the data in the @XmlRootElement.    That's definitely not
an ideal situation though.   The element names may not  be exactly what you want that way.

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

View raw message