TransformationInInterceptor fails when XML contains same namespace with different prefixes.
So for example this will fail:
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.