anchor.diff:  set on the Camel exchange and the route execution will continue as
   usual. This can be useful for integrating the existing JAX-RS implementations into Camel routes and
   for post-processing JAX-RS Responses in custom processors.
  +
  +[source,java]
  +----
  +@Path("/customerservice/")
  +public interface CustomerServiceResource {
  +
  +    @GET
  +    @Path("/customers/{id}/")
  +    Customer getCustomer(@PathParam("id") String id);
  +
  +    @PUT
  +    @Path("/customers/")
  +    Response updateCustomer(Customer customer);
  +
  +    @Path("/{id}")
  +    @PUT()
  +    @Consumes({ "application/xml", "text/plain",
  +                    "application/json" })
  +    @Produces({ "application/xml", "text/plain",
  +                    "application/json" })
  +    Object invoke(@PathParam("id") String id,
  +                    String payload);
  +}
  +----
   
   ### How to invoke the REST service through camel-cxfrs producer
   
  
positive.code: method request to a right processor or endpoint.
  
  Here is an example of a CXFRS route...
  
  And the corresponding resource class used to configure the endpoint...
  
  
negative.code: export the resources classes as a REST service. And we leverage the
  http://cxf.apache.org/docs/invokers.html[CXF Invoker
  API] to turn a REST request into a normal Java object method
  invocation.
   Unlike the <<restlet-component,Camel Restlet>> component, you don't need
  to specify the URI template within your endpoint, CXF takes care of the
  REST request URI to resource class method mapping according to the
  