Folks,
As you are aware, Ondro and I have began to draft a guide to Jakarta EE 10 contribution now that Jakarta EE 9 is winding down. A large part of this is outlining what people could help contribute to as part of a backlog. Ryan and I started just such a backlog a little bit ago: https://docs.google.com/document/d/1uZFBoIujXCc-gQhCzh_ZdlKEsrsV0yVVIHzBTI3usF8/edit?usp=sharing.
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.
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.
Here is the draft link again: https://docs.google.com/document/d/1uZFBoIujXCc-gQhCzh_ZdlKEsrsV0yVVIHzBTI3usF8/edit?usp=sharing.
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.
_______________________________________________
jakarta.ee-community mailing list
jakarta.ee...@eclipse.org
To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/jakarta.ee-community
2. @RolesAllowed for JAX-RS resources
_______________________________________________
It’s not been defined yet.
For me some starter general themes I would have at the platform level would be;
After that it’s individual spec themes over and above those 3 and addition of new specs if they are ready.
Steve
To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/jakarta.ee-community_______________________________________________
jakarta.ee-community mailing list
jakarta.ee...@eclipse.org
To unsubscribe from this list, visit
https://www.eclipse.org/mailman/listinfo/jakarta.ee-community
--
You received this message because you are subscribed to the Google Groups "Jakarta EE Ambassadors" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jakartaee-ambass...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jakartaee-ambassadors/OF812018F0.8A32A06C-ON8625858B.0051A6FC-8625858B.0051FE1F%40notes.na.collabserv.com.
Not being too familiar with OSGi, could we include module definitions for both?
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
3. JPA - enrich JPQL, for instance allow sub-select in select to avoid writing native queries.
4. JPA native queries pick up schema from orm.xml
5. JPA native queries use named parameters
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.
7. Multitenancy. On the JPA level at first.
On Jun 18, 2020, at 8:25 PM, Reza Rahman <reza_...@lycos.com> wrote:
--
You received this message because you are subscribed to the Google Groups "Jakarta EE Ambassadors" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jakartaee-ambass...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jakartaee-ambassadors/8c3aa88a-ff3a-c580-9220-24036d1a5702%40lycos.com.
Kind regards,Arjan
--
You received this message because you are subscribed to the Google Groups "Jakarta EE Ambassadors" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jakartaee-ambass...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jakartaee-ambassadors/CAE%3D-AhAcjnx3jvZ%3DvY7EwFWzCC6pigC60-59WS-g10yrdyEGPA%40mail.gmail.com.
Werner
I believe the idea is to use CDI when it is available and possible. So it is more "supports" than "requires". However, best to clarify this with folks like Markus.Reza RahmanJakarta EE Ambassador, Author, Blogger, SpeakerPlease 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: Kito Mann <kito...@virtua.com>Date: 6/19/20 11:39 AM (GMT-05:00)To: arjan tijms <arjan...@gmail.com>Cc: Jakarta EE Ambassadors <jakartaee-...@googlegroups.com>, Jakarta EE community discussions <jakarta.ee...@eclipse.org>Subject: Re: [jakarta.ee-community] [jakartaee-ambassadors] Re: Jakarta EE Backlog -> Guide to Jakarta EE 10
_______________________________________________
Isn't there a @RolesAllowed in Jakarta Security and the idea would be to deprecate it in Jakarta REST in favor of that?If Security needed a little more modularity or a "light" module where Authentication or Authorization may not always be required, I guess that is also something to explore.
@Context
: Implementors MUST provide CDI; applications MAY use CDI....@Context
: Applications MUST use CDIIn general honestly I agree. One of the key reasons Jakarta EE still remains relevant despite all its challenges is because it has always made an effort to try to empower a broader ecosystem where it can. The bellwether for me is the likelihood of Spring users integrating the API. If that likelihood is high, we should try to avoid making CDI a hard requirement.
Why not continue to support @Context as a fallback to CDI in environments where CDI is not available?
--
You received this message because you are subscribed to the Google Groups "Jakarta EE Ambassadors" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jakartaee-ambass...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jakartaee-ambassadors/5ef774de.1c69fb81.4f77f.5ea6SMTPIN_ADDED_MISSING%40gmr-mx.google.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jakartaee-ambassadors/5ef77e19.1c69fb81.2acb.a78a%40mx.google.com.
In general honestly I agree. One of the key reasons Jakarta EE still remains relevant despite all its challenges is because it has always made an effort to try to empower a broader ecosystem where it can. The bellwether for me is the likelihood of Spring users integrating the API. If that likelihood is high, we should try to avoid making CDI a hard requirement. Why not continue to support @Context as a fallback to CDI in environments where CDI is not available?
Reza RahmanJakarta EE Ambassador, Author, Blogger, SpeakerPlease 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: Kito Mann <kito...@virtua.com>Date: 6/27/20 12:22 PM (GMT-05:00)To: Jakarta EE community discussions <jakarta.ee...@eclipse.org>Cc: Jakarta EE Ambassadors <jakartaee-...@googlegroups.com>Subject: Re: [jakarta.ee-community] [jakartaee-ambassadors] Re: Jakarta EE Backlog -> Guide to Jakarta EE 10
final HelloWorldResource resource = new HelloWorldResource( configuration.getTemplate(), configuration.getDefaultName() ); environment.jersey().register(resource);
To view this discussion on the web visit https://groups.google.com/d/msgid/jakartaee-ambassadors/CAE%3D-AhAx6H4PD7Tzx011%3D60_aR-sbMpm6CL4XwO4j8weP-J1kA%40mail.gmail.com.
On Jun 27, 2020, at 12:33 PM, reza_rahman <reza_...@lycos.com> wrote:In general honestly I agree. One of the key reasons Jakarta EE still remains relevant despite all its challenges is because it has always made an effort to try to empower a broader ecosystem where it can. The bellwether for me is the likelihood of Spring users integrating the API. If that likelihood is high, we should try to avoid making CDI a hard requirement. Why not continue to support @Context as a fallback to CDI in environments where CDI is not available?