Hi,

I think we already fix this issue in smx 3.2.3 SNAPSHOT. [1] tracked this issue

[1]https://issues.apache.org/activemq/browse/SM-1556
Freeman

servicer-mixer wrote:
I'm currently using smx 3.2.2 with the following endpoints
cxf-consumer-bc=>cxf-provider-bc=>external service

The reply Envelope element from the external service looks like this:
<soap:Envelope xmlns:xop="http://www.w3.org/2004/08/xop/include";
   xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/";
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
   xmlns:xsd="http://www.w3.org/2001/XMLSchema";
xmlns:wsa="http://schemas.xmlsoap.org/ws/2004/08/addressing";
xmlns:wsse="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd"; xmlns:wsu="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd";>

However, the reply returned from cxf-consumer-bc is:
<soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/";>

I'm failing to parse the reply because one of the elements in the reply
looks like this:
<DeclineReason xsi:nil="true" />

I think this is similar to SM-1172, but the original namespace is declared
on the external reply and not the jbi message.

Is there any way to force the consumer to add namespace declarations to the
reply?

Thanks

Reply via email to