Hello,
I have a couple questions:
* Should there be an issue created to track this work?
* On which branch should this work based if we target a release with 5.2?
In parallel, I have been reading the pointers Vlad gave and I intend to
verify the current code actually works in all these cases :-) Any chance
there exist some kind of test suite for L2 caching providers?
Regards,
Louis
On Fri, May 20, 2016 at 3:41 PM Steve Ebersole <steve(a)hibernate.org> wrote:
What we had decided before during a discussion with myself, Alex
Snaps,
Radim and Sanne was to develop a JCache-based L2 case module and that
Ehcache 3 would be supported through that mechanism. We'd continue support
for the current Ehcahce 2 based hibernate-ehcache module for a short period
of time.
On Fri, May 20, 2016 at 7:48 AM Guillaume Smet <guillaume.smet(a)gmail.com>
wrote:
> Hi,
>
> On Fri, May 20, 2016 at 9:54 AM, Emmanuel Bernard <
emmanuel(a)hibernate.org>
> wrote:
>
> > 3. change the Ehcache module and move it from v2 to v3
> >
>
> Please don't do that.
>
> I'm pretty sure users will need to test Ehcache 3 before going live and
it
> shouldn't be tied to an Hibernate upgrade. Cache is a very sensible
subject
> and I'm pretty sure moving to Ehcache 3 will come with its challenges. We
> should at least have 1 or 2 versions allowing both Ehcache 2 and 3.
>
> Moreover, last time I checked, there was no Jgroups replication yet in
> Ehcache 3 (or it's not documented).
>
> --
> Guillaume
> _______________________________________________
> 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