Yeah, I read that, but in the scenario with Appfuse there are no
struts tags. The <s:set /> is not necessary to make displayTag see
the collection in the current version of Appfuse/Struts and I can't
figure out how. DisplayTag is going to look in the request scope for
the variable "list" for <display:table name="list"... , but Struts is
going to put that variable on the value stack.
Some possabilities:
* Struts pre-2.1 has a filter that makes the value stack values
available via the request scope as well for JSTL style code -- I
vaguely remember something like that in the Webwork days -- and that
is no longer there
* DisplayTag is able to somehow reach out past the request scope and
look in Struts' value stack for the List. And with the new version of
Struts, that code is broken???
I see your point on how its related, but that security warning is more
about the use of struts tags rather than OGNL value stack objects in
3rd party JSP tag libs.
-D
On May 10, 2008, at 7:16 PM, Matt Raible wrote:
This might be related to the following:
http://struts.apache.org/2.x/docs/s2-001.html
In other words, I believe they stopped processing JSP EL expressions
${} in Struts tags.
Matt
On Sat, May 10, 2008 at 8:05 PM, Dustin Pearce <[EMAIL PROTECTED]
> wrote:
So, we have discussed this topic in the past, but I wanted to bring
it up
again because I am still not sure why.....
When I use Appfuse 2.x and Struts2, I can just name my displayTag
table to a
getter on my Action and somehow that collection (on the OGNL value
stack)
finds its way to displayTag. My memory of working with Webwork is
always
having to do a <ww:set /> in order to move the OGNL variable into
page or
request scope for DisplayTag to grab it. I don't remember when I
stopped
having to do that <s:set /> call, but now with Struts 2.1.x, I have
to make
the <s:set /> call again for displayTag to see the collection.
Does anyone know how DisplayTag can see the collection without a
<s:set />
in the current Struts2 basic build of Appfuse (Struts 2.0.11.1,
Appfuse
2.0.1)?
-Dusty
That means you Rob.... ;-)
---------------------------------------------------------------------
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]
