We have been trying to setup integration testing for our maven seam jboss 4.2.3 project. I have spent way too much time trying to setup SeamTest based integration testing but ended up where I started. I stubled upon Arquillian and based upon the tutorial it looks like a very cool tool. While I am all for learning the tool, I interested in knowing if ariquillian works with jboss 4.2.3 (I ask this question despite of the fact that Arquiilan's tutorial spectifically states it only supports jboss 5.1 and 6.0 ). Has anybody tried that combination , if so what are your experiences and is there a place I can look for start up help.

Although I have done unit testing before, this is the first time I am setting up a full fledged integration testing. So, I urge anybody answering the question to explain stuff as if you were to an illiterate.

"Due to problems booting the JBoss Micro Container with Maven, we have choosen to use the Apache OpenEJB embedded container to run Seam (and EJB-3.x) integration tests. The seam-refimpl project template comes preconfigured with the Apache OpenEJB embedded container for running tests"

Thanks for the reply Sten. I did find your post on this issue, but wanted to stick to jboss for various reasons. I am yet to write my first integration test but progressing well with the help of the os community.

We have been trying to setup integration testing for our maven seam jboss 4.2.3 project. I have spent way too much time trying to setup SeamTest based integration testing but ended up where I started.

That's exactly why we are working on Arquillian. Integration testing Java EE has been a pain. While SeamTest had a compelling approach, it introduced it's own complexity that ultimately led to pain and failure. With Arquillian, we are committed to making it easy, elegant and powerful. Please hold us to those goals

With the OSS community at your side, it's truly amazing the types of challenges you can overcome. We like hearing that

An Arquillian container for JBoss AS 4.2.3 is certainly possible. After having done two container implementations just this past weekend, I can tell you from first-hand experience that it's not particularly difficult (just requires patience). It's really just a matter of figuring out how you are going to deploy and undeploy an application. JBoss AS has long supported remote deployments, so with a little digging and persistence, you should be able to get it working (hint, search for Deployment Manager or Web Manager).

If all else fails, you can try using the JSR 88 container support I attached to ARQ-156.

(Note: this is not a new post. I reposted because the reply somehow got associated with the wrong author).

I have a DeployableContainer implementation for JBoss AS 4.2 Remote that I did during JBoss World locally(not committed yet).

It looks up the RMIAdaptor via JNDI to invoke the MainDeployer. It works for deployment, but the problem is with EE 4 you need all the Descriptors like web.xml, application.xml etc. We have poor support for dynamic descriptor atm so the deployment fails..

I was thinking of revisiting this when we get the Descriptors project up and running..

So how many watchers would this JIRA ticket need to attract you attention and schedule this within one of the next releases?

Good question..

I'll make a ARQ-238 branch in my arq repo tomorrow and push the container implementation I have so far. Using Run(AS_CLIENT) should work, since Arq does not need to touch the deployment in that case. That means any form of Remote testing is doable now.

I'll make a ARQ-238 branch in my arq repo tomorrow and push the container implementation I have so far. Using Run(AS_CLIENT) should work, since Arq does not need to touch the deployment in that case. That means any form of Remote testing is doable now.