-
1. Re: Last row in < rich:tree > not updatable
jeffzzang Nov 7, 2007 12:49 PM (in response to jeffzzang)Update:
After some more debugging, this is what I found
When the value for the last leaf node is being submitted, the following happens during the lifecycle:
-----------------------------------------------
After Restore View (1):
Submitted value is correct
Value is null
isLocalValueSet is false
After Apply Request Values (2)
Submitted value is correct
Value is null
isLocalValueSet is false
After Process Validations (3)
Submitted Value is correct
Value is still null
isLocalValueSet is false
-------------------------------------------
When I press Done on a non-last-leaf node, the Value of the component gets set after process validations, unlike what we see above:
After Process Validations (3)
Submitted Value is null
Value is set and correct
isLocalValueSet is true
I've also found that this anomoly happens if there are tree levels after the last leaf node that do not have leaves in them. For example:
-Level One 1
-Level Two 1
-Level One 2
-Level Two 1
-Level Two 2 (Won't get updated properly)
-Level One 3
-Level One 4
Notice Level One 3 and Level One 4 have no leaf nodes under them. If I populate them with leaf nodes, however, then the last leaf node (which would be under Level One 4) is updated correctly. Anyone have any ideas? -
2. Re: Last row in < rich:tree > not updatable
jeffzzang Nov 8, 2007 4:29 PM (in response to jeffzzang)Resolution:
I had to wrap the whole thing in an a4j:region and then instead of binding to #{treeAbstracts.paperNumber}, I had to bind it to a bean in my controller. So weird.