Hi,
there are at least 2 different views what does it mean to "integrate JCache
with Java EE":
1. Expose JCache concepts in a managed way - basically what Payara (and I
think TomEE?) has done. From the surface this looks like a relatively low
effort. (but it could still creep out - e.g. what about different scopes?
Request-specific caches, various defaults, etc.)
2. Integrate JCache with other concepts from Java EE: 2nd level JPA cache
is a nice example. I am sure there are more. One would have to go through
all Java EE specs and think where an integration could make sense. This
could be a massive effort with overlaps to different areas of Java EE.
Cheers,
Jaromir
On Thu, Dec 31, 2015 at 12:39 AM, arjan tijms <arjan.tijms_at_gmail.com> wrote:
> Hi,
>
> In the Java EE 8 survey JCache came out as one of the top prioritised
> features. See
> https://blogs.oracle.com/theaquarium/entry/java_ee_8_survey_final
>
> If I'm not mistaken JCache would originally have been included in Java EE
> 7, but just missed the boat and went final a little while after EE 7. So
> you could perhaps say that for EE 8 the spec had all the time in the world,
> since it was mostly ready before EE 8 even started.
>
> Yet, I don't see much activity regarding JCache and Java EE 8.
>
> If I understood correctly what mostly needs to be done still is the EE
> integration. But that too actually seems largely done already.
>
> For the RI and CDI see:
> https://github.com/jsr107/RI/tree/master/cache-annotations-ri/cache-annotations-ri-cdi
>
>
> More specifically for Payara:
> https://github.com/payara/Payara/tree/master/appserver/payara-appserver-modules/payara-jsr107/src/main/java/fish/payara/cdi/jsr107
>
> So I wonder, what are the current plans for JCache and Java EE 8?
>
> Kind regards,
> Arjan Tijms
>
--
“Perfection is achieved, not when there is nothing more to add, but when
there is nothing left to take away.”
Antoine de Saint Exupéry