[hibernate-dev] [ORM] EhCache 3 and JCache

[Louis Jacomet]

Hey Steve,

That's a tough question.
For tomorrow I don't see how ... Technically the code is out there. But it
lacks documentation which is needed: how to select a specific provider and
specify a URI which can be used as config source. That still needs to be
added.

In one week, more likely. I am willing to commit on having it all in proper
shape.

Which branch will 5.2 be cut from? Because when I last checked some changes
happened in master that impacted api but seem to be identified as 6.0
related.

What are the chances someone from the hibernate side can look at it in this
timeframe? To make sure nothing dumb slips through.

Regards,
Louis


On mar. 24 mai 2016 at 22:57, Steve Ebersole <steve at hibernate.org> wrote:

>
> https://hibernate.atlassian.net/browse/HHH-10770
>
> On Tue, May 24, 2016 at 3:51 PM Steve Ebersole <steve at hibernate.org>
> wrote:
>
>> Hi Louis,
>>
>> In my opinion,
>>
>>    - Yes, of course :)
>>    - The plan is to release 5.2 tomorrow.  So either this would have to
>>    be done tomorrow or the release date pushed back in order for this to be
>>    part of 5.2.  We could push 5.2 another week, but would the work for this
>>    be done in a week?
>>
>>
>> On Tue, May 24, 2016 at 3:39 PM Louis Jacomet <ljacomet at gmail.com> wrote:
>>
>>> 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 at 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 at gmail.com>
>>>> wrote:
>>>>
>>>> > Hi,
>>>> >
>>>> > On Fri, May 20, 2016 at 9:54 AM, Emmanuel Bernard <
>>>> emmanuel at 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 at lists.jboss.org
>>>> > https://lists.jboss.org/mailman/listinfo/hibernate-dev
>>>> >
>>>> _______________________________________________
>>>> hibernate-dev mailing list
>>>> hibernate-dev at lists.jboss.org
>>>> https://lists.jboss.org/mailman/listinfo/hibernate-dev
>>>>
>>>