Thanks for the response Willem! I tried to set the response of the out message in EmptyProcessor, by exchange.getOut().setBody(exchange.getIn().getBody()); but I have the same symptom. In fact, when I set a breakpoint on that line within EmptyProcessor, it is never hit.
It seems that the order in which I run the tests in https://svn.apache.org/repos/asf/camel/trunk/components/camel-cxf/src/test/java/org/apache/camel/component/cxf/jaxrs/CxfRsProducerTest.java matters. When I add the EmptyProcessor route, the first two tests throw java.lang.IllegalArgumentException: The configure bean is not the instance of org.apache.cxf.jaxrs.JAXRSServerFactoryBean, and the third test fails with the response being null, even if I reorder the first 3 tests: testAddCustomerUniqueResponseCodeWithHttpClientAPI(), testGetCostumerWithClientProxyAPI(), testGetCostumersWithClientProxyAPI(). There must be something that I am doing conceptually wrong... in the route? Is it legitimate to just have a process run on a cxfrs endpoint be the entirety of the route? -Shan -- View this message in context: http://camel.465427.n5.nabble.com/CXFRS-and-Processing-tp5596053p5601140.html Sent from the Camel - Users mailing list archive at Nabble.com.
