| Re: [servlet-dev] Big ticket items for Servlet 6 / Jakarta EE 10? |
|
While I certainly appreciate the idea of aligning more Jakarta EE specifications to CDI, who would really be the target audience for a CDI based Servlet component model? Wouldn't this audience in practice have a lot of overlap with JAX-RS users? If so, is this an effort worth undertaking? Maybe this is something best pursued as an experimental framework to see what the uptake would be instead of work done in Jakarta? Personally I think it is important to try to align JAX-RS and Servlet if it is not too late to do so. A related area to perhaps think about is making Servlet more Reactive. Although even in this space I am not sure what the practical uptake has been, if there has been sufficient maturity and what the impact of Project Loom will be. What is slam dunk for me is working on the existing backlog of more minor enhancements including keeping track of HTTP/3. I think an API to reduce the need for frameworks to do annotation scanning would also be invaluable and overdue. This is potentially even something that could go into Java SE. I do think this is an API that should be separate from Servlet and usable in applications that may not be Servlet based. 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: arjan tijms <arjan.tijms@xxxxxxxxx> Date: 8/27/20 7:53 AM (GMT-05:00) To: servlet developer discussions <servlet-dev@xxxxxxxxxxx> Subject: [servlet-dev] Big ticket items for Servlet 6 / Jakarta EE 10? Hi,
A number of other specs in Jakarta have provided some ideas or roadmap items for their next major versions. Until so far I don't think Servlet has provided any such ideas, although we do have a backlog of about 112 issues, which are mostly clarifications or small enhancements. One of the pitched themes for Jakarta EE 10 is alignment, and for this theme I'd like to make a few proposals: 1. In cooperation with Jakarta REST (previously JAX-RS), see if we can define a subset of Servlet on which Jakarta REST can conveniently depend. At the moment most Jakarta REST implementations are based on Servlet anyway, but officially there's no such dependency. 2. For in a Jakarta EE environment, and as a separate related new spec, define a CDI version of Servlet, for instance with the proposed package jakarta.servlet.cdi. This would define what a Servlet would look like as a pure CDI bean, and in addition would finally allow us to transfer the HttpServletRequest producer that's now in core CDI itself. Alternatively this can also be proposed as a completely independent spec, not using the jakarta.servlet package, and just building on Servlet (like, e.g. Jakarta Faces does). Thoughts? Anything else that's big? Any of the existing issues we'd like to prioritize for Servlet 6? Kind regards, Arjan Tijms |