anchor.diff:  &lt;/beans&gt;
   ----
   The application should not have a servlet extending [classname]#VaadinServlet#,
  -as Vaadin servlet has its own [classname]#VaadinSpringServlet# that is deployed
  +as Vaadin servlet has its own [classname]#SpringVaadinServlet# that is deployed
   automatically. If you need multiple servlets or need to customize the Vaadin
   Spring servlet, see <<advanced.spring.deployment>>.
   
  
positive.code: When customizing the Vaadin servlet, as outlined in
  <<dummy/../../../framework/application/application-lifecycle#application.lifecycle.servlet-service,"Vaadin
  Servlet, Portlet, and Service">>, you simply need to extend
  [classname]#com.vaadin.spring.internal.VaadinSpringServlet# instead of
  [classname]#com.vaadin.servlet.VaadinServlet#.
  
  [subs="normal"]
  
negative.code:     &lt;/dependency&gt;
  ----
  
  For Vaadin Spring Boot, depending on [literal]#++vaadin-spring-boot-starter++# will
  include all the required Vaadin dependencies.
  
  
  [[advanced.spring.preparing]]
  == Preparing Application for Spring
  
  A Vaadin application that uses Spring must have a file named
  [filename]#applicationContext.xml# in the [filename]#WEB-INF# directory.
  Using Spring Initializr automatically generates a suitable file, but if
  you configure Vaadin Spring manually, you can follow the model below.
  
  [subs="verbatim,replacements,quotes"]
  ----
  