Thanks Willem. The InquiryRoute constructs the data that needs to be returned by the Web Service call (accomplished in a POJO) so the operation cannot be performed asynchronously (i.e. the caller is waiting for a response).
The reason I put the main logic in a separate route is that I wanted to plan for the possibility of multiple front-ends to the service (i.e. JAXWS, JAXRS, JMS, etc.). In this case, all of the front-ends would forward their messages to the InquiryRoute. I'm assuming that this is a valid pattern, or would it be best to put the logic inline for each front-end? I noticed that the CXF component has an attribute called /synchronous/ which is set to false by default. Should it bet set to true for the scenario that I'm trying to accomplish? -- View this message in context: http://camel.465427.n5.nabble.com/Camel-CXF-Endpoint-Performance-Threading-tp5748984p5749098.html Sent from the Camel - Users mailing list archive at Nabble.com.
