On Fri, 07 Dec 2012 10:51:44 -0200, captain_rhino
wrote:
Embedded components
It's a little weird to talk in Tapestry about embedded components because
all components can be used inside another component and pages are 99% the
same as components.
How can I pass the Text field component
er.Welcome (or a super-class of Welcome), but are not
> present in the component template
> (classpath:com/axa/cao/pages/partner/Welcome.tml).
>
> How can I pass the Text field component to the SimpleTextField Component to
> avoid the above error or is there a different approach I sho
the SimpleTextField Component to
avoid the above error or is there a different approach I should be taking?
Thanks in advance.
--
View this message in context:
http://tapestry.1045711.n5.nabble.com/T5-Embedded-Components-tp5718541.html
Sent from the Tapestry - U
You can cast a component to type org.apache.tapestry.runtime.Component
(this interface is added to component classes at runtime). You can
than access the component's ComponentResources, including embedded
components.
This is not advised; it is possible (in much the way you can use
reflection to
hi,
lets assume I have a root component with its html template. one of
components used in a template contains a component that interests me the
most. is it possible to get this embedded component from the root one? I
mean, is it generally possible to any component with allocated id from the
"root"
