Although this would work for me personally during development, i am not the first line of tech support... So when something breaks, and tech support turns logging up to debug, i would like them not to have a bunch of extra exceptions in their logs. As well, i do not expect them to have any knowledge of my technologies, so for them to turn down the logging on stuff to ignore, would result in them asking me what they should ignore, as well as them asking me how to ignore it. So, can i bypass this whole thing, and fix these exceptions before i release?
On 1/3/08, Dave Newton <[EMAIL PROTECTED]> wrote: > > Turn down logging on the stuff you want to ignore. > > --- Brian Relph <[EMAIL PROTECTED]> wrote: > > > When i turn logging up to debug, i get TONS of the same stack trace when > > using my struts2 app ... > > > > Can i get rid of these somehow? > > > > [1/3/08 13:08:13:106 CST] 0000004c SystemOut O [WebContainer : 1] > DEBUG > > com.opensymphony.xwork2.util.InstantiatingNullHandler - Entering > > nullPropertyValue [target=[ > > > [EMAIL PROTECTED] > , > > [EMAIL PROTECTED], > > [EMAIL PROTECTED], > > [EMAIL PROTECTED], property=struts] > > [1/3/08 13:08:13:106 CST] 0000004c SystemOut O [WebContainer : 1] > DEBUG > > com.opensymphony.xwork2.util.OgnlValueStack - Error setting value > > ognl.OgnlException: source is null for getProperty(null, "portlet") > > at ognl.OgnlRuntime.getProperty(OgnlRuntime.java:1638) > > > > > > > > Thanks, > > > > Brian > > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > >
