According to http://struts.apache.org/2.0.11.1/docs/ognl-basics.html
"Struts 2 places request parameters and request, session, and
application attributes on the OGNL stack." So, you'd think you could
just request the attribute and it would search the stack for the
value, but I agree that I haven't seen this behavior work in practice.
#attr doesn't sound like it will work in your case since it only
searches the old four scopes, and never searches the value stack.
Your best bet might be to use the old JSP EL and let the, aptly named,
request doohickey check the value stack for you.
(*Chris*)
On Tue, Jun 24, 2008 at 3:19 PM, Brad A Cupit <[EMAIL PROTECTED]> wrote:
> Musachy Barroso wrote:
>> "#attr" does something similar:
>
> right, but it's kind of yucky in the sense that each of these objects
> needs a block like this:
>
> <s:if test="%{myObject == null}">
> <s:set name="myObject" value="%{#session.myObject}" />
> </s:if>
> <s:else>
> <s:set name="myObject" value="%{myObject}" />
> </s:else>
>
> and then I change use of it from:
> <s:label value="%{myObject.property}" />
>
> to:
> <s:label value="%{#myObject.property}" />
>
> I can live with that, but it seems like a step backward. JSP EL could
> automatically look in the session, but now I have to explicitly state
> that it's in the session.
>
> Maybe I'm in the minority here...
>
> Brad Cupit
> Louisiana State University - UIS
>
>
> ---------------------------------------------------------------------
> 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]
