Freeman Fang wrote:
>
> Hi,
>
> We needn't set the conduit into exchange explicitly.
> When you see the code in MAPAggregator
> ContextUtils.getConduit(conduit, message);
> It should run into AbstractConduitSelector.getSelectedConduit(), from
> which we get conduit from the EndpointInfo.
>
> Would you please try your tests with SMX 3.2.3 snapshot? I think the fix
> for SM-1593 should also fix this problem.
>
> Regards
> Freeman
>
>
Looks like the same thing happens with the 3.2.3 snapshot. Snapshot uses
2.0.9 version of cxf. Here is the ContextUtils.getConduit(conduit, message);
implementation:
public static Conduit getConduit(Conduit conduit, Message message) {
if (conduit == null) {
Exchange exchange = message.getExchange();
conduit = exchange != null ? exchange.getConduit(message) : null;
}
return conduit;
}
Exchange getConduit, does use the conduit selector, but that also seems
null.
Setting the conduit into the exchange in the CxfProvider still works. It
looks like the exchange wraps the conduit into a selector.
--
View this message in context:
http://www.nabble.com/CXF-Proxy-fault-problem-tp20053523p20132896.html
Sent from the ServiceMix - User mailing list archive at Nabble.com.
