Hallo Yael,

I never really used contrib:table but I guess, this happens because the table uses the wrong link type for sorting, I guess the DirectLink, but am not really sure about that -
instead you should "convince" the table to use ActionLink -
this will make the page rerender (before rendering the page for output, also called rewinding) and the listener will be called during the iteration of the For, so each component will have its binding set.

I would guess that the contrib:Table should be able to do that given the right parameters.

Anyway, this is a case for Mind Bridge to tell...
Try posting again with something like: "changing contrib table sort links ActionLink instead of DirectLink" in the subject...

Hope that helps,
Cheers,
Ron




yamsterdamer wrote:
Hi Ron
I think you pretty much got it right.

For
|___Component
        |___Contrib Table

Step 1: the loop is rendering itself
2:  in the first iteration a component with current parameters and an id, let's 
say “myComp” is being created, and renders itself
3: in the second iteration the same component with the id “myComp” is given 
different parameters, and renders itself again
4: and so on in the next iterations
5: the loop ends. The index/ value are deleted, and so is “myComp”
6: the page is displayed
7: the user presses sort link on one column of one of the tables.
8: the sort link requests for the component “myComp” (why? In order to retrieve 
table parameters from it, I suppose)
9: the returned “myComp” is not initialized.
10: the table tries to get its parameters from “myComp”
11: null pointer exception

Very simple. Seems like a trivial thing to do, doesn’t it?


-------------------- m2f --------------------

Sent from www.TapestryForums.com

Read this topic online here: <<topic_link>>

http://www.tapestryforums.com/viewtopic.php?p=13315#13315

-------------------- m2f --------------------





---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to