[MYFACES-4490] TCK: Spec Issue2948IT: Context Management for Build-In Scopes

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 2.2.15, 2.3.10, 2.3-next-M7, 3.0.2, 4.0.0-RC2
• Fix Version/s: 4.0.0-RC3
• Assignee: Thomas Andraschko
• Reporter: Volodymyr Siedlecki
• Created: 25/Oct/22 15:32
• Updated: 16/Dec/22 21:37
• Resolved: 08/Dec/22 10:08

Description

This problem was found in the faces22/cdiInitDestroyEvent application under Issue2948IT.

The spec issue is found here: https://github.com/eclipse-ee4j/mojarra/issues/2952

As the spec describes:
`Portable extensions are encouraged to fire an event with qualifier @initialized(X.class) when a custom context is initialized, and an event with qualifier @DESTROYED(X.class) when a custom context is destroyed, where X is the scope type associated with the context. A suitable event payload should be chosen.`

The test can be found here:
https://github.com/jakartaee/faces/blob/4.0.1/tck/faces22/cdiInitDestroyEvent/src/test/java/ee/jakarta/tck/faces/test/javaee7/cdiinitdestroyevent/cdiinitdestroyevent/Issue2948IT.java#L101

For example, MyFaces fails to call this method within the application:

    public void observeFlowStart(@Observes @Initialized(FlowScoped.class) Flow currentFlow) {
        userBean.setInitFlowMessage("" + currentTimeMillis());
        userBean.setFlowId(currentFlow.getId());
    }