g the components to my data objects. i hope this
> gives you some ideas.
>
> g,
> kris
>
>
>
> Von:Taha Hafeez
> An: Tapestry users
> Datum: 12.04.2011 12:24
> Betreff:Re: Components communication with nested components
>
>
>
> I am also usi
service interface. this way i can reload the data whenever i need it
lazily without coupling the components to my data objects. i hope this
gives you some ideas.
g,
kris
Von:Taha Hafeez
An: Tapestry users
Datum: 12.04.2011 12:24
Betreff:Re: Components communication with nested
that acts as the model that the components can use
> to pull data from it. the service interface acts as the contract between
> component and model
>
> g,
> kris
>
>
>
> Von:Taha Hafeez
> An: Tapestry users
> Datum: 11.04.2011 18:00
> Betreff:
nents communication with nested components
But my problem is parent does not have any knowledge of the child. Child
is
either contained in the body somewhere or in an override block
e.g
Parent
Later in use
so, parameters is not an option
regards
Taha
On Mon, Apr 11, 2011 at 9:
roperty
> private String state;
> }
>
> public class Child
> {
> @Parameter
> private String state;
> }
>
> see also http://tapestry.apache.org/component-parameters.html
>
> --
> Chris
>
> --
> View this message in context:
> http://tapestry-us
private String state;
}
see also http://tapestry.apache.org/component-parameters.html
--
Chris
--
View this message in context:
http://tapestry-users.832.n2.nabble.com/Components-communication-with-nested-components-tp6261431p6261909.html
Sent from the Tapestry Users mailing list a
Hi
I have at times come across cases where I have a component which has to
communicate with its nested components. For that I use Environment and push
the context at setupRender(). That works as long as the internal component
does not contain a form. If it contains a form, at the time of submissio
