Hi,
I like this option better as it does not come with the baggage that comes with changing @FacesConfig
Thanks!
Kind regards,
Manfred Riem
From: faces-dev <faces-dev-bounces@xxxxxxxxxxx> On Behalf Of
Thomas Andraschko
Sent: Monday, January 18, 2021 8:19 AM
To: faces developer discussions <faces-dev@xxxxxxxxxxx>
Subject: Re: [faces-dev] Deprecate @FacesConfig
If it should be for auto-faces-servlet-mapping-marker only, then we should really talk about it if it's the best way.
We could also name it then "@AutoRegisterFacesServlet" or take the faces-config.xml inside the WAR as marker, which probably already exists in 90% of the times.
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
_______________________________________________
faces-dev mailing list
faces-dev@xxxxxxxxxxx
To unsubscribe from this list, visit
https://www.eclipse.org/mailman/listinfo/faces-dev
|