I think they believe the reverse.
Personally I am leery of accepting this because ultimately it is yet
another piece of code we are not the experts on but will be responsible for
maintaining.
On Wed, Nov 23, 2016 at 1:39 AM Gunnar Morling wrote:
> This is a very interesting contribution, only I
This is a very interesting contribution, only I am wondering why it should
be located within the Hibernate ORM project.
It seems interesting to Spring users only, so wouldn't it be better located
under the Spring umbrella?
--Gunnar
2016-11-22 17:50 GMT+01:00 Louis Jacomet :
> Hi all,
>
> Can't
Hi all,
Can't really say anything about the Hibernate integration, but the reason
Spring caching does not implement JCache is because the abstraction is
tailored at Spring integration and allows to wrap JCache into Spring Cache,
because the later existed before the former. SO it would be weird to
I think this gets back to the idea we discussed when first integrating the
JCache solution.. namely the idea of provisioning for these regions. At
the time we concluded that it would be better to simply have the JCache
integration not deal with the configuration/building of
a javax.cache.CacheMana
My initial reaction to this was of highly skeptical, as I don't see
how adding layers and layers of adapters helps performance, which is
crucial to the very purpose of Caching being effective.
But the PR mentions interesting things; if indeed people want to use
cloud service abstractions for "gene
