Hi,
The historical main purpose was NOT for automatically mapping the FacesServlet, it was for configuring a mode that would behave like a specific version.
Thanks!
Kind regards,
Manfred Riem
From: faces-dev <faces-dev-bounces@xxxxxxxxxxx> On Behalf Of
arjan tijms
Sent: Monday, January 18, 2021 8:08 AM
To: faces developer discussions <faces-dev@xxxxxxxxxxx>
Subject: Re: [faces-dev] Deprecate @FacesConfig
Hi,
The latest and greatest should indeed always be used. That weird simulation is just odd, but didn't we already agree to remove the "fake faces 2.2 mode"?
@FacesConfig's main purpose is to add the Faces servlet mapping automatically.
Before @ManagedBean would be used for that, but we've deprecated it, and are going to remove it. Some of the other Faces annotations can still be used for that, but most of them are not always present in a Faces application.
So +1 for removing the fake version and its semantics (always use latest and greatest
-1 for removing @FacesConfig itself, as it's a marker
TBH I didn't understand why you introduced it anyway.
As you said, the default should be the latest and greatest always.
You can never simulate 100% of JSF2.0 in e.g. JSF2.3 container, if you configure @FacesConfig(2.0);
I would also get rid of it an rely on a specific feature configuration like
javax.faces.ENABLE_CDI_RESOLVER_CHAIN.
_______________________________________________
faces-dev mailing list
faces-dev@xxxxxxxxxxx
To unsubscribe from this list, visit
https://www.eclipse.org/mailman/listinfo/faces-dev
|
