Hi Andy, > -----Original Message----- > From: Andy Kriger [mailto:[EMAIL PROTECTED] > Sent: jeudi 20 janvier 2005 17:44 > To: Cactus Users List > Subject: how to use an existing container > > The Ant documentation explains a lot about the Ant tasks created for > Cactus (cactifywar, cactus, runservertests). However, as far as I can > find, it doesn't talk much about using Ant with an existing container > that has been properly configured (for example in Tomcat, placing the > Cactus JARs in the shared/lib and adding the servlets to > conf/web.xml).
Yes. I think the reason it doesn't mention this yet is because it's your choice as a user of Tomcat, WebLogic, etc to configure them the way you wish. But maybe you mean something else. In any case, I'm all for improving the doc and if someone submits a doco patch, I'll happily check it in. > > After a day or so of messing around with the cactus and runservertests > tasks, I stumbled across a handy hint buried in the mailings lists. > Hopefully this will help other developers starting with Cactus. > > Pass the cactus.contextURL property to the JVM running your unit tests > (by your favorite means). See > http://jakarta.apache.org/cactus/integration/manual/howto_config.html#clie > ntside > for more info. > > Run your JUnit tests from the standard junit task as you would normally. > > That's all there is to it, nothing fancy, but the info is not as easy > to find as it could be. Hope this saves someone out there some time. The way it is currently organized is that all the manners to run Cactus tests are described on one page: http://jakarta.apache.org/cactus/integration/index.html The tip you mention seems to correspond to one way of running Cactus tests which is the "manual" way (i.e. you take care of configuring Cactus yourself). I'd like to pinpoint where on your reading path you've stumbled. I think I've seen a JIRA issue that you've opened that says that the runservertests task documentation does not mention the cactus properties. Good catch! We'll need to patch this. Do you think you could provide a documentation patch? I've just reviewed the <runservertests> and <cactus> tasks and it appears that the cactus.contextURL property is set in the <cactus> task but not in the <runservertests> one. This is normal as the <cactus> task has the port and context defined but this is not the case for the <runservertests> task. Thanks Andy! -Vincent --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
