By reza_rahman on Jan 31, 2013
We are very sad to report that JCache (JSR 107) missed a few critical deadlines and will not make it in time for Java EE 7. This is undoubtedly dissapointing to many of you as the community indicated strong support for JCache in the well-participated Java EE 7 survey. However, the consensus on both the Java EE 7 and JCache EGs was that it is best to not hold up Java EE 7 any further (as you know Java EE 7 has a ton of other great stuff including WebSocket, JMS 2, JAX-RS 2, JSON-P, Java Batch, EE Concurrency and the like - check out my Java EE 7 slide deck from a few months ago).
JCache is fully expected to move forward strongly independent of Java EE 7 and be an excellent candidate for Java EE 8. You should also be able to use JCache with Java EE 7 as a drop-in API provided the spec is finalized far ahead of Java EE 8. We encourage you to follow the Java EE 7 EG and JCache EG discussions on the topic and provide your feedback.