[Springframework-developer] Mock objects

[Rod J. <rod...@in...>]

All,

I've just upgraded from EasyMock 0.8 to 1.0.

See the bottom of http://www.easymock.org/Documentation.html for the new
features, and why doing this was worthwhile.

I've upgraded the Jar (same name, so no project changes needed).

I've also needed to change a number of test classes because of tighter
behaviour in 1.0. For example, some tests incorrectly used
setReturnValue(null) instead of setVoidCallable().

Also the JdbcTemplate tests needed changing to allow more than one call to
DataSource.getConnection(). Thomas, I assume this is to get the metadata to
be able to look up error codes?

There are still a lot of deprecations. However, I think we can live with
these and gradually update the code to get rid of them.

The principal updates to remove the deprecations are:

- EasyMock.controlFor() should change to MockControl.createControl()
- mockControl.activate() => replay()
- remove import of EasyMock

I've only made these changes in tests I otherwise needed to change. I may
try a global replace later today.

We still need to upgrade from Mock Object 0.07 to 0.09. However, this breaks
a number of the JDBC tests, which I don't have time to look at now. Any
volunteers? (Trevor? I think this breaks some of your code.)

Regards,
Rod