Hi Andrew, We have a solution in Cactus 1.5 (which you can download in the nightly build area). In 1.5, there is a new Ant Integration Module, which provides a fully reusable and generic Ant integration.
There is no doc yet for it but if you look at the cactus sample, you'll see how to use it. It completely cactifies your application war by: - adding the cactus jars - performing a merge of your application web.xml with the definitions needed by Cactus (such as the redirectors). This merge has been written by Chris Lenz recently and I'm not sure if it is working yet nor not. Thanks -Vincent > -----Original Message----- > From: Andrew van der Voort [mailto:[EMAIL PROTECTED] > Sent: 20 March 2003 04:30 > To: [EMAIL PROTECTED] > Subject: Separating Cactus tests from the application > > Hi. I have integrated the first of hopefully many tests into out > environment. Since I am testing struts actions, I should also say that I > have strutstestcase on the front of this, but I don't think it changes the > problem I am having. > > My working environment is to have my application .war file built as > normal. > Since I am using Cactus, I have added to the .war the following: > - Updated web.xml that specifies the ServletRedirector servlet mapping > - Required cactus and strutstestcase jars in WEB-INF/lib > - Test Cases built into a separate package structure > > Naturally this .war is packaged up into a .ear for deployment on JBoss. > Everything works fine. However the problem with this approach is that the > .war file is not suitable for distribution to clients. It contains cactus > jars and classes that are not necessary. > > What we want to do is prepare the application .ear without anything > related > to unit testing in it, and package a separate .war or .ear with all the > testing classes and jars in it. This is so that once the testing is > complete, we can be confident that the .ear we have is good, and can be > distributed as-is. > > Otherwise the only alternative is to package the .ear for testing, test, > and then repackage the .ear for distribution. > > Can this be done? > > Thanks, Andrew > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
