Re: [Tapestry-developer] Action vs. Direct services

[Howard M. Lewis Ship]

An example is the Portal application (in the tutorial).   The content that's displayed inside the portlets comes from other pages.  Tapestry has mechanisms to support this ... underlying it all is the fact that in Tapestry, renderring involves visiting many components and invoking render() on them; it does not necessarily mean that all the components live on the same page.  Using the RenderBlock component allows the contents of a Block to be rendered .... and if the Block comes from a different page in the applicaiton, so be it!  The action and direct services recognize this and adjust URLs to identify both the render page and the page containing the component ... just like magic!   You can use this form portal-like applications, or even do a bit of "themeing".   The limitation, though, is that the pages and components do in fact exist.  Bypassing this limitation (to brew up pages and components on the fly) is possible, but much more involved. ----- Original Message ----- From: Dave Roberts To: Mind Bridge ; Howard M. Lewis Ship ; [EMAIL PROTECTED] Sent: Wednesday, January 01, 2003 11:55 AM Subject: Re: [Tapestry-developer] Action vs. Direct services Yikes! This must be in the advanced class... ;-) I'm not even sure I know what that means... Using the Action service is often necessary when doing polymorphic rendering via RenderBlock or Delegator, especially when the inserted block/component is located on a different page.