- The Grid itself renders the client id only when inplace is set true, is there a specific reason why its id is omitted on inplace false? (also see https://issues.apache.org/jira/browse/TAP5-1569)
- Using the Grid component inside a Loop leads to erroneous sorting behavior. Example: 1 Grid, used inside a loop leads to 3 rendered grids on the client. Changing the sort of one of them, sorts all grids since the sorting links don't have a clue which one to sort. Even granted that we have a GridModel for each iterable (i have to admit i haven't tested it yet) won't change that issue, does it?! Am I getting something wrong or is the tapestry grid component simply not intended to be used inside a loop? Thanks in advance for any hints!
