I've taken a look at the integration being done with JBCache/Hibernate. A few things come to mind: 1. Why is the integration so complex? There are 32 classes, whereas JBCache 1.4 and Hibernate integration was done with 2 classes. I'm thinking of "OptimisticTreeCache" and "TreeCacheProvider". 2. What are the risks with changing the existing integration classes to use the new JBCache API? I have done so, and I don't see any problems, though I haven't attempted anything under load.
Incidentally, is there a recommended eviction strategy (was there ever one?) to use with JBCache 2.0 and Hibernate. I did not see one with "hibernate-recommended-config.xml". View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4098008#4098008 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4098008 _______________________________________________ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
