Ceki, Thank you - that fixed my problem! The characters 0xEFBBBF are the UTF-8 Byte Order Mark that is part if the unicode standard. Apparently, Crimson can't handle UTF-8 while Xerces can.
On another topic, do you if there any is interest in the patch I contributed to fix the LoggerFactory bug reported as 21707? (http://nagoya.apache.org/bugzilla/show_bug.cgi?id=21707) Thanks, Mark -----Original Message----- From: Ceki G�lc� [mailto:[EMAIL PROTECTED] Sent: Thursday, September 04, 2003 12:47 PM To: Log4J Users List Subject: RE: Problem with Crimson parser The first three bytes in of the config file are (in hex) EF BB BF instead of "<?x", or 3C 3F 78 in hex. Your file looks OK otherwise. Just remove the first 3 bytes to keep Crimson happy. At 02:12 PM 9/3/2003 -0400, [EMAIL PROTECTED] wrote: >Ceki, > >I tried initializing with a sample xml config file from the distribution >and it works fine with Crimson. I tried playing around with DOCTYPE and >other preamable elements in my document but I could not get it to work. I >have attached my config file to this email in case you can figure out what >is wrong with it. > >Thanks, >Mark -- Ceki G�lc� For log4j documentation consider "The complete log4j manual" ISBN: 2970036908 http://www.qos.ch/shop/products/clm_t.jsp See you in November at ApacheCon US 2003 in Las Vegas. http://apachecon.com/ --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
