title: EJB testing strategies?
body: <p>I'm working on a Java EE 6 application. When I started out, I was writing tests for my EJB classes by manually instantiating the EJB, then manually adding the members that normally get provided by dependency injection. As the application gets more complicated, I find that this approach just doesn't cut it. So I'd like to be able to start my own EJB container in the test framework, so it can manage my beans. What's the best way to approach this? I've heard of <code>javax.ejb.embeddable.EJBContainer</code>, are there other options?</p>
  
  <p>(I'm using Glassfish 3, and building with Maven, if that makes any difference.)</p>