Cool, I am tuned in there and will definitely help you build support if/when needed. One key objective for doing this is having more active folks in the mailing lists so that they can take part in all features - major, minor and bugs at the individual specification level.
Reza Rahman
Jakarta EE Ambassador, Author, Blogger, Speaker
Please note views expressed here are my own as an individual community member and do not reflect the views of my employer.
Sent via the Samsung Galaxy S7, an AT&T 4G LTE smartphone
-------- Original message --------
From: Vano Beridze <vanuatoo@xxxxxxxxx>
Date: 6/19/20 1:05 AM (GMT-05:00)
To: Jakarta EE community discussions <jakarta.ee-community@xxxxxxxxxxx>
Subject: Re: [jakarta.ee-community] Jakarta EE Backlog -> Guide to Jakarta EE 10
The issue #4 about picking up schema from orm.xml in native queries is definitely a minor issue and I will discuss it in JPA group.
Thanks for bringing forward the
discussion. My thoughts embedded below. I hope others will chime
in too.
Reza Rahman
Jakarta EE Ambassador, Author, Blogger, Speaker
Please note views expressed here are my own as an individual
community member and do not reflect the views of my employer.
On 6/17/2020 12:50 PM, Vano Beridze
wrote:
Hello,
I would add this issues to the list:
1. JAX-RS add uniform API for
multipart/form-data
Is this really a salient/common enough scenario to add in the
document? I may have done a poor job explaining the document, but
at this point I think we just want to list out major realistic
features likely to get a broader range of developers excited and
interested in at least tracking Jakarta EE 10 if not contributing.
This one feels to me like a feature that probably is not "headline
worthy" but still important enough to consider as an enhancement.
What do you think? I certainly would encourage you to pursue this
in the Jakarta REST project regardless.
2. @RolesAllowed for JAX-RS resources
Is this really needed separate from the possibilities outlined in
the document for the Security API? What do you think?
3. JPA - enrich JPQL, for instance allow
sub-select in select to avoid writing native queries.
This makes a lot of sense and one I have heard often from folks.
I'll generalize/abstract this as "Add more SQL features in
JPQL/Criteria API such as sub-select, WITH clause..."
4. JPA native queries pick up schema from
orm.xml
Can you kindly explain this a bit?
5. JPA native queries use named parameters
Is this also too minor to think of as a major possibility to
highlight? Again, I certainly would encourage you to pursue this in
the Jakarta Persistence project regardless.
6. Introduce standard for distributed caching.
Today we have JCache, Hazelcast, Infinispan, Redis. We need to
have standard for memory storage which is cluster aware and
synchronized.
I would like to think what others think of this. While in principal
I would love to see JCache move to Jakarta, in practical terms, will
this actually happen in terms of IP transfer? If not, maybe it is
best to leave this out?
7. Multitenancy. On the JPA level at first.
What do others think about this? The reason I ask is that this
feature was abandoned fairly quickly in Java EE 7 and no provider
seems to implement it since then. How likely is this to happen?
Just a reminder that I would like to wrap this up by next
weekend and begin authoring the actual guide. There has
been some discussion, but it would be good to have more.
We would like to start some discussion on this backlog now. I don't think every possible change, detail or idea needs to be hashed out right now. It is likely best to focus
on headline features more likely to attract people.
Ideally we should try to close this discussion by next weekend. Please do chime in. Once we stabilize this conversation we can focus on drafting the contribution guide.
Reza Rahman
Jakarta EE Ambassador, Author, Blogger, Speaker
Please note views expressed here are my own as an individual community member and do not reflect the views of my employer.