Lance, I think I'm encountering a similar issue with the textfields. I have a textfield nested in a ajaxformloop. When I create a new row the textfield gets the initial id of activityCode_a91bfdca926f. This is a required field, so when I leave it blank and try to save the form I get the serverside validation, but I do not get a highlighted field and that is because the id changed to activityCode_1. Now the next save, tapestry will continue to use activityCode_1 and highlight the field properly. Like you, I tried providing my own id with clientId and it failed to work properly. I'm thinking there is a bug with how tapestry generates the initial id before saving.
Anybody have any thoughts? On Thu, May 15, 2014 at 6:43 AM, Lance Java <lance.j...@googlemail.com>wrote: > https://issues.apache.org/jira/browse/TAP5-2331 > -- George Christman www.CarDaddy.com P.O. Box 735 Johnstown, New York
