[Hibernate-issues] [Hibernate-JIRA] Closed: (HB-560) Caching configuration with same class mapped in many sessionFactories

[<leg...@at...>]

Message:

   The following issue has been closed.

   Resolver: Gavin King
       Date: Wed, 24 Dec 2003 5:37 AM

See HB-566
---------------------------------------------------------------------
View the issue:

  http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-560


Here is an overview of the issue:
---------------------------------------------------------------------
        Key: HB-560
    Summary: Caching configuration with same class mapped in many sessionFactories
       Type: Improvement

     Status: Closed
   Priority: Trivial
 Resolution: DUPLICATE

    Project: Hibernate2
 Components: 
             core
   Versions:
             2.1

   Assignee: 
   Reporter: William Drai

    Created: Wed, 17 Dec 2003 6:01 AM
    Updated: Wed, 24 Dec 2003 5:37 AM

Description:
I'm sorry to reopen this issue but I still have a small problem.

I have the same class mapped in three differents session factories to three different MySQL databases.

Everything works (now with EHCache) BUT I am not able to define different cache configurations for the three cache instances because the cache region name is the same (it is the class name). 
This is also true for all cache providers.

Moreover I have not tried yet the replicated cache but I don't see how the replication could be able to identify the correct cache instance in the remote server if all three have the same region name.

For the moment I implemented a wrapper CacheProvider which just adds the session factory property 'cache.region_prefix' before the region name and added this property to the Hibernate JMX MBean.
It would be a lot easier to configure if this was directly configured in hibernate. This is really trivial and I hope it could be useful for other people.

Thanks.

William



---------------------------------------------------------------------
JIRA INFORMATION:
This message is automatically generated by JIRA.

If you think it was sent incorrectly contact one of the administrators:
   http://opensource.atlassian.com/projects/hibernate/secure/Administrators.jspa

If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira