concept Apache Cactus in category ant

This is an excerpt from Manning's book Ant in Action.
The main reason for sticking with the JUnit 3.8 branch is because it’s been so successful that it has become integrated with much of the Java development infrastructure. IDEs recognize test classes and can run them; Ant’s tasks are built for JUnit 3 and added only incomplete JUnit 4 support in Ant 1.7. Most critically, there are extension tools such as Apache Cactus, which work only with JUnit 3.8.x. Apache Cactus is an extension for JUnit that can run tests inside an application server; it’s invaluable for some server-side testing, and something which we’ll look at in chapter 14. There are other extensions which have yet to migrate, such as HttpUnit, XmlUnit, and DbUnit. If you need these extensions, you need to stick with the JUnit 3.8.x branch.
We need unit tests against the internals of the system, alongside the functional tests of HttpUnit. As Web and Java EE applications run only on an application server, we cannot directly run such unit tests under <junit>. Something devious is needed here, which is where Apache Cactus comes into play.