The problems are (1) what provider to use and (2) what access strategy
to use.
We are not like most other providers that only offer a single type of
cache and strategy.
On 05/02/2011 04:09 PM, Emmanuel Bernard wrote:
I agree with you.
Today, if you do not / forgot to specify "javax.persistence.sharedCache.mode",
you're up for a long debugging ride before figuring it out.
So +1 for ENABLE_SELECTIVE.
That is the default if people use hbm.xml files + SessionFactory anyways.
Emmanuel
On 2 mai 2011, at 15:55, Scott Marlow wrote:
> The JPA specification allows us to choose what happens when
> shared-cache-mode is not specified (JPA 2.0 3.7.1 specification).
>
> Hibernate currently (as best as I can tell), defaults to
> shared-cache-mode of NONE.
>
> Should we change the shared-cache-mode default to ENABLE_SELECTIVE in
> Hibernate 4.0? That would mean one less configuration step for
> application developers.
>
> Is there any negatives for changing shared-cache-mode to ENABLE_SELECTIVE?
>
> Scott
>
> _______________________________________________
> hibernate-dev mailing list
> hibernate-dev(a)lists.jboss.org
>
https://lists.jboss.org/mailman/listinfo/hibernate-dev
_______________________________________________
hibernate-dev mailing list
hibernate-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/hibernate-dev
--
Steve Ebersole <steve(a)hibernate.org>
http://hibernate.org