[
http://issues.apache.org/jira/browse/BEEHIVE-566?page=comments#action_63861 ]
John Rohrlich commented on BEEHIVE-566:
---------------------------------------
The repro is pretty self explanatory.
- Edit the build to point to your beehive/ant directory.
- import runtime
- build and deploy
- click on the anchor on the first page to get to the repro pageflow
- change the menus and radio buttons
- try each of the submit buttons
- one submit button executes the action in the backing file and returns null
- the other two buttons call actions in the backing file that raise page
flow actions that forward to the current page (one button calls an action that
passes a form bean and the other doesn't pass the bean)
- you'll see that in the cases where actions are raised the UI values revert
> The JSF UI Components values are reverting when using NavigateTo.currentPage
> ----------------------------------------------------------------------------
>
> Key: BEEHIVE-566
> URL: http://issues.apache.org/jira/browse/BEEHIVE-566
> Project: Beehive
> Type: Bug
> Components: NetUI
> Versions: V1
> Reporter: John Rohrlich
> Priority: Critical
> Attachments: reproOne.zip
>
> The JSF UI Components values are reverting when using NavigateTo.currentPage.
> When a JSF command is handled by a command handler in the backing file and
> the handler returns null (i.e. stay on page) the input elements in the form
> all retain the values set by the user. This is the expected behavior.
> Raising an action from the command handler and returning to the same page via
> Jpf.NavigateTo.currentPage should have the same behavior but it does not. In
> the later case the values in the form input components are reverting to their
> original values.
> A repro is attached
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
