I just want to be sure.  Should code like the following work?  We have code 
like this all over the site.

<%@ taglib prefix="dsp" uri="/WEB-INF/dspjspELTaglib1_0.tld" %>
<%@ taglib prefix="tiles" uri="/WEB-INF/struts-tiles.tld" %>
<%@ taglib prefix="c" uri="/WEB-INF/c.tld" %>
<%@ taglib prefix="x" uri="/WEB-INF/x.tld" %>
<%@ page contentType="text/html; charset=UTF-8" %>
<tiles:insert definition="layouts.popup.2" flush="true">
        <tiles:put name="img" value="pop_offer_title.gif" type="string" />
        <tiles:put name="content" type="string">
        <dsp:page>
                <dsp:droplet name="/droplet/PageLookup" />
                <dsp:importbean bean="/atg/userprofiling/Profile" var="profile" 
/>
                <dsp:importbean bean="/atg/userprofiling/LoginStatus" 
var="status" />
                        
                        <tiles:insert definition="tiles.offer_image" 
flush="true">
                                        <tiles:put name="header"                
        value="pop_offer_title.gif" type="string" />
                                        <tiles:put name="img"                   
value="default_pop.jpg" type="string" />
                                        <tiles:put name="title"                 
        value="Some Title" type="string" />
                                        <tiles:put name="pad"                   
value="20" type="string" /> 
                                        <tiles:put name="content"       
type="string">Some content</tiles:put>
                                </tiles:insert>
                        </dsp:page>
                </tiles:put>
        </tiles:insert>

Thanks

-----Original Message-----
From: Antonio Petrelli [mailto:[email protected]] 
Sent: Thursday, August 13, 2009 3:19 AM
To: [email protected]
Subject: Re: Issues with content rendering in nested tiles

2009/8/12 Bobby Fincher <[email protected]>:
> This is the behaviour that I want to happen and I think it is correct.

You may think so, but we never wanted it, so it is definitely a side
effect. The "correct way" is to use an attribute of type string and
insert it in the template.

>  You can see in the included sample output that "Inside Tile" is displayed, 
> but you don't see "Inside nested tile" in the output. You can search for the 
> word "Inside" in the include attachment and you will see the statements:
>
> out.write("\tInside Tile\n");
> out.write("  \t\t\tInside nested tile\n");

In fact, the "bug" is that the string is rendered to the user, that
should not happen, not the opposite. IMO this is a minor bug, since if
you don't do it, nothing wrong happens. Notice that with "wrong" I
mean "the appearance of that string as a result".

Antonio

Reply via email to