On Fri, 13 Feb 2015 17:26:25 -0200, Erich Gormann
wrote:
Hi Thiago,
Hi!
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
One last comment: you mentioned self-written component. For Tapestry,
there's absolutely no distinction at all at the components provided
out-of-the-box and the components you write. All components, regardless of
origin, are treated and work the same.
--
Thiago H. de Paula Figueiredo
Tapest
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 infor
On Fri, 13 Feb 2015 17:01:06 -0200, Erich Gormann
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 th
On Fri, 13 Feb 2015 16:44:52 -0200, Poggenpohl, Daniel
wrote:
Hello,
why don't you try @InjectContainer? Or give the necessary information
via parameters to the inner component?
Yep, an @InjectContainer private Object parentComponent; field will give
you the parent component. You can ch
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.
I'll try the service you proposed, thanks for your answer!
Greetings, Eric
Am 13.02.2015 19:44, schrieb Poggenpohl, Daniel:
Hello,
why don't you try @InjectContainer? Or give the necessary information via
parameters to the inner component?
Regards,
Daniel Poggenpohl
Von: Erich Gormann [e.gorm...@gormann.de]
Gesendet: Freitag, 13. Februar 2015 18:51
An: Tapestry users
Betreff: H
Hi all,
seems to be a simple task, but I did not manage it right now.
I'm working with a self written component. Inside the code of this
component I want to retrieve information about the outer component
(container), my component is currently used in.
I tried the service ComponentSource, but
