Re: Tiles problem

[Mark Lowe]

all the puts should be have

type="string"
type="definition"
type="page"
depending on what it is.

For example if .portfolioLayout is a definition

<put name="content"   value=".portfolioLayout" type="definition" />

if its a "layout" then it should be in the definition tag as the 
content of the path attribute. The naming convention for layouts 
usually refers to those files that are layouts not definitions as such.

<definition name="main.base" path="/layouts/mainLayout.jsp">
...
I've used some of your names but i doubt they are that relevent to you.

<definition name="activity.detail" extends="main.base">
        <put name="title" value="Mellow World!!!" type="string" />
        <put name="content" value="portfolio.default" type="definition" />
        <put name="app-specific" value="/tiles/activityInfo.jsp" type="page" />
</definition>
When did all this .somename business start then, i've seen this else 
where. Looks  like dirty php to me :o)

On 2 Mar 2004, at 22:49, Anderson, James H [IT] wrote:

Maybe I didn't follow you, but I changed

    <definition name=".activity.detail" extends=".mainLayout">
      <put name="content"      value=".portfolioLayout"/>
      <put name="app-specific" value="/tiles/activityinfo.jsp"/>
    </definition>
to

    <definition name=".activity.detail" extends=".mainLayout">
      <put name="content"      value=".portfolioLayout"/>
      <put name="app-specific" value="/tiles/activityinfo.jsp" 
type="page"/>
    </definition>

and it didn't make any difference. What am I missing?

-----Original Message-----
From: Mark Lowe [mailto:[EMAIL PROTECTED]
Sent: Tuesday, March 02, 2004 4:40 PM
To: Struts Users Mailing List
Subject: Re: Tiles problem
<put name="foo" value="${bar}" type="string/definition/page" />

On 2 Mar 2004, at 22:15, Anderson, James H [IT] wrote:

There's something I'm not understanding :-( I've got the following
tiles definitions.
    <definition name=".mainLayout"
path="/tiles/layouts/mainLayout1.jsp">
      <put name="header"  value="/tiles/header.jsp"/>
      <put name="footer"  value="/tiles/footer.jsp"/>
      <put name="content" value="${content}"/>
<< variable for
substitution
    </definition>
    <definition name=".portfolioLayout"
path="/tiles/layouts/portfolioLayout.jsp">
      <put name ="marketdata" value=".marketdata"/>
      <put name ="userinput"  value=".userinput"/>
      <put name ="dataview"   value="/tiles/dataview.jsp"/>
    </definition>
    <definition name=".marketdata"
path="/tiles/layouts/marketdataLayout.jsp">
      <put name ="quotes"              value="/tiles/quotes.jsp"/>
      <put name ="smithbarneyresearch" value="/tiles/research.jsp"/>
      <put name ="marketwatch"         
value="/tiles/marketwatch.jsp"/>
    </definition>

    <definition name=".userinput"
path="/tiles/layouts/userinputLayout.jsp">
      <put name ="accountview"   value="/tiles/accountview.jsp"/>
      <put name ="app-specific"  value="${app-specific}"/>            <<
variable for substitution
    </definition>
and I want to create a new tile, substituting values for both 
variable:

    <definition name=".activity.detail" extends=".mainLayout">
      <put name="content"      value=".portfolioLayout"/>
      <put name="app-specific" value="/tiles/activityinfo.jsp"/>
    </definition>
But this doesn't work! The "content" variable is replaced as expected,
but the "app-specific" variable
is ignored and doesn't show up at all. It looks like the only tile for
which variable substitution
is supported is the one that's specified in the "extends"
attribute--not in any nested tile. Surely
there must be a way to get around this...
jim

---------------------------------------------------------------------
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]
---------------------------------------------------------------------
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]