This forum is now a read-only archive. All commenting, posting, registration services have been turned off. Those needing community support and/or wanting to ask questions should refer to the Tag/Forum map, and to http://spring.io/questions for a curated list of stackoverflow tags that Pivotal engineers, and the community, monitor.
There are very few situations in which I would use Cactus.
I would go for the following types of testing for your objects:
1. True unit testing. Does not involve any container. Just JUnit, with mock objects or stubs.
2. Integration testing in a Spring container but not in a web container. This is fast, and skips the deployment step. See the superclasses in the org.springframework.test package in the mock JAR shipped with Spring. You can even have the superclasses create and rollback transactions if you like. With appropriate design, you can use virtually the same Spring XML config as in the deployed app.
3. Test your remote entry points remotely, against a deployed app, using a remote client.