<p>+1 on the standalone CDI bootstap. I think that was the real productivity boost for the CDI TCK effort.</p>
<p>The remote containers really aren't bad because it just stays running in the background and the only delay is the app deployment.</p>
<p>Aslak, does Arquillian start the remote server if it isn't already started like JBoss Test Harness did? That might be a really nice feature to get back in. I guess we can start w/ a JIRA for it. I'm thinking an option to start and another option to keep running or shutdown after suite (I'm on the road today so I can't add a JIRA.)</p>
<p>- Dan Allen</p>
<p>Sent from my Android-powered phone:<br>
An open platform for carriers, consumers<br>
and developers.</p>
<p><blockquote type="cite">On Dec 27, 2009 12:54 PM, "Aslak Knutsen" <<a href="mailto:aslak@conduct.no">aslak@conduct.no</a>> wrote:<br><br>It's not 100% a Embedded issue, but Andrew is looking into something that could help. <div>
<br></div><div>But the biggest problem is Jboss ASs startup time. 45 sec overhead pr test suite run is a bit to much.</div><div>
The Reloaded project is trying to help here as far as I know.. </div><div><br></div><div>First priority for Arquillian is a Weld SE/EE Mock container to speed it up, else for now i recommend using the remote containers.</div>
<div><br></div><div>-aslak-</div><div><br><div class="gmail_quote">2009/12/27 Dan Allen <span dir="ltr"><<a href="mailto:dan.j.allen@gmail.com" target="_blank">dan.j.allen@gmail.com</a>></span><p><font color="#500050">
>
> On Sun, Dec 27, 2009 at 12:31 PM, Johan Eltes <<a href="mailto:johan.eltes@callistaenterprise.se">johan.eltes@callistaenterprise.se</a>> wrote:
>>
>> ...</font></p></div><br><br clear="all"><p><font color="#500050">
--
--
Aslak Knutsen; +47 952 38 791; fax +47 22 33 60 24
Kongens gate 14; Boks 805 Sentrum, 0104 O...</font></p></div>
</blockquote></p>