The way the Hibernate TreeCacheProvider uses the TreeCache is broken (or, in other words, not optimal), and has been changed. The new code will be available as part of Hibernate 3 final. The integration code will be beta though, and will be final in one of the subsequent Hibernate versions. The main reason is the mismatch between H's assumption of optimistic locking and JBossCache's pessimistic locking. The new Hibernate TreeCacheProvider will minimize the locking exceptions, but not completely remove them: only the JBossCache version implementing optimistic locking will get rid of them completely, this is planned for JBossCache 1.3 or 1.4.
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3871695#3871695 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3871695 ------------------------------------------------------- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click _______________________________________________ JBoss-Development mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/jboss-development
