I considered putting the Tile Controller on each Ad Tile that would collect Ad codes to expose to in the request, which works, except that each Tile is rendered and flushed to the browser one at a time, so by the time the last Ad is processed, the header (which contains the Ad engine code) has already been sent to the browser. Ideally, we'd be able to inspect each Tile that WILL be loaded and then put a string of Ad codes in the request before the page is rendered so the Ad Engine code in the header will have a complete list of all the Ads to be rendered on the page.
-Ryan -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Antonio Petrelli Sent: Tuesday, September 30, 2008 12:04 PM To: Struts Users Mailing List Subject: Re: Inspect Tile Definitions 2008/9/30 Shelley, Ryan <[EMAIL PROTECTED]>: > Interesting! Is there a URL to some documentation or examples or are > there any examples of Tile Controllers in any of the packages? The only thing that I can find is this: http://www.theserverside.com/tt/articles/article.tss?l=Tiles101 > So in theory, if we put a custom Tile Controller on the primary Tile > definition, that Controller class could inspect down into the Tile tree > for that view and set page-level values that could be accessed when the > JSP is rendered? Not exactly, it could inspect attributes that you put in, it won't inspect JSP pages. Antonio --------------------------------------------------------------------- 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]
