[
https://issues.apache.org/jira/browse/CXF-926?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Daniel Kulp updated CXF-926:
----------------------------
Assignee: Daniel Kulp
Summary: JAX-WS code first fault mapping is not writing proper element
name on wire if detail has XmlRootElement (was: JAX-WS code first fault
mapping is not using @XmlRootElement names from detail type)
> JAX-WS code first fault mapping is not writing proper element name on wire if
> detail has XmlRootElement
> -------------------------------------------------------------------------------------------------------
>
> Key: CXF-926
> URL: https://issues.apache.org/jira/browse/CXF-926
> Project: CXF
> Issue Type: Bug
> Components: Core, JAX-WS Runtime, JAXB Databinding
> Affects Versions: 2.0.1
> Reporter: Daniel Kulp
> Assignee: Daniel Kulp
> Fix For: 2.0.2
>
>
> See: http://www.nabble.com/Handle-exceptions-on-the-client-side-tf4273066.html
> 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.
