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=42575>. 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=42575 Summary: Parsing errors in log4j-1.2.13 Product: Log4j Version: 1.3alpha Platform: All OS/Version: other Status: NEW Severity: normal Priority: P2 Component: Other AssignedTo: [email protected] ReportedBy: [EMAIL PROTECTED] We am encountering some problem as we have to parse our configuration file log4j.xml in a log4j application as we migrate from log4j-1.2.8 to log4j- 1.2.13 . In log4j-1.2.13 category has been deprecated and logger has been provided in place of it. With log4j-1.2.8 (i.e. in my previous log4j.xml file) I have a category declaration like the following: <category name="ClassName$Assigner"> <priority value="debug"/> </category> Here Assigner is an internal class name in a class called ClassName and this gets parsed ok. But with log4j-1.2.13 (i.e in our new log4j.xml file) we want to use logger instead of category and we have the following declaration: <logger name="ClassName$Assigner"> <level value="debug"/> </logger> This gives error in parsing; it complains the following: log4j:WARN Continuable parsing error 122 and column 43 log4j:WARN Attribute value "ClassName$Assigner" of type ID must be a name. That is, it is not accepting ClassName$Assigner to be a logger name. we wish to know where if there is any workaround possible for this internal class to get parsed with a logger declaration. Is it a bug? Regards -- 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]
