Thanks for sharing this with us, I just updated the camel-cxf wiki page for it.
-- Willem Jiang Red Hat, Inc. Web: http://www.redhat.com Blog: http://willemjiang.blogspot.com (English) http://jnn.iteye.com (Chinese) Twitter: willemjiang Weibo: 姜宁willem On March 5, 2015 at 12:05:43 AM, g8torPaul ([email protected]) wrote: > All, > > I fixed the issue. After digging through the CXF code, I found the following > property: > > org.apache.cxf.interceptor.OneWayProcessorInterceptor.USE_ORIGINAL_THREAD > > I set this property on the CXF endpoint that is consuming from the JMS Queue > via Camel Transport. > > This property does not appear to be well documented, but it ensures that CXF > processes the message on the same Camel JMS Consumer thread which is what I > want to happen in this case. > > This also solves the issue of propagating a local transaction across the > endpoints since they now exist on the same thread. > > Hope this helps someone else out there, > > g8torPaul > > > > -- > View this message in context: > http://camel.465427.n5.nabble.com/Problem-with-Message-Order-using-Camel-JMS-and-CXF-tp5763503p5763594.html > > Sent from the Camel - Users mailing list archive at Nabble.com. >
