DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG· RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT <http://issues.apache.org/bugzilla/show_bug.cgi?id=43200>. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND· INSERTED IN THE BUG DATABASE.
http://issues.apache.org/bugzilla/show_bug.cgi?id=43200 ------- Additional Comments From [EMAIL PROTECTED] 2007-08-23 11:30 ------- That would be as expected, LogLog.error is still called if the resource could not be found. The thing that changed was instead of returning null which tells the parser to try to find it on its own, an empty InputSource is returned which will prevent the parser to try to find it on its own. So hopefully you lost the exception from the parser when it could not find log4j.dtd. Could downgrade it from a LogLog.error to a LogLog.warn. There are two issues here: one is what do in the case that the resource can not be found. Other than potentially downgrading the message to a LogLog.warn, I think the fix is good. The other is why you can't find the resource and there isn't enough to go on for me to figure that out and to decide if it is a log4j issue or a IDE project issue. -- Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
