[
http://jira.codehaus.org/browse/XFIRE-977?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alexander Bollaert updated XFIRE-977:
-------------------------------------
Attachment: XFIRE-977.patch
This patch fixes the issue for me, but I haven't done much further checking...
> Client generated wrong if header element is not in separate message
> -------------------------------------------------------------------
>
> Key: XFIRE-977
> URL: http://jira.codehaus.org/browse/XFIRE-977
> Project: XFire
> Issue Type: Bug
> Components: Generator
> Affects Versions: 1.2.6
> Reporter: Chris Moesel
> Assignee: Tomasz Sztelak
> Attachments: pizza_service_xfire_wsdl2java_header_bug.zip,
> XFIRE-977.patch
>
>
> If an object is expected to be passed in the header, and the wsdl defines it
> as a part in the request message (rather than in its own message), then XFire
> generates the client incorrectly. For each operation using the header, it
> will define two parameters for the header object. One will be serialized
> into the soap header and the other will be serialized into the message body.
> Xfire works correctly, however, if the header is defined in its own message
> instead of as a part in the request message.
> This causes interoperability problems with CXF 2.0 RC, since CXF currently
> requires header objects to be defined as a part in the request message. This
> is apparently the OS-I suggested way of doing things. See
> https://issues.apache.org/jira/browse/CXF-602 and
> http://www.mail-archive.com/[EMAIL PROTECTED]/msg00231.html.
> I'll try to get a quick example together to demonstrate this.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe from this list please visit:
http://xircles.codehaus.org/manage_email
