cxf-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Piotr Klimczak (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CXF-4920) TransformationInInterceptor fails when XML contains same namespace with different prefixes
Date Wed, 27 Mar 2013 13:41:20 GMT

    [ https://issues.apache.org/jira/browse/CXF-4920?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13615259#comment-13615259
] 

Piotr Klimczak commented on CXF-4920:
-------------------------------------

Thanks Aki for your effort.

It will take me some time to test it in real life, but as I see it should be ok becauese the
main reason of my problem has been removed.

I have seen your changes and I have noticed that PREFIXES map can be removed at all.
Just remove prefixes from here: 
{code}
        if (!prefixes.isEmpty()) {
            Map<String, String> cache = prefixes.getFirst();
            for (Map<String, String> pfs : prefixes) {
{code}
and replace them by entrySet on namespaces.

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
>         Environment: FuseESB 4.4.1-07-11 on SLES
>            Reporter: Piotr Klimczak
>            Assignee: Aki Yoshida
>            Priority: Critical
>              Labels: core, failed, interceptors, missing, namespace, prefix, transform
>         Attachments: CXF4920.diff, CXF4920-v2.5.X.diff, CXF4920-v2.6.X.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

Mime
View raw message