1 Reply Latest reply on Jun 8, 2015 10:02 AM by rhauch

    JSR-333 status change to: "dormant"

    awoods

      How is ModeShape responding to the December 2014 JSR-333 status change to: "dormant"?

      How is this going to impact the development and end-of-life of ModeShape?

       

      The Java Community Process(SM) Program - JSRs: Java Specification Requests - detail JSR# 333

        • 1. Re: JSR-333 status change to: "dormant"
          rhauch

          We had been participating in JSR-333 several years ago until activity on it stopped. Basically, it was hung up on the reference implementation, and the Jackrabbit community had not really expressed an interest (since most of their activity had moved to Jackrabbit Oak). None of the other implementations implement all of the optional parts of the JSR-283 spec (including Jackrabbit Oak), so lack of a reference implementation for JSR-333 was the nail in the coffin.

           

          How will this affect ModeShape? Basically, not at all. We've already implemented the few API changes we hoped to see added in JSR-333 via our custom API extensions to the standard interfaces and our extensions to JCR-SQL2. So, ModeShape will continue to be implement the JSR-283 specification.