[jboss-user] [JBoss Cache: Core Edition] - Re: on child insert parent, child collection updated in DB b

[bstansberry@jboss.com]

"dukehoops" wrote : 
  | I didn't understand your comment above. Were you saying that you will take my test source and adapt it to hibernate-jbc test suite or were you suggesting I do it?

I meant I would do it, although if you want to do it and submit a patch that would be much appreciated. :-) I'm travelling next week so I wouldn't be able to port it for another week.

anonymous wrote : 
  | I took another look at hib-jbc project but could not find any examples of tests exercising hibernate and jbc *3*. I looked here:
  | http://anonsvn.jboss.org/repos/hibernate/core/trunk/cache-jbosscache2/

Have another look. :)

An hour or so ago I committed a bunch of stuff for http://opensource.atlassian.com/projects/hibernate/browse/HHH-3585 which is the task to move to JBC 3.  That task is really just to port tests from a branch where we proved last fall that the existing code already works with JBC 3. I added today some subtasks to HHH-3585 today related to some renaming stuff related to this, but the fact that those changes will eventually happen shouldn't prevent adding tests.

anonymous wrote : 
  | Debugging tells me I am using TransactionalAccessDelegate. Shouldn't OptimisticTxDelegate be used since my Domain object do use Hibernate's @Version? Or is that irrelevant because the two choices translate to deprecated Optimistic or Pessimistic locking in JBC and we're using MVCC?

Correct it relates to JBC's OPTIMISTIC locking scheme, so isn't relevant to MVCC.

anonymous wrote : 
  | I also have caches configured as Srping Beans (with Configuration and RuntimeConfig also spring beans) and use org.jboss.cache.CacheFactory directly to build caches (as described in JBC3 User Guide). org.hibernate.cache.jbc2 on the other hand uses org.jboss.cache.CacheManager to do the same. The reason I went with that approach is that org.hibernate.cache.jbc2 seems to want to work of jbc2-styled treecache.xml config only and does not parse org.jboss.cache.config.Configuration

If JBC 3 is used, the CacheManager can parse a JBC3-format file. It can also parse the legacy format.  Building up the Configuration POJO and then injecting it into the CacheManager works too; that's what JBoss AS 5 does, just using the JBoss Microcontainer instead of Spring.


I'll have to think about your REPEATABLE_READ issue. Do you see that with PESSIMISTIC or OPTIMISTIC instead of MVCC?

View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4215859#4215859

Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4215859