How do you swap dev/prod session factories for integr test?

[Colin Yates]

Hi all,

At the moment I am unit testing my DAOs by manually constructing the sessionFactory and injecting it. I have been looking at the spring integration tests, but I cannot figure out how to manage the seperate contexts.

I *could* add all the component contexts and include the development-persistence.xml and *exclude* the applicationContext.xml, but there are other beans in appContext.

What do other people do? Do you have an aenmic appContext which just imports other context?

Thanks all.

Col

[Rod Johnson]

People normally factor the persistence related stuff (datasource, transaction manager) into a separate XML doc like persistence-test.xml and persistence-deploy.xml. SessionFactory is usually common, just referencing/referenced by those shared beans, but you may have sep hbm.xml files I guess and this approach also accommodates them.

This XML file is one of those assembled into a single context. All the other XML definitions will normally be the same in both environments.

HTH,
Rod

[Colin Yates]

Right, I think I got myself all confused because my sessionFactory includes a configLocation which indicates a datasource (for hibernate), but I also have a dataSource defined in the context.xml as well (from JNDI).

So I remove the datasource from my context and provide a development hibernate.cfg.xml for unit tests (the sessionFactory.configLocation is classpath:hibernate.cfg.xml).

Thanks Rod.

[Andrew Swan]

Note that if you use different DB types in test and production (e.g. your tests use an HSQL in-memory db), you will also need to factor the sessionFactory bean definition out into separate test/prod XML files, because part of the sessionFactory definition is the hibernate.dialect property, which of course needs to be set to different values for the two db products in question.