Not sure if this is a tree2 specific problem, I can just see that for some reason the behaviour seems to have changed  in my app when I switch to 20050822. Yes the actionListener is called in the APPLY_REQUEST_VALUES(2) phase, and the repopulation is done before that (which means that when I click on the commandLink) the data I retrieve is wrong. The commandLink behave normally outside of the tree. The dataTable is generated dynamically (in fact I generate n datatables dynamically), and at the moment contains outputText and commandLinks.

I am really puzzled...

On 8/25/05, [EMAIL PROTECTED] < [EMAIL PROTECTED]> wrote:

Hmm, strange. Are you sure that this is a tree2 specific problem? AFAIK the recent changes in the tree2 should not influence the behaviour of a commandLink.
Is the actionListener called at all? Can you determine the phase in which this happens? Does the commandLink behave normally when it is outside of the tree?

Do you use input components to display your data (in the dataTable)?

[EMAIL PROTECTED] schrieb am 23.08.2005 15:05:18:


> Hi,
>
> Just got the 20050822 build and I have problems with my app (I did
> not have this problem with the 20050802 build). The problem is as
> follows. I have a tree2 where each item is a commandLink (with
> immediate set to true) with an actionListener. A click on a tree
> item should trigger the repopulation of a dataTable as well as the
> update of values in other components. Until today this all worked as
> the actionListener was triggered before the repopulation phase.
> However with this new build it looks like the immediate attribute is
> not taken into account, i.e. the repopulation phase in my app is
> triggered before the event handling....
>
> Is that a bug or am I doing something wrong?
>
> Thanks for your help,
>
> Emmanuel

Reply via email to