JSR-107 Early Draft Released (after nearly 12 years)

It’s been in the works for a number of years, more than a decade, but finally we’re making some solid process moving the JCache Specification forward, hopefully for inclusion in Java EE 7.

Yesterday the JCP made the important step of posting the Early Draft specification and API for JSR107. See http://jcp.org/en/jsr/detail?id=107 for details.

While an enormous amount of progress was made last year and early this year (by many people – not so much me) the JSR was somewhat delayed while the legals were resolved, especially with respect to ensuring clean and clear IP for Java itself, the eventual JCache Providers and the community.   Thankfully this stage is complete and we can move forward.

Source Code
For those of you that don’t know, all of the artifact are hosted on GitHub at https://github.com/jsr107.

If you’d like to pick up builds, you can do so from the CloudBees continuous build infrastructure here: https://jsr107.ci.cloudbees.com

JSR 107 Resourcing
Now the the Early Draft is out, Greg Luck (Terracotta) and myself (now a co-spec lead) will be committing the majority of our time to get this finished, together with appropriate implementations and the Technology Compatibility Kit (TCK), should you wish to write your own implementation.   However these things don’t happen in isolation so it would be greatly appreciated if you can free up some time over the next few months to take a look.   Unfortunately if we fail to get feedback, we’ll be force to make stuff up and “move on”.   ie: We both want this JSR completed asap.

JCP 2.7 Process
The Early Draft Review has now started and it is scheduled to end on 22 November. During this process we’ll continue to work on answering questions, making required changes etc.  Once complete we’ll start the Public Draft (another 30 days of review) and during the last week, we’ll schedule an EC ballot.  Should everything go well we’ll complete the RI and TCK then seek final approval for the JSR.

For those of you attending the next Coherence SIG (in London), I’ll be there to give an update and talk about Coherence support.

Cheers

– Brian

About these ads

4 responses to “JSR-107 Early Draft Released (after nearly 12 years)

  1. Could you describe what was the reason for the slow progress? Caching shouldn’t be as complex as EJB or even JPA. I’m curious what changed in the API in the last 10 years :)

    • Unfortunately lots of things! Companies changed, people left, people joined, community didn’t really push/demand it, legal processes intervened, JCP process intervened, companies/people didn’t have enough free time to invest, people had “life events” etc. The list could be quiet monumental really. The good news is that it’s progress now… and you can be involved.

      Caching shouldn’t be as complex as EJB and JPA

      Yeah that’s what everyone says :P Unfortunately when you try to implement a consistent coherent Cache, especially something that scales and is distributed, things get complicated very quickly. Having an API that works for both “in-process” and “out-of-process” Caching is a challenge, and not one that many people really seem to want or enjoy implementing.

  2. Pingback: Additional new material WebLogic Partner Community | WebLogic Community

  3. Pingback: Additional new material WebLogic Community | WebLogic Community

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s