That could work. BTW where is the advanced tiles PDF?
The other possibility I suppose is to have the default layout use an include that
specifies
<c:set var="titleKey"><tiles:getAsString name="titleKey"/></c:set>
<title><bean:message key="${titleKey}"/></title>
and it could be overriden in an extended tile definition to use
<title>${item.name}</title>
but my question on that is the efficiency of having two line JSPs that are included in
tiles.
What overhead is there in including a one or two line JSP?
Inheriting the TilesAction would require another intermediate class that would handle
the
default behaviour that I want the pages to have, and other actions would have to
override
this. If I did this, is there an appropriate method to do this default behaviour that
happens before the execute method?
Tim
> -----Original Message-----
> From: David Friedman [mailto:[EMAIL PROTECTED]
> Sent: 21 May 2004 23:41
> To: Struts Users Mailing List
> Subject: RE: Tiles and changing the title based on content
>
>
> Tim,
>
> Why not use a TilesAction (org.apache.struts.tiles.action package) and
> change/set tiles attributes using the putAttribute() method of the
> ComponentContext object. For more details, see the advances tiles PDF.
>
> -David
>
> -----Original Message-----
> From: Michael McGrady [mailto:[EMAIL PROTECTED]
> Sent: Friday, May 21, 2004 6:34 PM
> To: Struts Users Mailing List
> Cc: Struts Users Mailing List
> Subject: RE: Tiles and changing the title based on content
>
>
> I am not sure why this is a problem. All you have to do if you want part
> of the response object to be dynamic is put your dynamic value in the
> tile. Presumably you have some dynamic factor choosing the tiles content
> page. Just have that same factor decide what the value of the title
> is. There are lots of ways to introduce dynamic content. I don't see the
> problem.
>
> Michael
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
