I don't think this could work;  t:tree2 doesn't know anything about
the tr:table, so it doesn't know to save and restore the stamp
state on its behalf.  For now, I think you'd have to use pairs:  tr:table
with tr:tree, t:tree2 with t:table.  Once out of incubator, coming
up with a more generic strategy so that all of the MyFaces iteration
components can contain all of the components would be a
very Good Thing.

-- Adam



On 9/4/06, Jeantine Mankelow <[EMAIL PROTECTED]> wrote:

We are trying to convert all our tables from tomahawk tables to
af:tables to get the ppr functionality.  On one of our pages there is a
table which, amongst other things, is inside a tree2 component.  While
everything renders fine, if there is more than one table inside the tree
we are not able to save changes to the any table but the last one.  From
spending some time in the debugger I can see that  the apply request
phase  looks fine, i.e I can see the new value  set as the submitted
value, however when the stamp state is restored in the validation phase
it is set to the data from the last table.  Is there possibly something
I am doing wrong or should I log a bug?

Jeantine

Reply via email to