You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@cxf.apache.org by "Zarar Siddiqi (JIRA)" <ji...@apache.org> on 2007/09/13 22:05:32 UTC
[jira] Created: (CXF-1002) Message Part is not named correctly
(always called "fault") - this breaks XFire backward compatibility - Patch
attached
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
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.
[jira] Assigned: (CXF-1002) Message Part is not named correctly
(always called "fault") - this breaks XFire backward compatibility - Patch
attached
Posted by "Dan Diephouse (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CXF-1002?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Dan Diephouse reassigned CXF-1002:
----------------------------------
Assignee: 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: Dan Diephouse
> 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.
[jira] Commented: (CXF-1002) Message Part is not named correctly
(always called "fault") - this breaks XFire backward compatibility - Patch
attached
Posted by "Dan Diephouse (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CXF-1002?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12527745 ]
Dan Diephouse commented on CXF-1002:
------------------------------------
OK, just looked at this - yeah this is fine I think.
> 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
> 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.
[jira] Resolved: (CXF-1002) Message Part is not named correctly
(always called "fault") - this breaks XFire backward compatibility - Patch
attached
Posted by "Daniel Kulp (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CXF-1002?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Daniel Kulp resolved CXF-1002.
------------------------------
Resolution: Fixed
Fix Version/s: 2.0.2
Patch applied. Thanks!
> 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
> Fix For: 2.0.2
>
> 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.
[jira] Updated: (CXF-1002) Message Part is not named correctly
(always called "fault") - this breaks XFire backward compatibility - Patch
attached
Posted by "Zarar Siddiqi (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CXF-1002?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Zarar Siddiqi updated CXF-1002:
-------------------------------
Attachment: MessagePartNameFixForXFireBackwardCompatibility.patch
Here's that patch.
> 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
> 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.
[jira] Assigned: (CXF-1002) Message Part is not named correctly
(always called "fault") - this breaks XFire backward compatibility - Patch
attached
Posted by "Daniel Kulp (JIRA)" <ji...@apache.org>.
[ 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.