"bstansberry@jboss.com" wrote:
Re: the tests, there are tests in the Hibernate 3.3 core cache-jboss-cache2 module that avoid using the AS. See the org.hibernate.test.cache.jbc2.functional package. The difficulty is those bring in dependencies on the Hibernate test module, plus I'm sure have JBC 2 ties. So it will require some effort to break those ties and let them run standalone.

M2_REPO/junit/junit/3.8.1/junit-3.8.1.jar
M2_REPO/antlr/antlr/2.7.6/antlr-2.7.6.jar
M2_REPO/commons-collections/commons-collections/3.1/commons-collections-3.1.jar
M2_REPO/dom4j/dom4j/1.6.1/dom4j-1.6.1.jar
M2_REPO/xml-apis/xml-apis/1.0.b2/xml-apis-1.0.b2.jar
M2_REPO/javax/transaction/jta/1.1/jta-1.1.jar
M2_REPO/org/slf4j/slf4j-api/1.4.2/slf4j-api-1.4.2.jar

"bstansberry@jboss.com" wrote:
On the name, how about "hibernate-jbc-cache-provider"? CacheProvider is the legacy API that's replaced in 3.3. Including it in the name is at least a small indication this is a legacy integration.

A question with regards to org.hibernate.test.cache in hibernate-testing module and org.hibernate.test.cache.jbc2.functional package in cache-jbosscache2:

cache-jbosscache2 uses hibernate-testing but for some reason, it seems to redefine Item, VersionedItem and Item.hbm.xml. However, after comparing them, they look identical. This is important for me in case I can just use these classes from hibernate-testing module, or you're planning to remove these from here and keep the ones in cache-jbosscache2, in which case I'd need to redefine them for hibernate-jbc-cacheprovider.

Indeed. For the time being I've added a dependency on hibernate-testing 3.3.0.CR1 which lets me move forward and tackle the more difficult part of the UT testing, which is making your tests work with JBC 1.x.

I've forwarded the thread to Steve but it might take a while for him to come back as he's in Tuscany with the rest of Seam/Hibernate guys.

Right, I understand now how that duplication come about. I'll stick to hibernate-testing for the time being.

Re: pulling hibernate-testing 3.3. I've just realised that it pulls hibernate core 3.3, so you end up with Hibernate 3.2 and 3.3 in the classpath. I'm reverting back to pulling the classes the test classes that I need from 3.2 into hibernate-jbc-cacheprovider

I've got 1-5 plus .functional package tests running. It still needs some polishing because the set up and tear down execution phases of these tests is a <insert_a_lovely_word_here> mess, so if I run several tests together, they fail. Why? Well, because there's part of the set up code that is only run once per test case execution and other part that is run before each individual test. This is making it hard for me to figure out where on earth I need to put tear down code.

On top of that, things vary between single node and multi node tests, i.e. for multi node tests, one of the node's cache is set up once per unit test case class, whereas for the other is set up before each single test method.

Anyway, as Brian said, I think I have enough now to build a binary, so I'm gonna leave the testing to a side and focus on creating the binary and integrating it with Portal 2.7.x.

I'll commit the code today or tomorrow.

Btw, apologies for the late reply but for some reason I didn't get an email for Brian's reply.

https://svn.jboss.org/repos/jbossas/projects/cluster/hibernate-jbc-cacheprovider/trunk/

http://anonsvn.jboss.org/repos/jbossas/projects/cluster/hibernate-jbc-cacheprovider/trunk/

I'm now gonna try to build a jar and integrate it with Portal 2.7.x.

I'm back :)

Local puts only enhancement is now coded, tested and committed. Switched the tests to READ_COMMITTED.
Removed *Hook from the cache provider names.

I'll now work on the integration part so that Prabhat can start testing asap.