Hi Kristian
Thanks for your hints.
I just wanted to have control over my component and they appeared to be
null in my debugger at any stages of the rendering process.
My fault was to not declare them private. Since I declared them private
the problem was fixed.
Michael.
Kristian Marinkovic a écrit :
Hi Michael,
Thiago is right, first make the fields private... you should have
some warnings in your console tough.
then you have to decide how you want to add components:
you can add components to a page by declaring them
in the template like you did (then you dont need to declare
them in your page/component class):
<t:pagelink>....</t:pagelink>
or by using invisible instrumentation by adding an t:id attribute
to one of your HTML elements that matches
a field in the page class/componen class with a @Component
annotation with the same name of with a id parameter:
<a t:id="page">...</a>
// id matches field name
@Component
private PageLink page
----
// id in template does not match field name
@Component(id="page")
private PageLink pageToEdit
g,
kris
"Thiago HP" <[EMAIL PROTECTED]>
06.12.2007 12:31
Bitte antworten an
"Tapestry users" <users@tapestry.apache.org>
An
"Tapestry users" <users@tapestry.apache.org>
Kopie
Thema
Re: Can't get component inside a component
Try replacing
@Component(id="couleur1")
Couleur couleur1;
by
@Component(id="couleur1")
private Couleur couleur1;
AFAIK, @Component and @Inject only works in private fields.
Thiago
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
--
Michael Courcy
http://courcy.blogspot.com
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
