[hibernate-dev] [infinispan-dev] Hibernate 3.5.0.Beta-1 released

Manik Surtani manik at jboss.org
Thu Sep 24 10:41:11 EDT 2009

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 altogether is to pass a TCK and multiple inits, we  
can have a chat about this to see how we can make this work  
(Infinispan has a concept of a default cache, which "just works" and  
is always available, if that helps with multiple inits).

All the same, it would be good to have some sort of preference  
expressed in the docs even if you don't want to ship a default, but  
that's up to you guys.


[1] http://docs.jboss.org/hibernate/stable/core/reference/en-US/html/performance.html#performance-cache

On 9 Sep 2009, at 18:04, Emmanuel Bernard wrote:

> 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 wrote:
>> 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, 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 work at least in single-vm mode
>>> without configuration,
>>> to keep it as simple as possible for beginners.
>>> 2009/9/9 Galder Zamarreno <galder.zamarreno at redhat.com>:
>>>> Steve, taking in account that at least in the community version
>>>> you ship
>>>> a few different cache providers (correct me if I'm wrong), what
>>>> about
>>>> putting something in the Hibernate docs where you recommend using
>>>> Infinispan? i.e. "Infinispan is the recommended 2LC provider"
>>>> On 08/31/2009 06:02 PM, Steve Ebersole wrote:
>>>>> We do not make any cache integration the default.  There are too
>>>>> many
>>>>> variables that have to come in to play...
>>>>> On Mon, 2009-08-31 at 17:55 +0200, Galder Zamarreno wrote:
>>>>>> Bugger, this was released hours before I committed the
>>>>>> Infinispan cache
>>>>>> provider :(
>>>>>> Steve, let's catch up before next 3.5 release in order to figure
>>>>>> out
>>>>>> what's needed to make Infinispan the default cache provider. Do
>>>>>> you make
>>>>>> such decision based on any performance test or the configuration
>>>>>> itself?
>>>>>> My aim is to make Infinispan the best 2nd level cache provider
>>>>>> out there.
>>>>>> On 08/21/2009 06:43 PM, Steve Ebersole wrote:
>>>>>>> Hibernate 3.5.0.Beta-1 has been released.  Please see
>>>>>>> http://in.relation.to/12153.lace for details.
>>>> --
>>>> Galder Zamarreño
>>>> Sr. Software Engineer
>>>> Infinispan, JBoss Cache
>>>> _______________________________________________
>>>> infinispan-dev mailing list
>>>> infinispan-dev at lists.jboss.org
>>>> https://lists.jboss.org/mailman/listinfo/infinispan-dev
>> -- 
>> Steve Ebersole <steve at hibernate.org>
>> Hibernate.org
>> _______________________________________________
>> hibernate-dev mailing list
>> hibernate-dev at lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/hibernate-dev
> _______________________________________________
> infinispan-dev mailing list
> infinispan-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/infinispan-dev

Manik Surtani
manik at jboss.org
Lead, Infinispan
Lead, JBoss Cache

More information about the hibernate-dev mailing list