Anything else that's big? Any of the existing issues we'd like to prioritize for Servlet 6?
Another thing that would be to support Executors to be injected and/or exposed by the container. Too many deployments end up having many many thread pools, so it would be good to facilitate sharing.
This has a lot of overlap with Jakarta EE Concurrency. If we were going to do this I think it should be something like a getExecutor() method on the ServletContext.
I don't mind the idea of injection if we added a Servlet specific CDI qualifier (@ServletExecutor), but that requires a direct dependency on the CDI API for the @Qualifier annotation which is not going to fly.
I would be very very strongly opposed to anything that adds some new type of dependency injection just for Servlet. Jakarta EE as a whole already has too many, and it is definitely confusing to users (questions about why @Contextual from JAX-RS is not working on a CDI bean are super common on the Quarkus mailing list).
Stuart
_______________________________________________
servlet-dev mailing list
servlet-dev@xxxxxxxxxxx
To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/servlet-dev
