[
https://issues.apache.org/jira/browse/CXF-4920?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13612557#comment-13612557
]
Piotr Klimczak commented on CXF-4920:
-------------------------------------
The patch was made for trunk and 2.7 version.
On 2.6.x and older it will fail.
If anybody will request then i can create a patch for 2.6.x, 2.5.x versions.
Greetings
Piotr Klimczak
> TransformationInInterceptor fails when XML contains same namespace with
> different prefixes
> ------------------------------------------------------------------------------------------
>
> Key: CXF-4920
> URL: https://issues.apache.org/jira/browse/CXF-4920
> Project: CXF
> Issue Type: Bug
> Components: Core
> Affects Versions: 2.3, 2.4, 2.5, 2.6, 2.7.3, 2.8.0
> Reporter: Piotr Klimczak
> Priority: Critical
> Labels: core, failed, interceptors, missing, namespace, prefix,
> transform
> Attachments: CXF4920.diff
>
>
> TransformationInInterceptor fails when XML contains same namespace with
> different prefixes.
> So for example this will fail:
> {code}
> <wireTransfer xmlns:q1="http://bar.com/foo"; xsi:type="q1:SwiftWireTransfer">
> ...
> </wireTransfer>
> <wireTransfer xmlns:q2="http://bar.com/foo"; xsi:type="q2:SwiftWireTransfer">
> ...
> </wireTransfer>
> {code}
> as for "q2:SwiftWireTransfer" the prefix q2 would be never found due to
> internal cache strategy.
> So the above bug blocks usage of such kind of XML message.
> Of cource using different prefixes for same namespaces is not a good
> practice, but when there is a need to "talk" with external vendor software
> (as in my situation) there might be no chance to fix it on second side.
> I have this already fixed.
> Will apply patch in few moments.
> Greetings,
> Piotr Klimczak
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
