Arquillian with WAS Remote - CDI Beans not getting injected

[creinke]

I'm trying to make the standard Arquillian Greeting example work with the WAS 8 Remote adapter.  I'm doing all my testing under RSA 9 and I'm not using Maven.  I'm pretty sure I've figured out all the jars that are required and I was able to create the Greeting test, deploy it, and invoke the test from RSA's JUnit runner.  The WAS 8 adapter requires a Web or Enterprise archive so that is how I packaged it up. 

The test fires and works except that the Greeting Bean does not get injected; that results in a null pointer being thrown.  Clearly I'm missing something but can't determine what.  I've attached the WAR that Shrinkwrap creates to this post, along with other relevant information,  Would appreciate it if anyone can see what I've failed to do.

Thanks! 

[gpoul]

Hi Kurt,

have you tested this and made sure that it works without Arquillian and that the injection problem you're seeing is not a general CDI problem?

Please also see whether you can see any difference in what you're testing and what I'm using for testing the container implementation; you can find the code at arquillian-container-was/was-remote-8/src/test/java/org/jboss/arquillian/container/was/remote_8 at master · arquillian/a…

Gerhard

[creinke]

Poul,

Thanks for your suggestion!  Yes, I was able to prove that it isn't a CDI problem; it's the Arquillian setup in RSA that is problematic.  We don't use the Eclipse Maven plugin and so we need to get all the jars setup and settings correct manually.  I think we've finally been able to set things up correctly in that regard and we can now debug into the problem all the way through from the JUnit JVM to execution in the ArquillianServletRunner. We thought we finally had it, but the Arquillian runner now seems to be in an infinite loop on the originalStatement.evaluate() statement.  We're using ARQ 1.1.5 Final now but the binaries and the sources for the Arquillian runner seem to be off in the debugger so we're going to rebuild 1.1.6 Snapshot from the repository and try that next.  When we get an answer, we'll update our findings here in case anyone is interested.  Thanks again for your response!

Kurt