[ http://issues.apache.org/jira/browse/BEEHIVE-760?page=all ]
Carlin Rogers updated BEEHIVE-760:
----------------------------------
Fix Version: TBD
(was: V1)
Changing this to TBD fix version. I'll look at this today
to evaluate and determine the risk involved with a V1 fix.
Otherwise, based on where we are before the milestone, I
think this one will have to go in the next release.
Other thoughts?
> selected tree item getting set after the selectionAction is run
> ---------------------------------------------------------------
>
> Key: BEEHIVE-760
> URL: http://issues.apache.org/jira/browse/BEEHIVE-760
> Project: Beehive
> Type: Bug
> Components: NetUI
> Versions: V1Alpha, V1Beta
> Reporter: Krista Baker
> Assignee: Carlin Rogers
> Fix For: TBD
> Attachments: Controller.jpf, index.jsp
>
> TreeRootElement getSelectedNode() and TreeHelpers
> findSelectedNode(TreeElement root) are both a selection item behind the
> currently selected item.
> Example tree:
> Item0
> Item0.0
> JPF code snippet:
> TreeRootElement myTree;
> TreeHelpers myHelper;
> @Jpf.Action(forwards = {
> @Jpf.Forward(name = "success",
> navigateTo=Jpf.NavigateTo.currentPage)
> })
> protected Forward selectionAction()
> {
> TreeElement selected = myHelper.findSelected(myTree);
> System.out.println("SELECTED: " + selected.getName());
> return new Forward("success");
> }
> Repro steps with above snippets:
> 1) If I click on Item0, the println is null and an error/warning is given
> 2) If I then click on Item0.0, the following will be printed:
> SELECTED: 0
> 3) If I click on Item0.0 again, the following will be printed:
> SELECTED: 0.0
> Continue clicking and you will notice that the printed out selectedItem from
> the selection action is always one selection behind what was actually clicked.
--
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
