title: enable/disable servlets mapped by @WebServlet annotation in servlet 3.0
body: <p>I'm an admin used to the old-school way of defining servlets/mappings, i.e. in web.xml.</p>
  
  <p>Servlet 3.0 is great, and the @WebServlet annotation sure is nifty, if you're a developer.</p>
  
  <p>The problem is, as an admin, what if I'm managing a webapp that contains lots of different utility servlets (servlets.jar) defined by annotations, and not all of them are appropriate for each deployment?  In other words, I want to either whitelist the URI mappings that are appropriate for a given deployment, or blacklist the ones that aren't.  </p>
  
  <p>Without reverting to an earlier servlet spec, and ideally (though this is not off the table) without asking my developers to change the way they're doing things.</p>
  
  <p>Running JDK 1.7 Tomcat 7 if that matters.</p>