> I didn't understand much of the problem you're tring to solve, but the
> @InjectContainer annotation can help you: it allows a component to inject
> the parent component. Something like this, in a child component class:
>
> @InjectContainer
> private ParentComponent parentComponent;
Thank you.. unfortunately it does not solve my problem but this is about my
misunderstanding of how tapestry is doing things. After some more reading I
now do know about "static structure, dynamic behaviour".
Now I am trying to find out how a "portal-like" profile page could be
implemented with tapestry. I have several "portlets" defined as components and
want to arrange them on one page - but the order should be determined at
runtime (coming from the db)...
Piero
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org
For additional commands, e-mail: users-h...@tapestry.apache.org
