> -----Original Message----- > From: Vincent Massol [mailto:[EMAIL PROTECTED] > Sent: Monday, May 31, 2004 2:57 PM > To: 'Matt Raible' > Cc: 'Cactus Users List' > Subject: RE: New <resin2x>/<resin3x> tasks > > When you say a "runcontainer" task do you mean a task to > start/stop a container or to run Cactus tests in it (same as > the existing <cactus> task?). > > I'm asking because the current <cactus> task supports your > use case (it has "if" attributes for all containers). >
I dig the <cactus> task, so yes, I'm looking for something like that. What I would like is the ability for a user to set a property in build.properties and it uses that container for testing. What I'm trying to do is make it as easy as possible for me (and users of AppFuse) to switch from Tomcat to Resin to Weblogic or whatever Cactus supports. I'm trying to get away from running Servlet/Controller/Action tests in-container - so I eventually might not need Cactus there. However, I test my JSPs with Canoo's WebTest and those will always depend on a running container. Currently, I depend on tomcat.start and tomcat.stop targets that I gathered from Cactus examples. I'm looking for a simple way to start the container, run the tests, and stop it. From my understanding, the <cactus> task has this built in for most containers - and I'd like to re-use that functionality. Matt --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
