Hi,
the short answer is: Yes.
A bit more elaborate, I think that is a very common use case and kind of
screams for
something like Camel - if not Camel itself ;)
What you would typically do is:
1) Implement a route that calls out to your core business logic. This
route id your
service provisioning route. This route should be exposed using an
"internal" endpoint.
I normally choose seda or jms endpoints for that.
2) Once you have done that you can use the route from other routes which
I would call
the protocol routes. These would use the service implementation
route and just perform
any protocol specific data mapping if required.
Best regards
Andreas
On 10/10/2013 07:23 PM, madhairsilence wrote:
Am having a service running in a Apache tomcat server. Am currently exposing
the service as REST Service.
Now, we have decided to make it available for different types of clients.
Such that, the same service can be used as
1. Calling as REST Service
2. Pushing in a Queue
3. Call as Web Service
4. File/Multipart upload
and some other way mode of transport.
Can I have one single application, controlled by Camel , which can
understand all types of request and Route accordingly?
Can we achieve this!!!
--
View this message in context:
http://camel.465427.n5.nabble.com/Camel-with-Multiple-types-of-Endpoints-tp5741306.html
Sent from the Camel - Users mailing list archive at Nabble.com.
