Issue

The camel-servlet component can be used to integrate a Camel route that consumes HTTP requests, with the Fuse built-in HTTP infrastructure. So requests can be made on the same HTTP port that serves, for example, the default CXF servlet and the Hawtio console; there is no need to create a separate HTTP listener. camel-jetty cannot be used for this, because it will always create a new listening port, and the operating system won't allow two threads to bind the same listening port.

Another advantage of camel-servlet over camel-jetty (in a Fabric8 environment) is that servlet endpoints are published in the registry, and can be auto-discovered by the Fabric8 HTTP gateway.

Most of Red Hat's documentation that refers to camel-servlet shows its usage in a Spring-based application, and such examples cannot be used directly with Blueprint.