anchor.diff:  
   Please note that the Spring support in Quarkus does not start a Spring Application Context nor are any Spring infrastructure classes run.
   Spring classes and annotations are only used for reading metadata and / or are used as user code method return types or parameter types.
  -What that means for end users, is that adding arbitrary Spring to the classpath will not be used at all. Moreover Spring infrastructure
  -things like `org.springframework.beans.factory.config.BeanPostProcessor` will not be run.
  -
  +What that means for end users, is that adding arbitrary Spring libraries to the classpath will not be taken into account. Moreover Spring infrastructure
  +things like `org.springframework.beans.factory.config.BeanPostProcessor` will not be executed.
  +
  
positive.code: 
  === Controller method return types
  
  In addition to the method parameters that can be annotated with the appropriate Spring Web annotation from the previous table,
  `javax.servlet.http.HttpServletRequest` and `javax.servlet.http.HttpServletResponse` are also supported.
  
  
  
negative.code: }
  ----
  
  The Quarkus Maven plugin automatically generated a `src/main/java/org/acme/spring/web/GreetingController.java` file.
  However since we are going to be using Spring Web annotations to define our REST endpoint (instead of the JAX-RS ones used by default), we need to change
  the `GreetingController` to have the following content:
  
  