[
https://issues.apache.org/jira/browse/MYFACES-4489?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Volodymyr Siedlecki resolved MYFACES-4489.
------------------------------------------
Resolution: Later
Challenge accepted – [https://github.com/jakartaee/faces/issues/1734]
Will need more information from the spec to determine when a flow should be
abandoned.
> 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
> Assignee: 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)
