Hi Christopher, you should take a look at the following example: http://activemq.apache.org/camel/better-jms-transport-for-cxf-webservice-using-apache-camel.html
This tutorial describes how to use the camel transport for cxf. It is a better integration with cxf than using the cxf endpoint.
If the only thing you want to have is a better jms configuration for cxf you can also wait for cxf 2.1.3 which will be out in one or two weeks.
Then cxf will include a new much better configuration for jms endpoints. Greetings Christian huntc schrieb:
Hi there, I'm looking for a little guidance on best-practice use of CXF and Camel. I have a CXF based web service and I would like to publish the payload it receives to a topic. I then want various subscribers to the topic to receive the payload and subsequently process it. My CXF service is presently housed in a Tomcat container, but I'm thinking that I should use the Spring container and house a Camel context. I would then declare my CXF service to my Camel context so that I could route from it. Does this sound like the right approach? If so then does my CXF service implementation become obsolete? i.e. is it just my SEI that gets used if all that I want to do is publish the payload it receives to the topic? Kind regards, Christopher
-- Christian Schneider --- http://www.liquid-reality.de
