Hi Christian,
thanks for your reply.
I had a look at the code, too. I guess my problem is that I need to a
conduitSelectorPrefix with WebSphere MQ ("ID:"), otherwise CXF cannot
correlate anything at all.
My attempts to hack the conduit to support this have unfortunately not been
successful so far.
I'm running 2.3.2 at the moment but I think the code's pretty much unchanged
in trunk.
Jens
Christian Schneider wrote:
>
> sorry for the delay. I just created a testcase for this as I found none
> that was testing this case.
>
> See below for the algorithm to determine the correlation id to send out.
> So if you do not set a conduitSelectorPrefix and use a sync call and do
> not set useConduitIdSelector then it should work. In this case CXF will
> correlate using the message id.
>
> That is at least the trunk setting. What version of CXF are you using?
>
> Christian
>
--
View this message in context:
http://cxf.547215.n5.nabble.com/JMS-Message-Correlation-in-CXF-2-3-tp4830121p4856808.html
Sent from the cxf-user mailing list archive at Nabble.com.
