|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 1:49 PM, Scott Stark wrote:
Yes. Where are the issues that were used to deprecate ManagedBeans? When I searched through the platform issues I did not find any.
https://github.com/jakartaee/faces/blob/master/spec/src/main/asciidoc/ExpressionLanguageAndManagedBeanFacility.adoc still includes Managed Beans and Annotations 2.1 still has https://github.com/eclipse-ee4j/common-annotations-api/blob/master/api/src/main/java/jakarta/annotation/ManagedBean.java.
It sounds like we need a tracking Platform issue for post EE 10 deprecation/removal of ManagedBeans + an Annotations issue as well, since we cannot really remove Faces Managed Beans.
I think that javax.faces.bean.ManagedBean became
jakarta.faces.bean.ManagedBean and jakarta.faces.bean.ManagedBean
was removed from the Jakarta Faces 4.0 spec and the Platform TCK
tests that use jakarta.annotation.ManagedBean just needs updating
to include the empty beans.xml.
I also don't see any jakarta.faces.bean.ManagedBean references in the Platform TCK.
On Apr 28, 2022 at 12:27:40 PM, Scott Marlow <smarlow@xxxxxxxxxx> wrote:
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
_______________________________________________ jakartaee-tck-dev mailing list jakartaee-tck-dev@xxxxxxxxxxx To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/jakartaee-tck-dev
Back to the top