| Re: [jakartaee-platform-dev] [servlet-dev] Pruning managed beans from the component specs |
_______________________________________________We discussed this internally regarding the pruning Managed Beans. It was brought to my attention that in fact Managed Beans was not removed from Jakarta EE 10 Platform Spec. Instead, it just deprecated this spec. This might be an oversight. Managed Beans spec used to be under Web Profile. In Jakarta EE 10, this spec was indeed removed from Jakarta EE 10 Web Profile spec. However, it was still listed under the Jakarta EE 10 Web Profile release in this diagram. The diagram needs to be updated to reflect the current status.In EE 11, we should completely remove Managed Beans Spec from Jakarta EE 11 Platform spec and remove all of the references.ThanksEmilyOn Wed, May 31, 2023 at 5:46 PM Arjan Tijms <arjan.tijms@xxxxxxxxxxx> wrote:Hi,We removed the managed beans spec from the platform. However, we still have several specs referencing it. From the top of my head, REST, Servlets and Faces still have lingering references to them._______________________________________________Servlet is even a special case, perhaps. It supports (according to the managed bean spec) @Inject and @PostConstruct, but there are not yet plans to make Servlets CDI beans instead. REST and Faces do have those plans.Do we (at the platform level) want to set a mandate or strong recommendation that all specs abandon usage of managed beans, and move to CDI (when running inside an EE container, as not all always specs do)?Thoughts?Kind regards,Arjan Tijms
servlet-dev mailing list
servlet-dev@xxxxxxxxxxx
To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/servlet-dev
--Thanks
Emily
jakartaee-platform-dev mailing list
jakartaee-platform-dev@xxxxxxxxxxx
To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/jakartaee-platform-dev