My application deploys on customer hardware and connects to three different databases. One of the databases can be version 4 or version 5, I get around this by building a jar containing the hibernate-config.xml file for that database and the mapping and class files for version 4 and another jar for version 5. The install program chooses which jar to deploy.

When it comes to the ehcache.xml file things get more complicated. If multiple databases have multiple versions (later versions have more tables) I would need to generate a considerable number of permutations of the cache configuration. I need non-default timeToLiveSeconds for most of the objects. Should I just declare regions for every table that might be present or is there a better way?

Has anyone considered a rollup model for ehcache.xml where it references other xml files on the classpath like hibernate does with mapping files?

I have the same issue. It appears that once ehcache is configured, it just keeps that same configuration and I get "relation does not exist" error messages.

The strange thing is that each session factory does not create a separate Ehcache instance.

any solutions to this?