Howdy,
There's no overriding reason usually to move from
properties to XML files for log4j configuration.  XML
configuration does do a couple of things properties can't,
although off the top of my head I can't remember what
those things are.  OTOH, as always, XML is more verbose
than plaintext, takes longer to parse/load/unmarshal/whatever
you do with it.

Yoav Shapira
Millennium ChemInformatics


>-----Original Message-----
>From: Matt Raible [mailto:[EMAIL PROTECTED]
>Sent: Wednesday, September 17, 2003 8:05 PM
>To: 'Log4J Users List'
>Subject: Converting log4j.properties to log4j.xml
>
>Is it true that the 3 lines in my log4j.properties file:
>
>log4j.logger.org.apache.commons=ERROR
>log4j.logger.org.apache.struts=WARN
>log4j.logger.servletunit.struts=WARN
>
>Will end up as 9 lines in log4j.xml (carriage returns aside)
>
>  <logger name="org.apache.commons">
>    <level value="WARN"/>
>  </logger>
>  <logger name="org.apache.struts">
>    <level value="WARN"/>
>  </logger>
>  <logger name="servletunit.struts">
>    <level value="WARN"/>
>  </logger>
>
>Just want to verify that this is the simplest way to convert a
>.properties to an .xml file?  Also, what's the main reason for
>converting - validation against a DTD?
>
>Thanks,
>
>Matt
>
>
>
>---------------------------------------------------------------------
>To unsubscribe, e-mail: [EMAIL PROTECTED]
>For additional commands, e-mail: [EMAIL PROTECTED]




This e-mail, including any attachments, is a confidential business communication, and 
may contain information that is confidential, proprietary and/or privileged.  This 
e-mail is intended only for the individual(s) to whom it is addressed, and may not be 
saved, copied, printed, disclosed or used by anyone else.  If you are not the(an) 
intended recipient, please immediately delete this e-mail from your computer system 
and notify the sender.  Thank you.


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to