Over the years I've written boatloads of Junit method tests but never got around to actually doing anything in container (properly). For a variety of reasons, loading up cactus and doing in-container testing just seemed harder to work out than just running with breakpoints and logging things in a spreadsheet. However, as I've gotten busier, and processes and procedures have become more involved and time-consuming, that bias on my part isn't an option any more.
Unfortunately, Cactus is now pretty much dead. I couldn't even find a reasonably recent download of it any more.
What suggestions do people have for an easy to set up in-container test bed that works well with IBM RAD 8?
We learn more from our mistakes than our successes.
In most cases they are classes that have one or more elements reading and/or writing to an Oracle db via a JNDI alias to a JDBC connection. A handful connect to some web service and the remainder are Struts 1.3 actions.
author & internet detective
For the Struts actions, I recommend Selenium or JWebUnit. Selenium tests through the browser. JWebUnit pretends to be a browser.
For EJBs, JUnit in Action (published a couple years ago) does recommend Cactus. Lately, I've been using Spring - which is the container so you just use the run with Spring annotations. That won't solve your problem though.