I'm using Hibernate 3.3.1 GA and Ehcache 1.5 and have noticed that the property that enables you to specify an ehcache configuration is ignored.



If I specifiy another name for the file in the config above (say ehcache-2.xml), the ehcache config is still read from ehcache.xml.

Furthermore, if I rename my actual file ehcache.xml to something else (say ehcache-2.xml) and then set the configuration_file_resource_path to match the hibernate logs tell me that no configuration was found and it instead uses the ehcache failsafe settings.



This occurs with the net.sf.ehcache.hibernate.SingletonEhCacheProvider or with the org.hibernate.cache.EhCacheProvider class supplied in the hibernate-ehcache module.

It looks like the property hibernate.cache.provider_configuration_file_resource_path is ignored and ehcache tries to load its configuration from a file called ehcache.xml no matter what.

Has this property been renamed in hibernate 3.3? All the documentation and comments in the API docs for the org.hibernate.cache.EhCacheProvider classes state that this provider_configuration_file_resource_path property is the one to use to set an alternative ehcache configuration.

Many thanks in advance for any suggestions.[/code]

I think I have managed to resolve this myself.

I had a look in the http://anonsvn.jboss.org repository and examined the way that cache providers are set up.

It looks like this underwent a change from Hibernate 3.2 to 3.3 where Echache has become less of a default implementation of caching for Hibernate.

As a result of this, it seems that the property that needs to be used in hibernate.cfg.xml is net.sf.ehcache.configurationResourceName as demonstrated below:



That is probably why the hibernate.cache.provider_configuration_file_resource_path is now redundant. It looks like the documentation both in the API docs and in SVN haven't quite caught up with this change in how the specific cache provider implementations are set up in Hibernate.

As a result of using the net.sf.ehcache.configurationResourceName property I can now specify an ehcache config with a name other than /ehcache.xml, so my problem is solved.

However, I'd appreciate some confirmation as to whether my statements above are correct.

It also looks like a SingletonEhCacheProvider has made its way into the main trunk for the hibernate-ehcache module in SVN (http://anonsvn.jboss.org/repos/hibernat ... vider.java).

Presumably, when this is released I should use that version instead of the net.sf.ehcache.hibernate.SingletonEhCacheProvider.

Any clarification on the best way to understand the hibernate-ehcache integration in 3.3x will be much appreciated!