title: Two servlets in the same WAR vs. two seperate WARs -- pros and cons?
body: <p>I've recently run into a snag that will probably keep me from being able to follow through with plans to package a single WAR with two servlets.  The work-around is to create an extra Maven WAR module.  </p>
  
  <p>Besides the extra hassle for me and for customers, is there any other real drawback?  are there advantages?</p>
  
  <p>@Edit</p>
  
  <p>The "snag" I have run into is that I want two different authentication mechanisms for each servlet.  One to use Spring Security and the other either a different authentication provider or possibly Basic authentication.  See here:</p>
  
  <p><a href="https://stackoverflow.com/questions/3766004/is-it-possible-to-use-a-different-spring-security-authenticationprovider-in-diffe">Is it possible to use a different Spring Security AuthenticationProvider in different servlets, same WAR?</a></p>