Re: Components communication with nested components

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

Re: Components communication with nested components

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

Re: Components communication with nested components

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:

Re: Components communication with nested components

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:

Re: Components 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:04 PM, Christian Köberl < tapestry.christian

Re: Components communication with nested components

You could use parameters - Tapestry keeps them always in sync: public class Parent { // here Parent's state is bound to Child's state @Component(parameters = "state=state") private Child child; @Property private String state; } public class Child { @Parameter private String state;