| Summary: | Configurator does not cater for inner classes ie, containing a $ in the name) | ||
|---|---|---|---|
| Product: | Log4j - Now in Jira | Reporter: | Ramon Casha <rcasha> |
| Component: | Configurator | Assignee: | log4j-dev <log4j-dev> |
| Status: | RESOLVED DUPLICATE | ||
| Severity: | normal | ||
| Priority: | P2 | ||
| Version: | 1.2 | ||
| Target Milestone: | --- | ||
| Hardware: | PC | ||
| OS: | Linux | ||
|
Description
Ramon Casha
2009-10-21 04:31:13 UTC
Could you confirm that this is still an issue with the current SVN HEAD? It sounds familiar, but I don't have time to look it up at the moment. Yes, it's still there on svn head: log4j:ERROR Parsing error on line 43 and column 38 log4j:ERROR Attribute value "almira.DB$Location" of type ID must be a name. That message is from the XML parser validating the configuration file against a DTD where the attribute is defined to be an ID or IDREF. That is consistent with the behavior noticed in bug 41487 which was fixed in rev 510723 in 2007. The DTD validation messages are informative only (reporting them as an ERROR overstates the case, they are an XML error, but not an XML fatal error). Configuration actually succeeded at least in the original bug. I've reviewed the current log4j.dtd and there are no longer any ID or IDREF attributes, so I don't see how this could happen unless the DOMConfigurator is using an old DTD. Either, there is an older log4j.jar on the classpath or you specify a DTD that the DOMConfigurator doesn't replace with its internal copy of log4j.dtd. I think you're right; I moved the Log4J Jar to the top of the classpath and this error disappeared. |