Hi, Maybe you should take a look at the LoanBroker example[1] of Camel. There are two versions of Loan Service which look like your application.
It is not easy to adapter an asynchronized JMS message system with the Request/Response WebService message model effectively. Maybe you need to do some modification on your routing rule. [1] http://cwiki.apache.org/CAMEL/loan-broker-example.html Willem ychawla wrote: > Hello Fellow Camel Riders, > I have an application that is using camel for routing and it working quite > nicely. There are two allowed input paths for a message, one is a web > service and the other is direct file system access. > > When a user drops a file onto the file system, it is processed by the file > component, validated, assigned a message ID, routed to workflows (JMS > queues) and a confirmation or error is sent to a folder for the end user to > inspect. > > Our current strategy with the web service is to extract a message payload > and write it to the file system folder that is polled by the file component. > The web service will then poll a confirmation or error folder and then reads > the confirmation or error and uses that to create a web service response. > > The polling done by the web service is making me increasingly nervous > because it is a recipe for performance problems. Seems like way too much > unnecessary file I/O. > > The web service is written in CXF and the Camel Routes are already setup. > It seems like we just need to wire the CXF web service to the routes we > already have. We also want to wire the web service response to either the > confirmation or error rather than writing it to the file system and then > reading it from there. > > I am assuming this is all possible through the CXF component, but I want to > confirm that I am interpreting the functionality of the CXF component > properly. Will this work? Where should I get started? > > Cheers, > Yogesh
