I resolved this adding zones dynamically in the during the
setupRender. It looks something like this:
_clientBehaviorSupport.addZone(_assignedClientId, "show", "show");
Link link = _componentResources.createEventLink(EventConstants.ACTION,
_design.getId(), _assignedClientId);
_clientBehaviorSupport.linkZone(_linkClientId, _assignedClientId,
writer.element("a", "href", link.toURI(), "id", _linkClientId);
On Mon, Aug 17, 2009 at 6:51 PM, Juan E. Maya<maya.j...@gmail.com> wrote:
> Mohan! Did u manage to resolve this problem? How do u do this?
>
> On Fri, Jun 20, 2008 at 11:47 PM, Mohan
> Zhang<mohanzhang+nab...@gmail.com> wrote:
>>
>> Anyone? This problem is bugging me a lot because it seems like it would be a
>> common usecase...
>>
>>
>>
>> Mohan Zhang wrote:
>>>
>>> Hi everyone,
>>>
>>> I've been reading the mailing list for a while now and have only seen one
>>> post on this topic, which unfortunately did not clarify things for me. I
>>> know this question has probably been asked a few times either indirectly
>>> or whatnot, but I'm curious to find out if the problem is something very
>>> fundamental in my understanding, or whether this is just a technical
>>> issue.
>>>
>>> The question is this: if I have a component which has a zone and an
>>> actionlink (or alternatively an eventlink) which loads a block into the
>>> zone, what's the right way to do this? I've tried using clientId tricks,
>>> but this has never been successful for me.
>>>
>>> So to summarize, I have a component which declares its own zone, block,
>>> and actionlink. I want this actionlink to load the block into the zone for
>>> this component. Now I have a page which has say four of these components
>>> and I want each actionlink to affect the appropriate zone. What's the
>>> right way to do this?
>>>
>>
>> --
>> View this message in context:
>> http://www.nabble.com/Zones-and-blocks-inside-components-tp17993683p18037943.html
>> Sent from the Tapestry - User mailing list archive at Nabble.com.
>>
>>
>> ---------------------------------------------------------------------
>> 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
