DO NOT REPLY [Bug 32527] - log4j initialization in java1.3 no dom in class path.

[bu...@apache.org]

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=32527>.
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=32527





------- Additional Comments From hoju@visi.com  2004-12-04 07:07 -------
I can sort of see your point here that Log4j should do something more useful
than allow a NoClassDefFoundError or the like to propogate to the user and kill
the app.  Or, at a minimum, provide a clear stacktrace showing the reason for
the error as you have below.  However, I would also argue that you have made a
conscious choice to use an XML config file and ought to also be expected to make
sure that the standard XML libraries are in the classpath as well.  What else is
going to parse an XML file?

You can avoid all this by simply using a Properties file.

In any case, this is not likely to be addressed in Log4j-1.2.x since Log4j-1.3
is now the actively developed version.  I don't see this as super high priority,
but it's not a bad idea.  If you provide a patch, this will get addressed much
more quickly.  And keep in mind that the JoranConfigurator is now the default
XML config file parser for Log4j, not DOMConfigurator which is deprecated.  Just
check out the HEAD branch of the logging-log4j module and create a patch against
that.

Jake

-- 
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: log4j-dev-unsubscribe@logging.apache.org
For additional commands, e-mail: log4j-dev-help@logging.apache.org