Take a look at the Servlet and ServletListener components as well as the Restlet component. You can actually use Camel to serve parts of a web application easily
*Robert Simmons Jr. MSc. - Lead Java Architect @ EA* *Author of: Hardcore Java (2003) and Maintainable Java (2012)* *LinkedIn: **http://www.linkedin.com/pub/robert-simmons/40/852/a39* On Mon, Sep 30, 2013 at 12:55 AM, rudolf61 <rudolf.de.gr...@ziggo.nl> wrote: > I was wondering if it is possible to integrate Apache Camel into a http > request/reply cycle. > > Using Apache Camel as a proxy is an option, but is it possible to sit > between the web client and the servlet, like this happens with the Servlet > Filter. > > One possible solution would be to get my hand on the RequestDispatcher and > include the final servlet. has anyone ever done this? > > The reason I'm looking into this, is because I would like to setup a > publish > pipeline similar to Apache Cocoon. > As far as I can tell Apache Camel could do the same and even more > (supporting the major EIP's). > > It's important that I do have the same capabilities as I would have with > Apache Cocoon particularly access to the request (which includes session > support, which is shared by the servlet that is accessed. This is a major > difference compared to a proxy) and response. > > I would very much like to hear your ideas and thoughts. > > > > -- > View this message in context: > http://camel.465427.n5.nabble.com/Integrating-Apache-Camel-into-http-request-reply-cycle-tp5740451.html > Sent from the Camel - Users mailing list archive at Nabble.com. >
