struts-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Adam Hardy <>
Subject Re: Action-Redirect Parameter Problem
Date Sun, 01 Jun 2008 18:52:18 GMT
That issue is closed, although there is a comment left after it was closed 
suggesting that the issue is still a problem and that the bug should be re-opened.

I see this 'warning' from OGNL wherever I use Action-Redirect results with the 
latest struts2 version, and it's true that the stacktrace in the webserver log 
is distracting, but I don't find any problems with it like the last comment 

It's not clear why the poster of that comment didn't re-open the bug or create a 
new one if there is a real problem there.

Do you find problems with it still?

It seems to me that the issue should not have been changed from status open to 
resolved, rather it should have been changed from priority major to enhancement.

Also the poster of the last comment should have left more details with perhaps a 
patch or unit-test displaying his/her bug.


Mark Lester on 30/05/08 14:31, wrote:
> Thanks for the quick response. I don't think that is the problem
> because that directory is already clear plus I have only used the
> current version of struts2
> -----Original Message-----
> From: Owen Berry [] 
> Sent: Friday, May 30, 2008 9:24 AM
> To: Struts Users Mailing List
> Subject: Re: Action-Redirect Parameter Problem
> If you're using Maven, you should try clearing out your local Maven
> repository (rm -rf ~/.m2/repository) and try again ... I've had a few
> cases where I seemed to be using old versions of jars until I did
> this.
> On Fri, May 30, 2008 at 9:18 AM, Mark Lester <>
> wrote:
>> I followed the
>> To
> pass
>> parameters to an action
>> And it generates the exception
>> Caught OgnlException while setting property 'navigation' on type
>> 'org.apache.struts2.dispatcher.ServletActionRedirectResult'.
>> I looked the Exception up and I found a bug report for struts 2 at
>> The problem is that it says the issue is resolved as of version 2.08
>> but I am using 2.11 and I am still getting the warning.
>> Information regarding this issue would be very helpful.

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message