Robert, This does offer greater flexibility indeed.
Thanks for the tip! </Firas> -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Sent: Thursday, August 10, 2006 4:18 PM To: Tapestry users Subject: Re: @Block, accessing the caller's properties Note that "getInvoker" is a 4.x idiom. If you're using tapestry 3.x, you want the "getInserter()" method (deprecated in favor of getInvoker in 4.0). You can also do interesting things like: <div jwcid="@RenderBlock" block="ognl:block" informalParam1="ognl:foo"/> and then your block can do something like: blockComponent.getInvoker() (or getInserter() for 3.x).getBinding("informalParam1").getObject(); Which let's you pass a variety of things around, in interesting manners. (Eg: passing components to pages, passing "parameters" to pages, etc.) Robert > Check out Block's getInvoker() method. > Try > > blockComponent.getInvoker().getPage().getSomePageProperty() > > Regards, > Norbi > > Firas Adiler wrote: >> Hello, >> >> Can a Block-component access the page/component that's calling >> RenderBlock? >> >> Assume page C contains this call: jwcid="@RenderBlock" >> block="ognl:someBlock" >> >> Can someBlock access page C's properties? >> >> >> Thanks for your time! >> >> </Firas> >> >> >> --------------------------------------------------------------------- >> --- >> >> No virus found in this incoming message. >> Checked by AVG Free Edition. >> Version: 7.1.394 / Virus Database: 268.10.8/414 - Release Date: >> 2006.08.09. >> >> > > > --------------------------------------------------------------------- > 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]
