Jakarta Query Socialization

[starksm64]

Prior to moving the Jakarta Query project into a public review phase, I would like to complete a discussion of any concerns that might exist at the specification committee level.

Socialization of the concept amongst developers has been well received, and the initial committer list has been expanded to include all JPA and Jakarta Data leads.

Are there any issues that need to be addressed before we move forward with the Jakarta Query proposal?

[ivargrimstad]

Thanks @starksm64! It will be brought to the attention of the spec committee tomorrow.

[pzygielo]

Is this about socialization of Jakarta Data (title) or Query (body)?

[hantsy]

What is Jakarta Query, I can not find the introduction in eclipse.org or Github.com.

[ivargrimstad]

As I understand it, Jakarta Query will be a new specification project where JPQL and JDQL are specified. That means moving them out of Jakarta Persistence and Jakarta Data.

[gavinking]

What is Jakarta Query, I can not find the introduction in eclipse.org or Github.com.

@hantsy The idea was first proposed in the JPA discussion here:

jakartaee/persistence#603 (comment)

With the advent of Jakarta Data, the need is now more pressing, since, with JDQL being a well defined subset of JPQL, we need a "neutral ground" to evolve the full language and its subset in a unified, consistent way, so that it meets the needs of both its "clients".

[gavinking]

@starksm64 I think maybe the title of the issue is not what you intended.

[starksm64]

@ivargrimstad Was this discussed at the spec committee? It would be good to get a green light on moving Jakarta Data forward.

For some reason I don't think it has been on the agenda yet. I'll add it explicitly for the meeting today

[ivargrimstad]

@starksm64 It was discussed in the Spec Committee today, and no initial comments or objections were put forward.
So you can go ahead with the proposal. Note that there may be more opinions voiced as the proposal is further detailed.