Welcome to the new Spring.io forums!
If this is your first visit, be sure to check out the
by clicking the link above, and for security reasons, use the
forgot password link to reset your password..
You may have to register before you can post: click the register
link above to proceed. To start viewing messages, select the forum that you want to visit
from the selection below.
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.