Hey Tom,

I expect that you want to run HttpUnit as client, not inside the server, right? In such case, you can "force" only one method to run as client and inject URL there:

@Test
@RunAsClient
public void myHttpUnitTest(@ArquillianResource URL contextPath) {
// context path is for instance http://localhost:8080/testApp here, based on you container and deployment
}

If that's not the case, workaround is to use following trick

static URL myUrlField;

@InSequence(1)
@Test
@RunAsClient
public void getURL(@ArquillianResource URL url) {
myUrlField = url;
}

@InSequence(2)
@Test
public void myTest() {
// this test is running inside of the server, but it has access to myUrlField, which contains url of the deployment, because the first test set static field
}

Hope that helps,

Karel

Hmm, I wasn't aware of that class loader might play role here, good to know. Actually, I think it is a bug, Arquillian should transfer state of static fields no matter of class loader instance, because having different classloaders is somehow expected - tests are running in different JVMs. I'm wondering why I've never hit such issue.

Another idea is to have a look at Arquillian Warp extension - arquillian-extension-warp/README.md at master · arquillian/arquillian-extension-warp · GitHub. It supports JSF, JAXRS, SpringMVC only but you might be able to rewrite the test by exposing REST endpoint or maybe you could alter Warp to fit your needs.

Karel

Hi Tom,

other solution that pops up in mind is to use ServerSetupTask to propagate system property from client to server. It could help you to propagate at least base URL of the application server that is configured in arquillian.xml. This is used in AS7/WF testsuite as well.

Some details here:

[ARQ-647] Implement a convenient way to pass system properties to managed container's JVM. - JBoss Issue Tracker

wildfly/testsuite/shared/src/main/java/org/jboss/as/test/integration/security/common/AbstractSystemPropertiesServerSetup…

HTH,

Karel