Ciao Marcello,
Yep, it is ugly but you have to set it, I am still trying to figure out
why. So far I only know (by using <s:debug/> and
<%=request.getParameterMap().toString()%> that:
- The ValueStack contains all the request parameters expected by the JSP
i.e. the users List exposed from UserAction
- The request parameters Map is empty!
<%=request.getParameterMap().toString()%> outputs {}
I have been already working with Struts 2.1.x separate from AppFuse and
had no problems fetching ValueStack elements made available via request
onto displaytag directly with no set. I think that AppFuse is
manipulating the request somewhere e.g. BaseAction low level uses and
exposes the HttpServletRequest or in the Filters resulting in the
request being emptied somehow, just don't know where it is happening yet.
Saluti,
Giovanni
Marcello Teodori wrote:
Hi Giovanni,
thanks for sharing this, I'm applying it almost successfully. I've found
that whenever you use variables from the OGNL stack, you have to explicitly
set them in the request scope using <s:set.. to make them visibile in JSTL
EL. Don't know why this has changed from 2.0 to 2.1, I got the hint as I saw
that, for using displaytag, you did a <s:set before, but that is required
also on the single element edit pages.
Another problem I've found is that the actionName!method syntax is not
supported anymore for <s:form (it is used in the file upload page) you have
to add the method name in <s:submit
--m
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
