@ArquillianResource on AS 7

[htfv]

Hello again!

I have a simple test method:

@Test

public void testMessageTag(@ArquillianResource URL baseUrl) throws Exception

{

    String result = Utils.readToString(new URL(baseUrl, "/TestMessageTag.jspx"));

}

This is my first attempt to use @ArquillianResource. I expected to receive domething like http://127.0.0.1:8080/886410e0-f846-45b4-9a70-b1fe8f9f7c0c in baseUrl, but I receive only http://127.0.0.1:8080. Is this a bug or do I do something wrong?

I use jboss-as-arquillian-container-remote version 7.1.0.Alpha1-SNAPSHOT (built from sources).

[aslak]

Are you sure baseUrl points to only 127.0.0.1:8080 ?

When you use new URL(baseUrl, "/") it will go back to the ROOT of that baseURL which is 127.0.0.1:8080 (since your 'child-resource' starts with /)

You might want: new URL(baseUrl, "TestMessageTag.jspx") to make the new URL relative to baseUrl

[htfv]

Yes, I'm sure, I checked the value of the baseUrl variable. "/TestMessageTag.jspx" is a mistake (I noticed it after I have posted the message), but it's NOT the cause. new URL(baseUrl, "TestMessageTag.jspx") gives me "http://127.0.0.1:8080/TestMessageTag.jspx".

[aslak]

Can you post the @Deployment ?

[htfv]

Attached test project; use arquillian-jbossas-remote-7 profile. On my side it prints http://127.0.0.1:8080 and fails.

[aslak]

This is working for me in current master jbossas, https://github.com/jbossas/jboss-as

?

[htfv]

Did you use AS built from sources? I use AS 7.0.0.Final; I only built container from sources. Can this be a problem?

[aslak]

Hmm.. I had everything build and ran against current source tree yes.

I'm not aware of changes in AS it self that should support this feature, but it might behave differently.. so yea, could be the problem.

There has been commited multiple fixes to the arq containers lately, your checkout/build might have been before them ?

[htfv]

Works with Arquillian 1.0.0.CR4, JBoss AS 7.0.1.Final.