| Re: [mojarra-dev] Starting Jakarta Faces 4.0 |
_______________________________________________Hi,On Thu, Oct 29, 2020 at 1:13 AM Lars Grefer <eclipse@xxxxxxxxxxxxx> wrote:How would the "Continue re-basing on CDI" part affect projects, which currently use JSF without the CDI bean container?
Many projects want to use the Spring Framework as bean container for example.
There are existing integrations for both Spring WebFlow (https://docs.spring.io/spring-webflow/docs/2.5.1.RELEASE/reference/html/spring-faces.html) and Spring Boot (https://github.com/joinfaces/joinfaces)Would these use-cases still be possible with Faces 4.0?
Faces has been dependent on things like CDI for over 10 years now, but has done so in small steps. Some might even say too small steps, but it is what it is. Things like the FlowScope and custom data-models were CDI based from the beginning, there never were non-CDI versions of those.The way forward is to support Spring Beans in a very similar way as Spring frameworks support CDI beans, e.g. how Spring MVC and Spring Security are integrated into EE environments and using CDI. CDI, via its producers and portable extensions has first class support for building bridges to other containers / DI systems.Some pointers to get you started:If there are volunteers, we could perhaps even look into providing a distribution which would embed (shade) a CDI implementation like OWB together with a bridge.With the native managed bean system being removed, in terms of size and complexity this would not even be a major difference. It would essentially replace the internal native managed bean system code with an internal OWB managed bean system. I don't think the core Faces team has the resources for this, but a volunteer project, perhaps even sponsored if a company would be interested, can surely be taken into account.Kind regards,Arjan Tijms
mojarra-dev mailing list
mojarra-dev@xxxxxxxxxxx
To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/mojarra-dev