Seems like client-side ID assignment is causing a lot of issues to new tapestry users including me. AFAIK, the purpose of having Tapestry generate client-side IDs, is to maintain a healthy application with unique client\server side IDs.
So I have a suggestion.. Why don't Tapestry allow developers to *optionally* assign client-side IDs to components before rendering them ? With every iteration in a loop and with every page render... If I open a Jira for this suggestion, will there be enough votes for the developers to consider it ? *---------------------* *Muhammad Gelbana* http://www.linkedin.com/in/mgelbana
