This was fixed as part of EJB3 RC9 Patch 1.
You should be using TreeCacheProviderHook which, from this release, works for both
Optimistic and Pessimistic locking JBoss Cache instances.
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4039360#...
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...