users@javaee-spec.java.net

[javaee-spec users] Re: [jpa-spec users] [jsr338-experts] JPA 2.2 with Java EE8 Public Draft #2 Review

From: reza_rahman <reza_rahman_at_lycos.com>
Date: Tue, 25 Apr 2017 15:57:53 -0400

While I cannot necessarily completely agree, there are aspects of this I cannot disagree with. In particular, I do think there is room for improvement in terms of collaboration, communication and transparency. For example, I tried to broach the topic of Java SE 8 and Java EE 8 alignment a couple of times now in this group. We ought to be able to discuss even thorny issues openly in the EG with Oracle participation even without explicit support from Oracle's management chain.
At any rate, I am hopeful the right things are still being done for Java EE 8 and JPA.
-------- Original message --------From: Oliver Gierke <ogierke_at_pivotal.io> Date: 4/25/17 1:41 AM (GMT-05:00) To: users_at_javaee-spec.java.net Subject: [javaee-spec users] Re: [jpa-spec users] [jsr338-experts] JPA 2.2 with Java EE8 Public Draft #2 Review
Given those resource and timing constraints now persist for close to two years, and also given that apparently the spec is considered important to a lot of people, would it make sense to distribute the work to the people interested in it instead of keeping all of this within an unofficial "team", which very obviously is not the JPA EG?

I hate to break the news but JPA is becoming a poster child example of what's wrong with the process as is. It's really a shame that we have three months to go and still only see a lot of hand waving while other specs move along just fine and folks have indicated for two years that they're willing to help but have been held outside an anonymous inner circle with "we'll keep you posted" responses (have a look at the JPA mailing list archive for proof).

You're busy? Fine. Then why not let people help? If I have too much on my plate I reach out to others asking for help. This is a community process, right? If there are reasons that community is not pulled into the loop, at least those should be openly communicated.

Thanks,
Ollie

> Am 24.04.2017 um 22:50 schrieb Linda DeMichiel <linda.demichiel_at_oracle.com>:
>
> We are still planning a JPA MR -- at a minimum to include
> repeating annotations.
>
> Given the resource and timing constraints our team is working
> under, we are still in the process of evaluating what other
> features will be able to be achieved in the MR.
>
> Will keep you posted.
>
> -Linda
>
>
> On 4/21/17, 1:25 PM, reza_rahman wrote:
>> Linda,
>>
>> I am bringing this question into the Java EE 8 alias in part due to
>> frustration. While talking to the community about Java EE 8, the
>> question that comes up consistently is JPA. Specifically most people are
>> looking for repeatable annotation support and Date/Time API support. I
>> keep telling people there is an MR in the works to do this based on
>> dated and partial information.
>>
>> Is that still true? If it is true, when can we expect to see this work
>> happen? What can we do to demonstrate the importance of this work to the
>> right people at Oracle?
>>
>> Thanks,
>> Reza
>>
>> -------- Original message --------
>> From: Jody A Grassel <jgrassel_at_us.ibm.com>
>> Date: 4/21/17 4:09 PM (GMT-05:00)
>> To: jsr338-experts_at_jpa-spec.java.net
>> Subject: [jpa-spec users] [jsr338-experts] JPA 2.2 with Java EE8 Public
>> Draft #2 Review
>>
>> Good afternoon. I looked at the Draft #2 for the Java EE 8 spec, and saw
>> that it still looks like there is plans for a JPA 2.2 (EE.6.30 Java
>> Persistence API 2.2 Requirements). Back in late February it was
>> mentioned about a possible Maintenance Release, but since then things
>> have been very quiet among the JPA expert group. July is almost upon us,
>> so I'm bringing this discussion topic back up again if there's going to
>> be any public discourse over the updates (presumably to support
>> capabilities added in Java 8) before we run out of time.
>>
>> Best regards,
>>
>> Jody Grassel
>> WebSphere JPA Development, Support, and Testing
>>