Hi Thiago,
I see what you mean, but I did not want to manipulate the container
component, but only wanted to look up if a certain (self written)
annotation is present on it and then let the embedded component to do
certain things.
According to my opinion that would be a nice way to get information
about the container component without knowing it in the embedded
component and without make the unnecessary work for other developers to
write one more parameter besides all other ones.
I can not see why an additional parameter is the recommended way here.
Greetings, Eric
Am 13.02.2015 20:11, schrieb Thiago H de Paula Figueiredo:
On Fri, 13 Feb 2015 17:01:06 -0200, Erich Gormann
<e.gorm...@gormann.de> wrote:
Hello Daniel,
I wanted to avoid an additional parameter, because there are already
some parameters and if there would another way to manage it, this
would be better.
You're much better off with another parameter then accessing the
parent component directly.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org
For additional commands, e-mail: users-h...@tapestry.apache.org
