Re: [jakartaee-tck-dev] [faces-dev] Should Platform TCK tests that inclu

[arjan tijms <arjan.tijms@xxxxxxxxx>]

> Yes. Where are the issues that were used to deprecate ManagedBeans? When I searched through the platform issues I did not find any.

It was deprecated in JSF 2.3: 

 * @since 2.0
 * @deprecated This has been replaced by the Managed Beans specification in general and specifically the dependency
 * injection, scopes and naming from the CDI specification. Note that the <em>eager</em> attribute for application
 * scoped beans is replaced specifically by observing the {@code jakarta.enterprise.context.Initialized} event for
 * {@code jakarta.enterprise.context.ApplicationScoped}. See 6.7.3 of the CDI spec for further details.
 *
 */
@Retention(RetentionPolicy.RUNTIME)
@Target(ElementType.TYPE)
@Inherited
@Deprecated
public @interface ManagedBean

See https://github.com/eclipse-ee4j/mojarra/blob/3.0/impl/src/main/java/jakarta/faces/bean/ManagedBean.java#L71

The intention to deprecate was already put in a warning somewhere in the API (I can look it up if needed) just before releasing JSF 2.0 in 2009.

Kind regards,

Arjan Tijms

On Thu, Apr 28, 2022 at 7:49 PM Scott Stark <starksm64@xxxxxxxxx> wrote:

Yes. Where are the issues that were used to deprecate ManagedBeans? When I searched through the platform issues I did not find any.

On Apr 28, 2022 at 12:27:40 PM, Scott Marlow <smarlow@xxxxxxxxxx> wrote:

On 4/28/22 12:19 PM, arjan tijms wrote:

Hi,

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?

Scott

Kind regards,

Arjan Tijms

On Thu, Apr 28, 2022 at 6:06 PM Scott Marlow <smarlow@xxxxxxxxxx> wrote:

Hi,

GlassFish issue 23917 [1] 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 [1] but I am wondering if the test adjustment should be to:

1. Add empty beans.xml so CDI is available as suggested in [3].
2. Remove the Platform TCK tests that use Managed Beans, since Managed Beans are no longer supported in Faces 4.0.
   

Scott

[1] https://github.com/eclipse-ee4j/glassfish/issues/23917
[2] https://github.com/eclipse-ee4j/jakartaee-tck/issues/950
[3] https://github.com/jakartaee/faces/issues/1600#issuecomment-1058049454

_______________________________________________
faces-dev mailing list
faces-dev@xxxxxxxxxxx
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
jakartaee-tck-dev@xxxxxxxxxxx
To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/jakartaee-tck-dev