[
https://issues.apache.org/jira/browse/BEEHIVE-1217?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Poornachandran updated BEEHIVE-1217:
------------------------------------
Attachment: testcase.zip
test case that shows pageflow stack corruption
> PageFlow stack gets corrupted when a request to nested pageflow ends
> prematurely
> --------------------------------------------------------------------------------
>
> Key: BEEHIVE-1217
> URL: https://issues.apache.org/jira/browse/BEEHIVE-1217
> Project: Beehive
> Issue Type: Bug
> Reporter: Poornachandran
> Attachments: testcase.zip
>
>
> Scenario:
> 1. Please compile the attached pageflows (unzip these files into the pageflow
> enabled webapp and compile).
> 2. Run Controller.java pageflow and invoke "Go to Nested" action. "Go to
> Nested" on NestedPageFlowController simulates delay (using loop) and it takes
> sometime to complete the action.
> 3. In the meantime, invoke "Done" action, this action belongs to the outer
> pageflow and displays a jsp page.
> Now, the PageFlowStack has the outer pageflow instance pushed, but the flow
> has actually come out of the nested pageflow. By repeating this process, page
> flow stack gets lot of invalid pageflow instances and after sometime,
> NullPointerException is thrown.
> By adding a validation code in FlowControllerFactory before creating the
> pageflow instance and before pushing the pageflow instance to the pageflow
> stack, I am able to overcome this issue. Please update, if this is correct
> approach.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
