[wildfly-dev] Jakarta Servlet as the foundation for web workloads

I'm curious what people think about the use of Jakarta Servlet as the foundation for web workloads in the WildFly technology ecosystem. Particularly people interested in Jakarta REST / RESTEasy. Upfront note: I am NOT suggesting dropping Jakarta Servlet or other view layer specs that require it. This is about Servlet's role in handling other web workloads. Context here is a discussion on the jakarta-platform-dev list of MP JWT and Jakarta Security: https://www.eclipse.org/lists/jakartaee-platform-dev/msg03725.html A key point in that thread is that MP in general does not require Servlet or Jakarta Authentication. Jakarta REST does not require Servlet. Also, Servlet has its own ecosystem independent of EE Platform and EE Web Profile; i.e. people who participate in the spec and provide impls of it who are not interested in providing the EE security specs or even foundational things like CDI. And then WildFly is also somewhat in the middle; we provide all of EE but we also value people being able to tailor their installation to provide what their app *needs*. WildFly configs pretty much all include servlet, but core Undertow doesn't, and our undertow subsystem can be configured (and provisioned by Galleon) without it. I just now posted on that jakarta-platform-dev thread about this, but that was from an EE architecture POV. I'm interested in what people think about this from a WildFly or WildFly component project POV. Best regards, Brian Stansberry He/Him/His