Thanks for clearing this config option.
But the error does not go away with DevMode set to false.
Am Donnerstag, 1. März 2007 schrieb Ted Husted:
> In DevMode, the framework logs a number of extra warnings. In this
> case, a control is being submitted that doesn't have a corresponding
> property.
In DevMode, the framework logs a number of extra warnings. In this
case, a control is being submitted that doesn't have a corresponding
property. This might be OK (and probably is), but in DevMode, the
framework nags us just to be sure.
In production or late development, always set DevMode to fal
Am Mittwoch, 28. Februar 2007 schrieb Ted Husted:
> Is DevMode set to false?
no, its set to true.
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
> I do.
> It looks vicious, but is pretty harmless.
> You could wipe it out of your logs by setting the class that throws it to
> only log ERROR and greater.
I will do it for development - but I hope this gets fixed. Exceptions are the
slowest parts in the jvm as far as I know. Performance cant b
Is DevMode set to false?
...
-Ted.
On 2/27/07, Piero Sartini <[EMAIL PROTECTED]> wrote:
upgraded to 2.0.6 - now the error below is thrown when accessing an Action
with validators.
dont know if it is important, but ajax-validation is enabled and the
annotation looks like this:
--- code -
-
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>
>
--
View this message in context:
http://www.nabble.com/Problem-with-2.0.6-tf3300246.html#a92077
Am Dienstag, 27. Februar 2007 schrieb cilquirm:
> I see errors like that on occasion ( mine is with the JSONResult type and
> the location property ), but they've always been warnings.
>
> Is yours logged at the ERROR level?
they are logged at WARNING level. Should I just ignore them? I do not fee
ava:86)
> at
> com.opensymphony.xwork2.DefaultActionInvocation$2.doProfiling(DefaultActionInvocation.java:219)
>
>
> ....
>
> -----
> To unsubscribe,
upgraded to 2.0.6 - now the error below is thrown when accessing an Action
with validators.
dont know if it is important, but ajax-validation is enabled and the
annotation looks like this:
--- code ---
@RequiredStringValidator(message = "Login is required", key
= "error.loginname.missing")
9 matches
Mail list logo