You are viewing a plain text version of this content. The canonical link for it is here.
Posted to log4j-dev@logging.apache.org by bu...@apache.org on 2004/09/10 22:15:19 UTC
DO NOT REPLY [Bug 31173] New: -
Cannot load LF5 configuration file in JBoss.
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=31173>.
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=31173
Cannot load LF5 configuration file in JBoss.
Summary: Cannot load LF5 configuration file in JBoss.
Product: Log4j
Version: 1.2
Platform: PC
OS/Version: Windows XP
Status: NEW
Severity: Normal
Priority: Other
Component: Other
AssignedTo: log4j-dev@logging.apache.org
ReportedBy: jpianezze@telephia.com
I configure JBoss's log4j.xml to use the LogFactor Appender
LF5 is not able to load its configuration file: lf5_configuration.xml
Works OK with Jboss 3.2.3 and fails with 3.2.5.
LF5 ConfgiurationManager does this:
DocumentBuilderFactory docBuilderFactory = DocumentBuilderFactory.newInstance
();
DocumentBuilder docBuilder = docBuilderFactory.newDocumentBuilder();
Document doc = docBuilder.parse(file);
parse(file) fails with
java.io.FileNotFoundException: C:\Documents%20and%20Settings\jpianezze\lf5
\lf5_configuration.xml
I observe that:
* The DocBuilder uses org.apache.xerces.jaxp.DocumentBuilderImpl
which is distributed with JBoss.
* the JBoss xml parser is shipping with the NEWER version of JBoss
* LF5 is OLDER
* The parser is a standard shared componnt that passed all JBoss's unit tests.
Is it possible that the LF5 code does not use the parser properly?
---------------------------------------------------------------------
To unsubscribe, e-mail: log4j-dev-unsubscribe@logging.apache.org
For additional commands, e-mail: log4j-dev-help@logging.apache.org