You can try using a different method for finding the form. If you
know it's the only form in the zone you can use
Or give the zone a fixed client id (id parameter) instead of letting
Tapestry do that.
I'm not in front of a computer right now so I can't verify this, but I
don't think this affects the id's of other elements in the zone, does
it? I believe we are looking for the form element in the zone, which
as far as I can tell, from looking through javadoc on my phone, does
not have a way to keep it's id...
-- Josh
On May 28, 2010, at 8:52 AM, "Thiago H. de Paula Figueiredo" <thiag...@gmail.com
> wrote:
On Fri, 28 May 2010 12:22:10 -0300, Josh Canfield <joshcanfi...@gmail.com
> wrote:
When elements are loaded into a zone their id's get modified to
ensure they are still unique in the page.
You can try using a different method for finding the form. If you
know it's the only form in the zone you can use
Or give the zone a fixed client id (id parameter) instead of letting
Tapestry do that.
--
Thiago H. de Paula Figueiredo
Independent Java, Apache Tapestry 5 and Hibernate consultant,
developer, and instructor
Owner, Ars Machina Tecnologia da Informação Ltda.
http://www.arsmachina.com.br
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org
For additional commands, e-mail: users-h...@tapestry.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org
For additional commands, e-mail: users-h...@tapestry.apache.org
