Obviously, I'm not clear on the distinction between EL and OGNL.
As a rule of thumb, would it be correct to say that OGNL is only valid
within Struts tags, and I should never expect OGNL interpolation in any
other context?
I thought that OGNL allowed me to get session attributes via the
$(#session.attributeId} syntax?
I'm able to do what I want with this:
<s:set name="companyId" value="#session.companyId" />
<tiles:insertDefinition name="${companyId}_compensation" />
But this doesn't quite make sense to me. Why does this work? Am I
using OGNL in the first line (#session.companyId) to set a JSP variable
which I can then access in the 2nd line? Is that "companyId" variable
placed on the value stack for access (it appears to be). The 2nd line
looks like OGNL as well to me, but maybe it's EL.
In this case, the company's tiles are really that different. And there
aren't many companies ;).
Wes
-----Original Message-----
From: Dave Newton [mailto:[EMAIL PROTECTED]
Sent: Tuesday, June 10, 2008 4:41 PM
To: Struts Users Mailing List
Subject: Re: Dynamically pulling in tile definitions based on session
attributes using OGNL
--- On Tue, 6/10/08, Gamble, Wesley (WG10) <[EMAIL PROTECTED]> wrote:
> <tiles:insertDefinition name="${#session.companyId}_compensation" />
You're still mixing JSP EL and OGNL. The link I supplied earlier might
still be handy (and I provided a direct link to your other question
regarding interceptor access to various servlet-oriented structures).
That aside, are company's tiles really so different that you need a
different tile for each company? (Rhetorical.) If so, I hope there
aren't very many companies :/
Dave
---------------------------------------------------------------------
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]
