[ https://issues.jboss.org/browse/ISPN-7534?page=com.atlassian.jira.plugin.... ] Sebastian Łaskawiec commented on ISPN-7534: ------------------------------------------- There is an ongoing work on JCache.next. They are [targeting into JEE8|https://groups.google.com/forum/#!topic/jsr107/YIBGV4YQ5WY]. Top issues mentioned by Ondrej Mihalyi are: {quote} * necessary improvements to align with Java EE (we need them to bring JCache into Java EE) * optional improvements (CDI cache scope, asynchronous API, injection of Cache and CacheManager) - seems that Payara and Tomitribe already put some effort on their own, and would welcome a standard approach * integration with other specs (JPA 2nd level cache, caching JPA queries, facelet cache in JSF, JTA to span transaction over both cache and database, ...) - JCache should provide means to do it, but first JCache needs to be officially included in Java EE scope {quote} [~NadirX] added a few others: {quote} * define where container-created caches/managers are placed in JNDI so that they can be injected in applications. Because these caches could be shared among deployments, we need to think about ClassLoader issues. * define a way for a deployment to specify the caches it wants created within its lifeycle. For example JPA uses persistence.xml, CDI uses beans.xml. JCache doesn't (yet) specify a standard declarative format. * As for the Async API, we should retarget JCache to Java 8 so that we can use CompletionStage/CompletableFuture instead of coming up with our own non-standard API. {quote} Werner Keil however concluded: {quote} Just very briefly condensed it sounded like "if JCache was fit for Java EE it could be included" but looking at the rather aggressive Java EE 8 timeline, I would not expect that to happen before Java EE 9 IMHO. JTA support is just one, but certainly an important goal JCache 1.0 missed out on. Better integrating with standardized configuration (as of the new Config JSR) instead of reinventing its own configuration sub-system would be another aspect to tackle, but the Config JSR also aims at that for EE 9 mostly. {quote} -- This message was sent by Atlassian JIRA (v7.2.3#72005)