I was looking at the portal 2.0.1 source code and noticed that the Hibernate 
MBean (SessionBinderFactory) explicitly sets the cache provider to Hibernate's 
HashtableCacheProvider after reading the config file, overridding any setting I 
place there.

Is there a reason this is done instead of using the JBoss Cache provider and 
hooking the portal's cache into JBoss Cache and its invalidation framework?

Any reasoning behind this would be helpful to understand.

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

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


-------------------------------------------------------
This SF.Net email is sponsored by the JBoss Inc.  Get Certified Today
Register for a JBoss Training Course.  Free Certification Exam
for All Training Attendees Through End of 2005. For more info visit:
http://ads.osdn.com/?ad_id=7628&alloc_id=16845&op=click
_______________________________________________
JBoss-user mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/jboss-user

Reply via email to