2 Replies Latest reply on Nov 17, 2005 4:19 PM by Kurt Gabrick

    Why does Portal use Hibernate's HashtableCacheProvider

    Kurt Gabrick Newbie

      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.