title: Best Practice for loading 3rd party JARs in JBoss AS7 standalone deployment?
body: <p>What is the best practice for loading 3rd party JARs in JBoss-as-7.0.x standalone deployment? </p>
  
  <p>I have tried:</p>
  
  <ol>
  <li>deploying each JAR as an independent module with it's own module.xml desriptor; </li>
  <li>deploying the JARs in the WEB-INF/lib directory of a WAR;</li>
  <li>and the foo.ear/lib directory for any JARs shared across multiple WARs. </li>
  </ol>
  
  <p>The obvious advantage to approach 1. above is the reduced memory footprint at deploy time over apprach 2. and approach 3. However it seems to be pretty arduous to maintain as each dependency that a JAR has needs to be explicitly defined in the module.xml which doesn't seem very maintainable with large numbers of 3rd party libraries.</p>