You're right - casting componentResources#getPage works fine. > @InjectContainer does indeed inject the "parent" of the component. For > InnerLayout this is the page alright, but for Layout it's actually the > InnerLayout because Layout is contained in InnerLayout.
Could you clarify the meaning of 'contained'? From an html point of view (and I assume a component tree point of view), the hierarchy of my page is: Page +-- Layout +-- InnerLayout However, if "Layout is contained in InnerLayout" means "InnerLayout.tml references Layout.tml" then the 'reference' hierarchy is: Page +-- InnerLayout +-- Layout Should I be reading "InjectContainer" as "InjectTheComponentWhoseTemplateContainsTheContentsToBeInsertedAsBody"? If so, perhaps @InjectContentProvider would be more intuitive? Is there any documentation on @InjectContainer? I've searched the Tapestry site and Wiki but found nothing. -- View this message in context: http://www.nabble.com/-T5--Injecting-page-into-nested-layouts-tp19028771p19046282.html Sent from the Tapestry - User mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
