arquillian extensions often use auto-enrichement (that's not the right vocabulary but i find it more explicit ;). It means it adds libs to your app autiomatically. It only works for war and ear (sometimes).
*Romain Manni-Bucau* *Twitter: @rmannibucau <https://twitter.com/rmannibucau>* *Blog: **http://rmannibucau.wordpress.com/*<http://rmannibucau.wordpress.com/> *LinkedIn: **http://fr.linkedin.com/in/rmannibucau* *Github: https://github.com/rmannibucau* 2013/8/20 Christian Schlichtherle <[email protected]> > Turned out I needed to have > > final WebArchive archive = ShrinkWrap.create(WebArchive.class) > .addClass(Foo.class); > > instead of > > > final JavaArchive archive = ShrinkWrap.create(JavaArchive.class) > > .addClass(Foo.class); > > However, that doesn't make sense to me. The module I am testing is > packaged as an EJB JAR and will be contained in an EAR, not a WAR. > Furthermore, the old code worked with OpenEJB Embedded. To me, the whole > point of using Arquillian is to make the container a build time choice, so > I should not have to change my code. > > Regards, > Christian Schlichtherle >
