18:00
Betreff: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
t:container
t:body
/t:container
Later in use
t:parent
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 tawus.tapes...@gmail.com
An: Tapestry users users@tapestry.apache.org
Datum: 11.04.2011 18:00
Betreff:Re: Components communication with nested
:Re: Components communication with nested components
I am also using @Environmental but it is not availiable at all times. e.g.
when the nested component contains a form and that form is submitted... So
in order to deal with it I use @Persist, first time around and on form
submission I use
this
gives you some ideas.
g,
kris
Von:Taha Hafeez tawus.tapes...@gmail.com
An: Tapestry users users@tapestry.apache.org
Datum: 12.04.2011 12:24
Betreff:Re: Components communication with nested components
I am also using @Environmental but it is not availiable at all
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
;
}
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 archive at Nabble.com
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-users.832.n2.nabble.com/Components-communication-with-nested-components