Arquillian: Adding beans.xml causes "ArquillianServletRunner not found"

Question

I am using Arquillian[1] for testing my J2EE-App in an embedded glassfish environment inside Eclipse[2]-IDE. ``` package test.java; import org.jboss.arquillian.container.test.api.Deployment; import org.jboss.arquillian.junit.Arquillian; import org.jboss.shrinkwrap.api.ArchivePaths; import org.jboss.shrinkwrap.api.ShrinkWrap; import org.jboss.shrinkwrap.api.asset.EmptyAsset; import org.jboss.shrinkwrap.api.spec.WebArchive; import org.junit.Assert; import org.junit.Test; import org.junit.runner.RunWith; @RunWith(Arquillian.class) public class ArquillianTest { @Deployment public static WebArchive createDeployment() { return ShrinkWrap.create(WebArchive.class).addAsWebInfResource(EmptyAsset.INSTANCE, ArchivePaths.create("beans.xml")); } @Test public void test() { Assert.assertNull(null); } } ``` The test executes fine until I add the showed instruction ".addAsWebInfResource(...)". When doing this, following exception is thrown: ``` java.lang.IllegalArgumentException: ArquillianServletRunn…

Accepted Answer

I've taken a look at your POM and your test. The issue appears to be related to GLASSFISH-16964, going by the following log entries: ``` SLF4J: The requested version 1.5.10 by your slf4j binding is not compatible with [1.6] SLF4J: See http://www.slf4j.org/codes.html#version_mismatch for further details. Dec 07, 2012 2:09:59 PM org.glassfish.api.ActionReport failure SEVERE: Exception while loading the app Dec 07, 2012 2:09:59 PM org.glassfish.deployment.admin.DeployCommand execute SEVERE: Exception while loading the app : org.slf4j.spi.LocationAwareLogger.log(Lorg/slf4j/Marker;Ljava/lang/String;ILjava/lang/String;Ljava/lang/Throwable;)V ``` You have a few dependencies in your project that pull in v1.6.1 of `slf4j-api`. That appears to conflict with what embedded GlassFish requires - I believe it is `1.5.10` going by the logs of embedded GlassFish. To resolve this particular issue, downgrade to the version that keeps GlassFish happy. I added the lower version as a managed dependency. ``` .... org.slf4j slf4j-api 1.5.10 test ``` Of course, this might have an impact on the other libraries that depend on the newer version of slf4-api, so you'll have to watch out for other issues. The best way to resolve this would be to use the remote or managed GlassFish Arquillian adapter.

Arquillian: Adding beans.xml causes "ArquillianServletRunner not found"

Solution

Problem