<html>
<head>
<meta content="text/html; charset=windows-1252"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<p><br>
</p>
<br>
<div class="moz-cite-prefix">On 06/01/2016 05:20 PM, Alessio Soldano
wrote:<br>
</div>
<blockquote cite="mid:574F5196.4090907@redhat.com" type="cite">
<meta content="text/html; charset=windows-1252"
http-equiv="Content-Type">
<div class="moz-cite-prefix">Il 01/06/2016 20:16, Ron Sigal ha
scritto:<br>
</div>
<blockquote
cite="mid:c26971bd-dcb0-8aeb-4f75-1a4702ce7595@redhat.com"
type="cite">
<meta content="text/html; charset=windows-1252"
http-equiv="Content-Type">
<br>
<br>
<blockquote
cite="mid:1662693582.1399492.1464789426729.JavaMail.zimbra@redhat.com"
type="cite">
<pre wrap="">
ARQ + Undertow know each other: <a moz-do-not-send="true" class="moz-txt-link-freetext" href="http://arquillian.org/modules/undertow-embedded-container-adapter/">http://arquillian.org/modules/undertow-embedded-container-adapter/</a>
</pre>
</blockquote>
<br>
My first inclination, like Weinan's, was to think that running
everything in Wildfly was pretty heavy, but if we just start
Wildfly once, that's not so bad.</blockquote>
Right, that's what I meant saying that it depends on how you
implement the solution. In practice, we might end up needing more
than just a single WFLY instance (perhaps because we need
different container configurations for different types of tests),
but the number of instances should really be limited (let's say
less than 5?).<br>
<br>
<blockquote
cite="mid:c26971bd-dcb0-8aeb-4f75-1a4702ce7595@redhat.com"
type="cite"> After all, that's what the TCK does, as well as the
new qe TS.</blockquote>
And the JBossWS testsuite ;)<br>
<br>
<blockquote
cite="mid:c26971bd-dcb0-8aeb-4f75-1a4702ce7595@redhat.com"
type="cite"> One problem I still have is that, when I'm working
on a problem, I MUCH prefer running tests in an embedded
container like tjws or Undertow.</blockquote>
Not sure what the preference is based on, but if that's because
you don't want to manually start the container, etc... Arquillian
does that for you.<br>
</blockquote>
<br>
I just like the instantaneous startup. For example, I just ran a
test in RESTEASY-TEST-WF8, and it took 2.7 seconds to start up
Wildfly and another 2.7 seconds to create and deploy the WAR. Better
than AS 5 ;-) but still a little annoying.<br>
<br>
<blockquote cite="mid:574F5196.4090907@redhat.com" type="cite"> <br>
<blockquote
cite="mid:c26971bd-dcb0-8aeb-4f75-1a4702ce7595@redhat.com"
type="cite"> I guess I could just write a standalone test and
then turn it into an arquillian test when I'm done. But if
Arquillian works with Undertow, which I didn't know, that might
be the best of all worlds.</blockquote>
I've never tried this, but afaiu yes it works with Undertow.<br>
<br>
<blockquote
cite="mid:c26971bd-dcb0-8aeb-4f75-1a4702ce7595@redhat.com"
type="cite"> I'm a little worried though about the time it takes
Arquillian to create a WAR, which isn't insignificant ...<br>
</blockquote>
It's not that bad after all; btw, once you have all tests as
arquillian ones and you ensure they do not make assumptions on the
server being there just for each of them (which is also good), you
can most likely make the testsuite execution concurrent and run
multiple tests at the same time.<br>
<br>
Cheers<br>
Alessio<br>
<br>
<pre class="moz-signature" cols="72">--
Alessio Soldano
Web Service Lead, JBoss</pre>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
resteasy-dev mailing list
<a class="moz-txt-link-abbreviated" href="mailto:resteasy-dev@lists.jboss.org">resteasy-dev@lists.jboss.org</a>
<a class="moz-txt-link-freetext" href="https://lists.jboss.org/mailman/listinfo/resteasy-dev">https://lists.jboss.org/mailman/listinfo/resteasy-dev</a>
</pre>
</blockquote>
<br>
<pre class="moz-signature" cols="72">--
My company's smarter than your company (unless you work for Red Hat)</pre>
</body>
</html>