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<newton.d...@yahoo.com> wrote: > 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 I drill down to the "....xwork2.ogln" package the >> error is logged. What am I missing? >> >> <!-- This successfully removes the logged errors, but is too broad! --> >> <category name="com.opensymphony.xwork2" additivity="true"> >> <priority value="FATAL"/> >> </category> >> >> <!-- This DOES NOT remove the logged errors, one package down --> >> <category name="com.opensymphony.xwork2.ogln" additivity="true"> >> <priority value="FATAL"/> >> </category> > > What happen when you spell "ognl" correctly? > > Dave > > --------------------------------------------------------------------- > To unsubscribe, e-mail: user-unsubscr...@struts.apache.org > For additional commands, e-mail: user-h...@struts.apache.org > > --------------------------------------------------------------------- To unsubscribe, e-mail: user-unsubscr...@struts.apache.org For additional commands, e-mail: user-h...@struts.apache.org