title: How to disable Servlet 3.0 scanning and auto loading of components
body: <p>We have an application which keeps loading instances of ServletContainerInitializer from our 3rd party libs.</p>
  
  <p>One instance is JerseyServletContainerInitializer and the other is SpringServletContainerInitializer.  These classes from Jersey and Spring seem to "take over" our servlet context messing with our mappings and filters and such.</p>
  
  <p>We really need to explicitly configure our servlet container's web.xml and this auto scanning is driving us insane.  By simply pulling in a dependency in our pom.xml our runtime ServletContext configurations such as Servlets/Filters/ContextListeners are mutated because the servlet container finds these libraries on the classpath.</p>
  
  <p>Is there a way to use Servlet 3 but disable its annoying auto classpath scanning "feature"?</p>