It appears you are trying to hand-craft your DAO mocks. Over time this can get very tedious and difficult to maintain because not only will you have to maintain your production code and the tests for them, you'll also have to maintain your hand-crafted mocks. This also adds complexity that I don't think is really necessary.
If you define an interface for your DAOs and use a mocking framework like Mokito, you can have Mokito manage your mock DAOs for you. Then you can concentrate on the parts of the tests that
you should be: the
test data and the assertions that you want to make. Unit tests need to run very fast and they shouldn't cross any execution boundaries like having to read the file system or access a database or access a Web Service. I suggest you keep your test data/mock data in your test classes (this is in reference to another
thread you started).