Hibernate 3.5.0.Beta-1 has been released. Please see http://in.relation.to/12153.lace for details.

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. >> >

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(a)redhat.com&gt;: > 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(a)lists.jboss.org > https://lists.jboss.org/mailman/listinfo/infinispan-dev >

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(a)redhat.com&gt;: >>> 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(a)lists.jboss.org >>> https://lists.jboss.org/mailman/listinfo/infinispan-dev >>> > -- > Steve Ebersole <steve(a)hibernate.org&gt; > Hibernate.org > > _______________________________________________ > hibernate-dev mailing list > hibernate-dev(a)lists.jboss.org > https://lists.jboss.org/mailman/listinfo/hibernate-dev _______________________________________________ infinispan-dev mailing list infinispan-dev(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/infinispan-dev

2009/9/9 Steve Ebersole&lt;steve(a)hibernate.org&gt;: > 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?