struts-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Guillaume Carre (JIRA)" <>
Subject [jira] Commented: (WW-1798) erratic behaviour when trying to get objects from the valuestack with JSTL
Date Sat, 10 Mar 2007 12:29:51 GMT


Guillaume Carre commented on WW-1798:

Adding the filter org.apache.struts2.dispatcher.ActionContextCleanUp before the FilterDispatcher
solved the problem, but my jsp wasn't in a sitemesh decorator (from the javadoc, "ActionContextCleanUp
is a special filter designed to work with the FilterDispatcher and allow for easier integration
with SiteMesh").

So now I have the following filters in the following order:
- ActionContextCleanUp filter 
- SiteMesh filter 
- FilterDispatcher 

I didn't have the behaviour in Webwork 2.2.4. Any idea?

> erratic behaviour when trying to get objects from the valuestack with JSTL
> --------------------------------------------------------------------------
>                 Key: WW-1798
>                 URL:
>             Project: Struts 2
>          Issue Type: Bug
>          Components: Value Stack
>    Affects Versions: 2.0.6
>         Environment: Windows, Apache Tomcat 5.5.17
>            Reporter: Guillaume Carre
> In reference to the following User list entry:
> With a very simple test case(TestAction with a String test attribute, getter setter,
and a jsp result), there is an issue getting objects from the valuestack in a JSP with JSTL
(ww:property tag is always working).
> On the first call to the JSP (fresh new session), ${test}, which is supposed to look
for a "test" object in the valuestack, thanks to the StrutsRequestWrapper, returns nothing.
StrutsRequestWrapper is not even called.
> On the next calls it returns the good value from the valuestack.

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

View raw message