You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@myfaces.apache.org by "Thomas Andraschko (Jira)" <de...@myfaces.apache.org> on 2023/01/17 15:20:00 UTC

[jira] [Commented] (MYFACES-4489) TCK: Spec3001IT: Abandon Flows

    [ https://issues.apache.org/jira/browse/MYFACES-4489?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17677803#comment-17677803 ] 

Thomas Andraschko commented on MYFACES-4489:
--------------------------------------------

[~volosied]can you take care of this? 

> TCK: Spec3001IT: Abandon Flows
> ------------------------------
>
>                 Key: MYFACES-4489
>                 URL: https://issues.apache.org/jira/browse/MYFACES-4489
>             Project: MyFaces Core
>          Issue Type: Bug
>    Affects Versions: 2.2.15, 2.3.10, 2.3-next-M7, 3.0.2, 4.0.0-RC2
>            Reporter: Volodymyr Siedlecki
>            Priority: Major
>
> This problem was brought up via [https://github.com/eclipse-ee4j/mojarra/issues/3001.] 
> My understanding, is that the you can leave a flow via a flow-return or flow-call node. However, the OP would like an easier way to exit flows without duplicating the flow returns / calls. OP says:  "It is unreasonable to add all of them in a flow definition as flow-returns." 
> The test is 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/Issue2997IT.java]
> The test verifies that  `[@PostConstruct|https://github.com/PostConstruct]` and and `[@PreDestroy`|https://github.com/DESTROYED] work correctly on beans which were used in the  abandoned flows.  This is where MyFaces fails.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)