Hi Scott, Hi Scott,
You have not misunderstood a thing. This is exactly the technology for your use case. I would start with the Enterprise Integration Patterns found here: http://camel.apache.org/enterprise-integration-patterns.html. Managing a workflow with aggregation and transformation is pretty boilerplate and the EIP page should get you started. Good luck! Best Regards, Scott ES On Tue, Oct 2, 2012 at 4:06 PM, scottj <scott.james...@outlook.com> wrote: > hello list, > as a student's project we've received the task to come up with an > architecture for a flight search. Like e.g. hipmunk.com. Our idea was to > let > camel handle the integration part, but we are not sure if this would be a > feasible solution. > > idea: camel receives X requests that are to be dispatched to X different > online airline services, e.g. Delta, Air France. We assume the airline > services require different formats; some may require an http-request, some > may require json/xml etc. Camel dispatches these requests and receives the > answers. Upon receiving the answers, answers are transformed to a common > format which is to be stored in a database. A unique id should identify the > initial X requests with the answers received (assume the airline service > feedbacks this in the response) > > so the short question is: is Camel the right technology for this? Or have > we > completely misunderstood what Camel can do? > > any suggestion is highly appreciated! > > > > -- > View this message in context: > http://camel.465427.n5.nabble.com/is-camel-the-right-choice-tp5720396.html > Sent from the Camel - Users mailing list archive at Nabble.com. > -- -- Scott England-Sullivan Apache Camel Committer Principal Consultant / Sr. Architect | Red Hat, Inc. FuseSource is now part of Red Hat Web: fusesource.com <http://www.fusesource.com> | redhat.com<http://www.redhat.com> Blog: sully6768.blogspot.com Twitter: sully6768
