Yes, it's really the job of the containing component to coordinate Foo and Bar.
See if this helps - it's a page which coordinates PersonList and PersonEditor:
http://jumpstart.doublenegative.com.au/jumpstart/examples/ajaxcomponentscrud
Geoff
On 09/05/2011, at 1:03 PM, Thiago H. de Paula Figueiredo wrote:
> On Sun, 08 May 2011 23:23:15 -0300, revprez <revp...@correlatesystems.com>
> wrote:
>
>> Say I have a component Foo that defines an action link on a zone rendered by
>> component Bar.
>
> Components are supposed to be self-contained, so having one component
> updating a zone inside another one is not recommended at all.
>
>> I receive an error noting that Foo does not define a component Bar.
>> My understanding is that neither components Foo nor Bar have any knowledge
>> of components rendered within one another (the attribute t:id) is not global.
>
> Correct. A t:id is local to the template at which it's declared.
>
>> I therefore infer that
>> component communication occurs only when they coincide within the same
>> immediate container and one component is child to the other. Is this
>> correct?
>
> No. I can see these kinds of communication in Tapestry:
>
> * Events (inner to outer)
> * Parameters (outer to inner)
> * Environment (outer to inner and inner to outer)
>
> --
> 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
