Try typing "hibernate default cache provider" into Google. ;-)
Note that the (official?) docs [1] state: "Note that versions prior to
3.2 use EhCache as the default cache provider." So perhaps most of
the hits refer to old versions of Hibernate. And if the reason for
removing a default al
On 09/09/2009 01:09 PM, Sanne Grinovero wrote:
> 2009/9/9 Steve Ebersole:
>> Again, there is no default cache provider. Â Users must decide which to
>> use.
>
> oh, I'm sorry. There are lots of articles online saying that ehcache
> is the default;
> did this change recently or have they always been
Let me say it for the third time (complementing Steve's first two).
There is no default cache provider, a user has to chose one. One of
the reasons for this move was that the JPA TCK was having issues with
cache systems and multiple initializations.
On 9 sept. 09, at 18:58, Steve Ebersole wr
2009/9/9 Steve Ebersole :
> Again, there is no default cache provider. Users must decide which to
> use.
oh, I'm sorry. There are lots of articles online saying that ehcache
is the default;
did this change recently or have they always been wrong?
Wouldn't it make sense to make Infinispan the def
Again, there is no default cache provider. Users must decide which to
use.
On Wed, 2009-09-09 at 11:42 -0500, Sanne Grinovero wrote:
> I'd like to see Infinispan as default cache provider, AFAIK ehcache is
> the default now.
>
> IMHO the default is to some extend a recommendation to the users, a
I'd like to see Infinispan as default cache provider, AFAIK ehcache is
the default now.
IMHO the default is to some extend a recommendation to the users, at
least that's
how I perceived it when I was new to hibernate: "if they have chosen
it, it must be good".
It would need however to be able to
