yes i did use idPath for the hidden field.
but i'm using tapestry 4.0.2 - could that be the reason i'm seeing different
results than you are?
On 11/5/06, Patrick Moore <[EMAIL PROTECTED]> wrote:
did you assign the hidden field's id using idPath?
Also I am using the 4.1.1 SVN build.
I am having some success with this method (borrowed from another's
email) in finding the unique ids but I haven't throughly tested it
yet:
public String getUniqueId(AbstractComponent component) {
return getRequestCycle().getUniqueId(
TapestryUtils.convertTapestryIdToNMToken(component.getIdPath()));
}
Hopefully there is a better solution soon!
-Pat
