<html>
<head>
<meta content="text/html; charset=windows-1252"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
Hi James,<br>
<br>
I am using it. Currently as workaround to the [1], I am usually
connecting to already running server instead of starting it with
arquillian because of that issue.<br>
<br>
I have also encountered that arquillian deployments management
doesn't work when the server is started by arquillian, thereby I am
managing deployments outside of arquillian and handling deployments
via WildFly management API.<br>
<br>
Radim<br>
<br>
[1] <a class="moz-txt-link-freetext" href="https://issues.jboss.org/browse/ARQ-1971">https://issues.jboss.org/browse/ARQ-1971</a><br>
<br>
<div class="moz-cite-prefix">On 09/17/2015 02:01 AM, James Perkins
wrote:<br>
</div>
<blockquote
cite="mid:CADGwLpih5jrpAA1jbZw8KJx8G4YisjZqkXdXrzMBApqjdH0f=g@mail.gmail.com"
type="cite">
<div dir="ltr">
<div>Does anyone use wildfly-arquillian with domain servers? If
so does it work?</div>
<div><br>
</div>
<div>I was processing pull request for the wildfly-arquillian
[1] project. During the process I found a pull requestion for
an issue with using arquillian on domain servers [2]. This led
me to look at the to look at the domain adapters. Looking
through the code it looks quite out of date and potentially
wrong in some places. I started updating and noticed that the
tests were ignored. I re-enabled them and realized the adapter
doesn't seem to work at all.</div>
<div><br>
</div>
<div>The main issue seems to be that deployments are not rolled
out to the servers. If I change the deployment plan to
rollback on error it has an error message that states
"WFLYDC0022: Operation failed or was rolled back on all
servers.". No other reason. I can start the same server used
in domain mode and execute CLI commands or use an operation
identical to the one created by the deployment plan and all
seems to work fine. I assume this issue is unique to
arquillian.</div>
<div><br>
</div>
<div>I'm at the point where I don't want to invest anymore time
if no one is using arquillian for domain servers. If anyone is
using it and has an example application that you could share
that would be helpful :)</div>
<div><br>
</div>
<div>I propose if no one is using it, we scrap it.</div>
<div><br>
</div>
<div>If people *are* using it I propose we do a redesign it a
bit. There's mainly some things exposed I don't think should
be exposed. I could keep compatibility too fairly easily. It
would be about the same amount of work either way I think.</div>
<div><br>
</div>
<div>If anyone else has other ideas I'm open to that as well.</div>
<div><br>
</div>
<div><br>
</div>
<div>[1]: <a moz-do-not-send="true"
href="https://github.com/wildfly/wildfly-arquillian">https://github.com/wildfly/wildfly-arquillian</a></div>
<div>[2]: <a moz-do-not-send="true"
href="https://issues.jboss.org/browse/ARQ-1971">https://issues.jboss.org/browse/ARQ-1971</a></div>
<div><br>
</div>
<div>--</div>
<div>James R. Perkins</div>
<div>JBoss by Red Hat</div>
</div>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
wildfly-dev mailing list
<a class="moz-txt-link-abbreviated" href="mailto:wildfly-dev@lists.jboss.org">wildfly-dev@lists.jboss.org</a>
<a class="moz-txt-link-freetext" href="https://lists.jboss.org/mailman/listinfo/wildfly-dev">https://lists.jboss.org/mailman/listinfo/wildfly-dev</a></pre>
</blockquote>
<br>
</body>
</html>