| Re: [faces-dev] Faces 4.1 M2 upcomming |
Thanks again
The specification is becoming simpler and more practical every day, but some problems arise in the vocabulary
In a complete MVC application, for business methods EJB Lite was used but now this is also seen as a CDI Bean with the Stateless annotation(different specification), for the controller made by FacesServlet there was the JSF CDI Bean (it still appears like this in NetBeans) with the difference that these have the @Named annotation. I think it's more a question of names than functionalities. I have been working with JSF (Faces) since the first version and I like it.
I already have and I'm already reading David R. Heffelfinger's new book, just to see if this CDI issue is clear to me, which seems to have replaced a lot of things.
Thanks for your patience
Hi,On Wed, 6 Mar 2024 at 11:11, Joaquim Hangalo via faces-dev <faces-dev@xxxxxxxxxxx> wrote:Thanks for the clarification.
Therefore, the old managed Beans were replaced by CDI, but we can use the _expression_ "Managed Beans" to talk about CDI when used at the Jakarta Faces levelOld managed beans (aka native jsf managed beans) were fully removed see https://jakarta.ee/specifications/faces/4.0/jakarta-faces-4.0#backward-compatibility-with-previous-versionsWe did leave some traces of the term here and there, which are spec bugs. It's really good you mentioned this, so I'll take a look to remove them fully. The term "managed bean" was a bit overloaded. There were the JSF native ones, but also a pseudo super spec that made a lot of things in Jakarta EE managed beans (an attempt to unite all different component models), but this one failed / was overshadowed by CDI.I think we mostly just call the CDI beans in Jakarta Faces "beans" or when they sit behind a page specifically a "backing bean".Kind regards,Arjan Tijms