Hm. Ok, so, the issue is that you're running into problems when you try to sort the table, right? Because some parameters come back as null and your page throws an exception. I haven't started using tap 4 yet for a variety of reasons, however, what I've done in tap3 in situations like this goes something along the lines of:
1) Wrap the table(s) in a form component 2) Use contrib:FormTable instead of contrib:Table (this should be unnecessary for tap 4... table and form table have been merged, I believe) 3) place any objects necessary for "bootstrapping" the table just above the table using @Hidden components. Voila... things start playing nicely. The trick is that the links will submit the form, triggering a rewind of the entire form, including the @Hidden fields, which will restore whatever objects you need. In fact... depending on how you have things setup, I suspect that you could skip #3 in your case and things should still "Just work". Keep me posted on how things are going... Robert yamsterdamer wrote: > Which means, in other words, implementing the whole sort method myself, > how lovely. Instead of the table simplifying my life I ended up overriding > almost every component inside. > > Thanks a lot for all the help, I think I'm going to work without contrib's > table. > > Yael. > > > -------------------- m2f -------------------- Sent from www.TapestryForums.com Read this topic online here: <<topic_link>> http://www.tapestryforums.com/viewtopic.php?p=13448#13448 -------------------- m2f --------------------
