On Mon, Sep 19, 2011 at 16:23, Paul Bakker <span dir="ltr"><<a href="mailto:paul.bakker.nl@gmail.com">paul.bakker.nl@gmail.com</a>></span> wrote:<br><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
<div style="word-wrap:break-word">I think we're talking about two different things here<div>1) Deploying to AS7 using Shrinkwrap/Arquillian instead of file copies.</div></div></blockquote><div><br></div><div>This got me thinking, perhaps the Arquillian managed container should support both a remote deployment and a local deployment. The remote deployment is via the deployment APIs of a running server, whereas the local deployment is a file copy to a deployment directory. I'm hesitant to introduce another type of container in Arquillian, so perhaps it's just an aspect of a managed container...seems to fit best.</div>
<div><br></div><div>Regardless, the file copy should be abstracted away as a impl detail of the container adapter.</div><div><br></div><div>-Dan</div><div> </div></div>-- <br><div>Dan Allen</div>Principal Software Engineer, Red Hat | Author of Seam in Action<br>
Registered Linux User #231597<br><br><div><a href="http://www.google.com/profiles/dan.j.allen#about" target="_blank">http://www.google.com/profiles/dan.j.allen#about</a><br><a href="http://mojavelinux.com" target="_blank">http://mojavelinux.com</a><br>
<a href="http://mojavelinux.com/seaminaction" target="_blank">http://mojavelinux.com/seaminaction</a><br></div><br>