You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@cxf.apache.org by "Adrian Corcoran (JIRA)" <ji...@apache.org> on 2007/11/16 17:53:43 UTC
[jira] Created: (CXF-1216) WS-Addressing & .net Interop
WS-Addressing & .net Interop
----------------------------
Key: CXF-1216
URL: https://issues.apache.org/jira/browse/CXF-1216
Project: CXF
Issue Type: Bug
Components: WS-* Components
Affects Versions: 2.0.3
Environment: cxf 2.0.3 running withjava version "1.5.0_11" On Tomcat 5.5.25
client consumer on .net 2.0.50727 & WSE 3.0
Reporter: Adrian Corcoran
There seems to be a issue with WS-addressing (http://schemas.xmlsoap.org/ws/2004/08/addressin) & a .net consumer. .NET 2.0 expects the response header to comply to
/wsa:RelatesTo/@RelationshipType
This OPTIONAL attribute (of type xs:QName) conveys the relationship type as a QName. When absent, the implied value of this attribute is wsa:Reply.
See: http://www.w3.org/Submission/ws-addressing/
However the header contains:
<RelatesTo
xmlns="http://schemas.xmlsoap.org/ws/2004/08/addressing"
RelationshipType="reply">
urn:uuid:b33fc856-dbae-4034-ac6f-e2d53b593722
</RelatesTo>
As per Sergey the suggested fix is to only include the RelationshipType if it is not the default "Reply" value.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Resolved: (CXF-1216) WS-Addressing & .net Interop
Posted by "maomaode (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CXF-1216?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
maomaode resolved CXF-1216.
---------------------------
Resolution: Fixed
Fix Version/s: 2.0.4
> WS-Addressing & .net Interop
> ----------------------------
>
> Key: CXF-1216
> URL: https://issues.apache.org/jira/browse/CXF-1216
> Project: CXF
> Issue Type: Bug
> Components: WS-* Components
> Affects Versions: 2.0.3
> Environment: cxf 2.0.3 running withjava version "1.5.0_11" On Tomcat 5.5.25
> client consumer on .net 2.0.50727 & WSE 3.0
> Reporter: Adrian Corcoran
> Assignee: maomaode
> Fix For: 2.0.4
>
> Attachments: cxf-2.0.3.patch
>
>
> There seems to be a issue with WS-addressing (http://schemas.xmlsoap.org/ws/2004/08/addressin) & a .net consumer. .NET 2.0 expects the response header to comply to
> /wsa:RelatesTo/@RelationshipType
> This OPTIONAL attribute (of type xs:QName) conveys the relationship type as a QName. When absent, the implied value of this attribute is wsa:Reply.
> See: http://www.w3.org/Submission/ws-addressing/
> However the header contains:
> <RelatesTo
> xmlns="http://schemas.xmlsoap.org/ws/2004/08/addressing"
> RelationshipType="reply">
> urn:uuid:b33fc856-dbae-4034-ac6f-e2d53b593722
> </RelatesTo>
> As per Sergey the suggested fix is to only include the RelationshipType if it is not the default "Reply" value.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Assigned: (CXF-1216) WS-Addressing & .net Interop
Posted by "maomaode (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CXF-1216?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
maomaode reassigned CXF-1216:
-----------------------------
Assignee: maomaode
> WS-Addressing & .net Interop
> ----------------------------
>
> Key: CXF-1216
> URL: https://issues.apache.org/jira/browse/CXF-1216
> Project: CXF
> Issue Type: Bug
> Components: WS-* Components
> Affects Versions: 2.0.3
> Environment: cxf 2.0.3 running withjava version "1.5.0_11" On Tomcat 5.5.25
> client consumer on .net 2.0.50727 & WSE 3.0
> Reporter: Adrian Corcoran
> Assignee: maomaode
> Attachments: cxf-2.0.3.patch
>
>
> There seems to be a issue with WS-addressing (http://schemas.xmlsoap.org/ws/2004/08/addressin) & a .net consumer. .NET 2.0 expects the response header to comply to
> /wsa:RelatesTo/@RelationshipType
> This OPTIONAL attribute (of type xs:QName) conveys the relationship type as a QName. When absent, the implied value of this attribute is wsa:Reply.
> See: http://www.w3.org/Submission/ws-addressing/
> However the header contains:
> <RelatesTo
> xmlns="http://schemas.xmlsoap.org/ws/2004/08/addressing"
> RelationshipType="reply">
> urn:uuid:b33fc856-dbae-4034-ac6f-e2d53b593722
> </RelatesTo>
> As per Sergey the suggested fix is to only include the RelationshipType if it is not the default "Reply" value.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (CXF-1216) WS-Addressing & .net Interop
Posted by "Adrian Corcoran (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CXF-1216?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Adrian Corcoran updated CXF-1216:
---------------------------------
Attachment: cxf-2.0.3.patch
Path to fix issue. Only class effected is VersionTransformer
> WS-Addressing & .net Interop
> ----------------------------
>
> Key: CXF-1216
> URL: https://issues.apache.org/jira/browse/CXF-1216
> Project: CXF
> Issue Type: Bug
> Components: WS-* Components
> Affects Versions: 2.0.3
> Environment: cxf 2.0.3 running withjava version "1.5.0_11" On Tomcat 5.5.25
> client consumer on .net 2.0.50727 & WSE 3.0
> Reporter: Adrian Corcoran
> Attachments: cxf-2.0.3.patch
>
>
> There seems to be a issue with WS-addressing (http://schemas.xmlsoap.org/ws/2004/08/addressin) & a .net consumer. .NET 2.0 expects the response header to comply to
> /wsa:RelatesTo/@RelationshipType
> This OPTIONAL attribute (of type xs:QName) conveys the relationship type as a QName. When absent, the implied value of this attribute is wsa:Reply.
> See: http://www.w3.org/Submission/ws-addressing/
> However the header contains:
> <RelatesTo
> xmlns="http://schemas.xmlsoap.org/ws/2004/08/addressing"
> RelationshipType="reply">
> urn:uuid:b33fc856-dbae-4034-ac6f-e2d53b593722
> </RelatesTo>
> As per Sergey the suggested fix is to only include the RelationshipType if it is not the default "Reply" value.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.