cxf-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Daniel Kulp (JIRA)" <j...@apache.org>
Subject [jira] Assigned: (CXF-1002) Message Part is not named correctly (always called "fault") - this breaks XFire backward compatibility - Patch attached
Date Tue, 18 Sep 2007 16:53:44 GMT

     [ https://issues.apache.org/jira/browse/CXF-1002?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Daniel Kulp reassigned CXF-1002:
--------------------------------

    Assignee: Daniel Kulp  (was: Dan Diephouse)

> Message Part is not named correctly (always called "fault") - this breaks XFire backward
compatibility - Patch attached
> -----------------------------------------------------------------------------------------------------------------------
>
>                 Key: CXF-1002
>                 URL: https://issues.apache.org/jira/browse/CXF-1002
>             Project: CXF
>          Issue Type: Improvement
>          Components: JAX-WS Runtime
>    Affects Versions: 2.0.1, 2.0.2
>         Environment: Platform independent.
>            Reporter: Zarar Siddiqi
>            Assignee: Daniel Kulp
>         Attachments: MessagePartNameFixForXFireBackwardCompatibility.patch
>
>
> There's a one-man discussion here:
> http://www.nabble.com/WSDL-part-name-incorrect.-How-do-you-change-it--tf4432101.html
> CXF always names the part of a fault as the word "fault".  IMHO it's better to name it
as the fault's simple class name as this is how things were with XFire.
> The simple patch attached fixes this.

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


Mime
View raw message