I recently upgraded from struts 2.0 to 2.1.7 and noticed that we are
now getting lots of warnings in the logs:
12:31:53,283 WARN [OgnlValueStack] Error setting expression
'button.save' with value '[Ljava.lang.String;@1683e9f'
ognl.OgnlException: target is null for setProperty(null, "save",
[Ljava
I just change the logging level.
log4j.properties:
# Struts OgnlUtil issues unimportant warnings
log4j.logger.com.opensymphony.xwork2.util.OgnlUtil=error
log4j.logger.com.opensymphony.xwork2.ognl.OgnlValueStack=error
On Fri, Jul 31, 2009 at 8:48 AM, Peter Phillips <
petergphill...@googlemail.com
On Fri, Jul 31, 2009 at 8:48 AM, Peter
Phillips wrote:
> I recently upgraded from struts 2.0 to 2.1.7 and noticed that we are
> now getting lots of warnings in the logs:
>
> 12:31:53,283 WARN [OgnlValueStack] Error setting expression
> 'button.save' with value '[Ljava.lang.String;@1683e9f'
> ognl.
>
>
> /sigh... This is one of the great debates of struts2 development. On
> one side you have a camp that wants to know any time a parameter is
> submitted that doesn't have a matching getter/setter on the action, on
> the other side, you have a group that doesn't want a bunch of errors
> in the l
Thanks for your help. I guess everyone has their own opinions on when
warnings etc. should appear in the logs and trying to keep everyone
happy is an impossible task.
After a bit more digging I think I can just implement my own version
of OgnlValueStackFactory (by setting the struts.valueStackFac
Not trying to hijack this thread, but I am from the latter camp Wes
described. I tried removing the logged errors as you suggested, but
it doesn't seem to work. If I move up to the broad
"com.opensymphony.xwork2" package it works, but this will remove too
much I fear. When I drill down to the ".
Burton Rhodes wrote:
Not trying to hijack this thread, but I am from the latter camp Wes
described. I tried removing the logged errors as you suggested, but
it doesn't seem to work. If I move up to the broad
"com.opensymphony.xwork2" package it works, but this will remove too
much I fear. When
Good eye (damn you drunk fingers) however, even with correct
spelling the errors are still logged. Could a different package/class
be throwing the error?
On Sat, Aug 1, 2009 at 8:57 PM, Dave Newton wrote:
> Burton Rhodes wrote:
>>
>> Not trying to hijack this thread, but I am from the latter
être sujets à la manipulation, nous ne pouvons accepter aucune responsabilité
pour le contenu fourni.
> Date: Sun, 2 Aug 2009 09:26:36 -0500
> Subject: Re: [S2] OgnlValueStack Error setting expression warnings after
> upgrade from struts 2 to struts 2.1.7
> From: burtonrho
Martin Gainty wrote:
a genuine bug..the prob is trying to hunt down the file as it seems to have
disappeared
notice the disconnect between com.opensymphony.xwork2.ognl classes and
ognl.ObjectPropertyAccessor;
here is 2.1.4 xwork class that actually references the non-existent base class
/***
Well... I ended up limiting log level on the object
"com.opensymphony.xwork2.ObjectFactory". This seemed to do the trick.
Not sure if that's the "right" solution though.
On Sun, Aug 2, 2009 at 10:40 AM, Dave Newton wrote:
> Martin Gainty wrote:
>>
>> a genuine bug..the prob is trying to hunt dow
11 matches
Mail list logo
