[jpa-spec users] Re: Feedback on the JPA 2.2 MR process...

From: arjan tijms <>
Date: Wed, 16 Dec 2015 16:51:00 +0100


On Wed, Dec 16, 2015 at 4:18 PM, Paul Benedict <> wrote:

> Will not the JPA 2.2. process comb the backlog to see what other good
> issues can be included? I watched the presentation too and know EclipseLink
> has many supposed 2.2 features already prototyped; I just wasn't expecting
> it to be the end-all of the entire feature set.

I can't speak for the MR/spec lead, but I interpreted the given list as
just an initial list of issues that seem likely. For clarity this list is:

* CDI support in attribute converters
* Meta annotations
* Repeating annotations

* Date/time support
* Stream support in queries
* JPQL/SQL string from Query

* Autocloseable for entity manager/factory (for Java SE)
* Pagination support for JPQL and Criteria
* Creating criteria from query
* Subquery(entityType) to criteria
* Query metamodel by entity name
* Multitenacy

The "problem" is of course that it's a MR, not a full spec revision with a
selected EG etc. And a MR has a limited scope and doesn't have an official
EG etc. I'd rather seen an official full release given the amount of issues
that are still open for JPA and the fact that JPA is arguably one of the
most important specs in Java EE (I'd personally say it's only second to

Yet, a MR is better than nothing.

Kind regards,
Arjan Tijms

> Cheers,
> Paul
> On Thu, Dec 10, 2015 at 9:10 AM, Scott Marlow <> wrote:
>> Hi,
>> I have some feedback that I would like to share about the JPA 2.2 process
>> (see email [1]). While, I enjoyed listening
>> to Lukas Jungmann's presentation [2], I am disappointed to not yet be able
>> to participate in the discussion of what changes should be in JPA 2.2. I
>> think it is very important that we follow the JCP 2.9 1.1.1 [3] guidance.
>> I think that the easiest way to ensure that the substantial development of
>> the JPA 2.2 MR specification is observable, is to immediately start a
>> mailing list.
>> I also would like to congratulate Lukas Jungmann, on being the new JPA
>> specification lead! :-)
>> Regards,
>> Scott
>> [1]
>> [2]
>> [3] Section 1.1.1 from
>> Expert Groups may choose to keep purely administrative matters private,
>> but all substantive business must be performed in a manner that allows the
>> public to observe their work and to respond to it. All proceedings,
>> discussions, and working documents must be published, and a mechanism must
>> be established to allow the public to provide feedback. One common way of
>> meeting these requirements is through the use of mailing lists, but other
>> alternatives such as blogs, Wikis, and discussion forums may be preferred.
>> Whatever communication mechanisms are chosen, these must include an
>> archiving function so that a record of all communications is preserved.
>> Archives must be readable by the public. 3
>> "