That's more or less true. But, the page will actually contain the component.
So... MyPage.html: <div jwcid="@MyBorderComponent"> Here is some content that is specific to MyPage.html. </div> and in Border.html: <html jwcid="@Shell" title="Some Page"> <body jwcid="@Body"> <a href="#">This link will render on every page which uses the border component.</a> <!-- this is where the "Here is some content that is specific to MyPage.html" will appear. --> <div jwcid="@RenderBody"/> </body> </html> So... you can't directly include a page in a component. Rather, your page includes the components inside of it. Page is the top-level component. However, your border, by means of the @RenderBody, can/will render anything nested inside of it on the page. HTH. Robert Will Scheidegger wrote: > Hm... maybe I'm missing something, but as far as I know the border > component is the subcomponent although it is wrapped around the inner > component. The inner component is actually a subclass of BasePage > whereas the border component subclasses BaseComponent. At least this is > how I understood > http://jakarta.apache.org/tapestry/3.0.3/doc/ComponentReference/ > RenderBody.html. > > -Will > > On 02.08.2005, at 17:21, Jamie Orchard-Hays wrote: > >> I don't see how you could pass info from your contained component to >> your border component. It's easy to pass data from your page to a >> component on the page. How are you trying to pass data from the >> contained component to the border? >> >> Jamie >> >> >> On Aug 2, 2005, at 10:51 AM, Will Scheidegger wrote: >> >>> Thanks for the help. By "..wrapped around it" I meant: >>> >>> <span jwcid="@CRStandardPage" printView="ognl:printView" >>> languageKey="ognl:languageKey" pageKey="rental"> >>> ... my component >>> </span> >>> >>> As I said, I'm a newbie. If I understood correctly my CRStandardPage >>> component is called "Border" component, right? The CRStandardPage >>> component then contains a @RenderBody tag. Actually it contains two >>> @RenderBody tags because depending on the value of the "printView" >>> parameter either one or the other part of CRStandardPage is used. >>> >>> What else would you be interested in? I don't want to clutter the >>> list with pages of java, html and xml code. ;-) >>> >>> -Will >>> >>> On 02.08.2005, at 16:34, Jamie Orchard-Hays wrote: >>> >>> >>>> could you share some more code? What do you mean exactly by "a >>>> component with a border component wrapped around it"? >>>> >>>> Jamie >>>> >>>> >>>> On Aug 2, 2005, at 8:38 AM, Will Scheidegger wrote: >>>> >>>> >>>>> (Tapestry 3.0.3) Newbie alert! Could not find any solution in the >>>>> archive, so please bare with me: >>>>> >>>>> I've got a component with a border component wrapped around it. >>>>> Depending on a parameter passed from my component to it's border, >>>>> the border should display a navigation or should not: >>>>> >>>>> <parameter name="printView" type="boolean" direction="in"/> >>>>> >>>>> Now, I've tried to add two more parameters that should be set from >>>>> the component: >>>>> >>>>> <parameter name="languageKey" type="String" direction="in"/> >>>>> <parameter name="pageKey" type="String" direction="in"/> >>>>> >>>>> This had the following effect: >>>>> >>>>> a) when I don't set a "direction" attribute, the page displays >>>>> fine (as before), but the languageKey and pageKey values are not >>>>> set (of course) >>>>> b) as soon as I set the direction (in either or both of the new >>>>> parameters), the page crashes with the following exception message: >>>>> >>>>> 2005-08-02 14:14:25,373 ERROR BaseComponentTemplateLoader - >>>>> Template for component CRRentalList does not reference embedded >>>>> component: ConditionalPrintView. >>>>> >>>>> Even when I remove the ConditionalPrintView component from the >>>>> html I get the error message. Any ideas anyone? Thanks a bunch! >>>>> >>>>> -Will >>>>> >>>>> >>>>> -------------------------------------------------------------------- - >>>>> To unsubscribe, e-mail: [EMAIL PROTECTED] >>>>> For additional commands, e-mail: >>>>> [EMAIL PROTECTED] >>>>> >>>>> >>>>> >>>> >>>> >>>> --------------------------------------------------------------------- >>>> To unsubscribe, e-mail: [EMAIL PROTECTED] >>>> For additional commands, e-mail: [EMAIL PROTECTED] >>>> >>> >> >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: [EMAIL PROTECTED] >> For additional commands, e-mail: [EMAIL PROTECTED] >> > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
