> In EE 11, we should completely remove Managed Beans Spec from Jakarta EE
> 11 Platform spec and remove all of the references.
Could someone more familiar with this confirm what this means for the
Servlet specification.
Do we just need to remove the one reference to the managed bean
specification from the Servlet spec doc?
The reference to @PostConstruct below concerns me. Is there any
expectation that removing the Managed Bean spec will have any impact on
section 15.5 of the Servlet specification (Annotations and Resource
Injection)?
I think, as we have discussed in the past to some degree, that we must make a stronger distinction in the Servlet spec for Servlet running outside the Jakarta EE platform (such as Tomcat and Jetty) and inside the Jakarta EE platform (such as GlassFish, WildFly, OpenLiberty).
Within the Jakarta EE platform Servlets should (probably) become CDI beans (WildFly already does this, setting a precedent). This means @Inject (specifically) is handled by CDI.
Outside the Jakarta EE platform, Servlet containers are free to support @Inject and @Postconstruct as they wish. Maybe delegate the task to CDI if it's available.
Thoughts?
Kind regards,
Arjan Tijms
