anchor.diff:  can access the `camel-servlet` endpoint through the servlet publish
   address: `("http://localhost:8080/camel/services") + RELATIVE_PATH("/hello")`.
   
  -#### Sample when using Spring 3.x
  -
  -See Servlet Tomcat Example
  -
  -#### Sample when using Spring 2.x
  +==== Sample when using Spring 3.x
  +
  +See link:servlet-tomcat-example.html[Servlet Tomcat Example].
  +
  +==== Sample when using Spring 2.x
   
   When using the Servlet component in a Camel/Spring application it's
   often required to load the Spring ApplicationContext _after_ the Servlet
  
positive.code:     <groupId>org.apache.camel</groupId>
      <artifactId>camel-servlet</artifactId>
      <version>x.x.x</version>
      <\!-\- use the same version as your Camel core version \-->
  </dependency>
  ---------------------------------------------------------------
  
  
  INFO: *Stream*. 
  Servlet is stream based, which means the input it receives is submitted
  to Camel as a stream. That means you will only be able to read the
  content of the stream *once*. If you find a situation where the message
  
negative.code: // spring-boot-auto-configure options: END
  
  
  === Message Headers
  
  Camel will apply the same Message Headers as the <<http-component,HTTP>>
  component.
  
  Camel will also populate *all* `request.parameter` and
  `request.headers`. For example, if a client request has the URL,
  http://myserver/myserver?orderid=123, the exchange will contain a
  header named `orderid` with the value 123.
  
  === Usage
  
  You can consume only `from` endpoints generated by the Servlet component.
  Therefore, it should be used only as input into your Camel routes. To
  issue HTTP requests against other HTTP endpoints, use the
  <<http-component,HTTP Component>>.
  
  === Putting Camel JARs in the app server boot classpath
  
  If you put the Camel JARs such as `camel-core`, `camel-servlet`, etc. in
  the boot classpath of your application server (eg usually in its lib
  