[
http://opensource.atlassian.com/projects/hibernate/browse/HHH-3585?page=c...
]
Steve Ebersole commented on HHH-3585:
-------------------------------------
Brian, actually is there really any reason to keep the 1.x integration around? Do
y'all still "support" 1.x?
Could we not instead just::
1) drop the current hibernate-jbosscache module
2) rename the current hibernate-jbosscache2 module to hibernate-jbosscache
I mean you are talking about 3.x support here and 2.x has been out for some time. Do you
really see a benefit to keeping up on 1.x support?
Convert org.hibernate.cache.jbc2 integration to use JBoss Cache 3
-----------------------------------------------------------------
Key: HHH-3585
URL:
http://opensource.atlassian.com/projects/hibernate/browse/HHH-3585
Project: Hibernate Core
Issue Type: Task
Components: caching (L2)
Reporter: Brian Stansberry
Assignee: Steve Ebersole
Fix For: 3.5
JBoss Cache 3 is the main development branch for JBC. It introduces MVCC locking, which
should help the Hibernate 2LC use case.
Integration with JBoss Cache 3 and use of MVCC has already been tested against the
Hibernate Core 3.3.1.GA tag, on the
https://svn.jboss.org/repos/hibernate/core/branches/JBOSS_CACHE_3/ branch. Task here is
to port the changes (all in cache-jbosscache2 testsuite) to trunk.
--
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....
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira