anonymous wrote : | I am assuming this requires an XADataSource, right? | Yes.
anonymous wrote : | Optimized locking seems to fail no matter what, with this except: | You need Hibernate's OptimisticTreeCacheProvider if you plan to use optimistic locking. See http://wiki.jboss.org/wiki/Wiki.jsp?page=JBossCacheHibernate anonymous wrote : | Ok it does actually start filling in the Node values after a while ... | This is because you have: | <async>true</async> | which means writes to the DB will not happen immediately, but are batched instead. Why are you using a cache loader with Hibernate anyway? The purpose of a cache loader is so that an in-memory cache has a place to persist state so state survives over reboots and evictions. With Hibernate, this state will survive *anyway* (in Hibernate) so why add a cache loader as well? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4031083#4031083 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4031083 _______________________________________________ jboss-user mailing list [email protected] https://lists.jboss.org/mailman/listinfo/jboss-user
