-----Original Message----- From: Matt Raible [mailto:[EMAIL PROTECTED] Sent: 25 February 2004 02:03 To: Cactus Users List Subject: Re: Starting/Stopping Resin with Ant
From: http://www.mail-archive.com/[EMAIL PROTECTED]/ msg04762.html
<snip>
Yes, I'd also like that we add <startcontainer>/<stopcontainer> Ant
tasks for starting/stopping containers. It should be very easy to
implement as we're already doing it in the <cactus> task. We could
probably even reuse the existing <[container name]> nested elements
(they're already Ant task in their implementation I think), and simply
add an "action" attribute (action="start|stop"). Anyone wishing to help?
</snip>
[snip]
4/ I'm not too sure to implement the feature. The best solution is probably to create a startcontainer/stopcontainer tasks (or a single <run> task with an action attribute) in o.a.c.i.a package and let it accept a nested AbstractContainer element. The other option would be to directly try to reuse the existing container elements as top level Ant tasks but adding to them an action attribute (action="start|stop"). It may require other attributes. The first solution is probably cleaner.
I believe we already have this functionality in <runservertests> (although not documented):
<runservertests testurl="...">
<start target="start.resin"/>
<test>
<!-- Here you can invoke any Ant tasks you like -->
<echo>Here we go</echo>
<antcall target="foo"/>
<antcall target="bar"/>
</test>
<stop target="stop.resin"/>
</runservertests>Cheers, Chris -- Christopher Lenz /=/ cmlenz at gmx.de
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
