Thiago, I couldn't see the wood for the trees on this one - I was looking for a problem within the component I had created, but all the IDs in the various areas were explicitly bound in there - the problem was where the component was included in a page, the ID was not bound:
<t:componenName componentZoneId ="zone_3"/> instead of: <t:componenName componentZoneId ="zone_3" t:id="zone_3"/> ... so Tapestry was generating the (usually) unique IDs. Your comment below I think is highlighting the same issue but on the generated html rather than the tml markup. Thanks for your help. Regards, Jim. -----Original Message----- From: Thiago H. de Paula Figueiredo [mailto:thiag...@gmail.com] Sent: 05 May 2010 22:37 To: Tapestry users Subject: Re: Zone ID issue On Wed, 05 May 2010 17:59:01 -0300, Jim O'Callaghan <jc1000...@yahoo.co.uk> wrote: > <div class="t-zone" > zone="org.apache.tapestry5.corelib.components.z...@278a2a" id="zone_1"> You should pass a String containing the id of the zone to be updated, not the zone itself. -- 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
