In my opinion, @InjectContainer is a bit fragile. I think you're much
better off using the Environment or a component parameter. Let's consider a
future case where you want to render the child component in a loop (or
maybe an 'if' component). In this case the parent will be the loop/if and
it won't
@InjectContainer is the way to go.
Have a 10 minute read on the OSI 7 Layer model for data communications as
a reference point if you need one.
e.g. Each layer knows the layer above and below it, like parent and child.
It's a proven mechanism of keeping things "encapsulated" and if you have
OK,
I'm not experienced in the InjectContainer annotation, but it seems that one
have to write it on each embedded component?
I have to figure out.
The original intention was that the component's container must not be mentioned
anywhere, even not in an annotation.
Von Samsung Mobile gesendet
Hello,
I have some strange behaviour going on in my Tapestry app. On a page using
jquery tabs, some UI elements from different parts of the page pop up for a
millisecond when I change the active tab. They pop up outside of the tabs.
What could be the problem? Should I post my tab configuration?
