|Re: [jakartaee-tck-dev] [faces-dev] Should Platform TCK tests that include Managed Beans be removed from the EE 10 Platform or updated to include an empty beans.xml?|
On 4/28/22 12:19 PM, arjan tijms wrote:
Every trace of the Faces Managed Beans (as defined in faces-config.xml) should indeed be totally removed. There's nothing there that can, or should, support those.
Do we need to add a https://github.com/eclipse-ee4j/common-annotations-api issue for deprecating/removing https://github.com/eclipse-ee4j/common-annotations-api/blob/master/api/src/main/java/jakarta/annotation/ManagedBean.java in the next Annotations release?
Kind regards,Arjan Tijms
On Thu, Apr 28, 2022 at 6:06 PM Scott Marlow <smarlow@xxxxxxxxxx> wrote:
GlassFish issue 23917  asks "Since managed beans are removed now via jakartaee/faces#1547, should Faces 4.0 implementations fail to deploy applications with faces-config.xml that specify managed beans?" We are looking to make a Platform TCK test change to adjust for the "CDI is not available" failure mentioned in  but I am wondering if the test adjustment should be to
- Add empty beans.xml so CDI is available as suggested in .
- Remove the Platform TCK tests that use Managed Beans, since Managed Beans are no longer supported in Faces 4.0.
faces-dev mailing list
To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/faces-dev
_______________________________________________ jakartaee-tck-dev mailing list jakartaee-tck-dev@xxxxxxxxxxx To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/jakartaee-tck-dev_______________________________________________
jakartaee-tck-dev mailing list
To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/jakartaee-tck-dev
Back to the top