-
1. Re: ArquillianServletRunner not found. Could not determine ContextRoot from ProtocolMetadata using wildfly-arquillian-container-domain-remote
bmajsak Oct 23, 2014 3:39 AM (in response to abertschi)1 of 1 people found this helpfulAndrin Bertschi wrote:
Using wildfly-arquillian-container-domain-remote in version 8.1.0.Final to deploy to a jboss-as-7.1.1.Final
Hi Andrin,
I think this is the very problem. I don't think you can use WF adapter to deploy on 7.1.1. Why not using jbossas-7.1.1 adapter instead? Is it because of the domain mode (I guess this came to eap 6.x only @aslak)?
-
2. Re: ArquillianServletRunner not found. Could not determine ContextRoot from ProtocolMetadata using wildfly-arquillian-container-domain-remote
abertschi Oct 23, 2014 4:53 AM (in response to bmajsak)Hi Bartosz,
Thanks for the hint. The reason why I stuck to wildfly-arquillian-container-domain-remote was that I got problems using jboss-as-arquillian-container-domain-remote:
Using the latest version of jboss-as-arquillian-container-domain-remote (7.2.0.Final), arquillian running in my maven based tests started deploying the artifact, but neither on my server log nor in the maven console output I got further output.
So the deployment process got stuck at that time.
-------------------------------------------------------
T E S T S
-------------------------------------------------------
Running com.axa.ch.partneraccess.it.presservice.DomainTest
0 [main] INFO org.xnio - XNIO version 3.2.2.Final
79 [main] INFO org.xnio.nio - XNIO NIO Implementation Version 3.2.2.Final
110 [main] INFO org.jboss.remoting - JBoss Remoting version 3.2.14.GA
Considering your hint, I tried older versions of jboss-as-arquillian-container-domain-remote. In short, the deployment using older versions such as 7.1.3.Final and 7.1.2.Final both works. Great!
To sum up, these dependencies enable the tests to run in a domain-mode environment of jboss-as-7.1.1.Final:
<dependency>
<groupId>org.jboss.as</groupId>
<artifactId>jboss-as-arquillian-container-domain-remote</artifactId>
<version>7.1.2.Final</version><scope>test</scope>
</dependency><dependency>
<groupId>org.jboss.arquillian.protocol</groupId>
<artifactId>arquillian-protocol-servlet</artifactId>
<scope>test</scope>
<version>1.1.2.Final</version>
</dependency>
<dependency>
<groupId>org.jboss.arquillian.junit</groupId>
<artifactId>arquillian-junit-container</artifactId>
<scope>test</scope>
<version>1.1.2.Final</version>
</dependency> -
3. Re: ArquillianServletRunner not found. Could not determine ContextRoot from ProtocolMetadata using wildfly-arquillian-container-domain-remote
bmajsak Oct 23, 2014 4:56 AM (in response to abertschi)Can you try to update Arquillian Core to 1.1.5.Final?
-
4. Re: ArquillianServletRunner not found. Could not determine ContextRoot from ProtocolMetadata using wildfly-arquillian-container-domain-remote
abertschi Oct 23, 2014 6:15 AM (in response to bmajsak)Arquillian Core:1.1.5.Final with jboss-as-arquillian-container-domain-remote:7.2.0.Final shows the same results, the deployment gets stuck showing just:
-------------------------------------------------------
T E S T S
-------------------------------------------------------
Running com.axa.ch.partneraccess.it.presservice.origin.DomainTest0 [main] INFO org.xnio - XNIO Version 3.0.7.GA
0 [main] INFO org.xnio.nio - XNIO NIO Implementation Version 3.0.7.GA
32 [main] INFO org.jboss.remoting - JBoss Remoting version 3.2.12.GA
However, 7.1.3.Final | 7.1.2.Final with Arquillian Core:1.1.5.Final works fine. -
5. Re: ArquillianServletRunner not found. Could not determine ContextRoot from ProtocolMetadata using wildfly-arquillian-container-domain-remote
bmajsak Oct 23, 2014 7:14 AM (in response to abertschi)There might be something with outdated jboss-remoting library. I can look it up if you need that.
-
6. Re: ArquillianServletRunner not found. Could not determine ContextRoot from ProtocolMetadata using wildfly-arquillian-container-domain-remote
abertschi Oct 23, 2014 7:31 AM (in response to bmajsak)In my case, I'll be fine with Arq CORE 1.1.2.Final and jboss-as-arquillian-container-domain-remote: 7.1.3.Final for the moment.
Nevertheless, the latest version of jboss-as-arquillian-container-domain-remote doesn't seem to work with Arquillian Core:1.1.5.Final, so we might create an issue for that?