Return-Path: Delivered-To: apmail-ant-dev-archive@www.apache.org Received: (qmail 77355 invoked from network); 4 Oct 2004 14:56:50 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur-2.apache.org with SMTP; 4 Oct 2004 14:56:50 -0000 Received: (qmail 99007 invoked by uid 500); 4 Oct 2004 14:56:48 -0000 Delivered-To: apmail-ant-dev-archive@ant.apache.org Received: (qmail 98887 invoked by uid 500); 4 Oct 2004 14:56:46 -0000 Mailing-List: contact dev-help@ant.apache.org; run by ezmlm Precedence: bulk List-Unsubscribe: List-Subscribe: List-Help: List-Post: List-Id: "Ant Developers List" Reply-To: "Ant Developers List" Delivered-To: mailing list dev@ant.apache.org Received: (qmail 98865 invoked by uid 99); 4 Oct 2004 14:56:46 -0000 X-ASF-Spam-Status: No, hits=0.2 required=10.0 tests=HTML_50_60,HTML_MESSAGE,NO_REAL_NAME X-Spam-Check-By: apache.org Received-SPF: pass (hermes.apache.org: local policy) Received: from [193.109.238.66] (HELO dnsinet.rzf-nrw.de) (193.109.238.66) by apache.org (qpsmtpd/0.28) with ESMTP; Mon, 04 Oct 2004 07:56:45 -0700 Received: from z011104.bk.fin.local (z011104.bk.fin.local [193.109.238.140]) by dnsinet.rzf-nrw.de (8.12.10/8.12.10) with ESMTP id i94EudvR007273 for ; Mon, 4 Oct 2004 16:56:39 +0200 Received: by z011104.bk.fin.local with Internet Mail Service (5.5.2657.72) id <4FJ958KK>; Mon, 4 Oct 2004 16:56:41 +0200 Message-ID: <879A5AD5DD0ED511891F0003473A9B560E23F6C6@Z011004> From: Jan.Materne@rzf.fin-nrw.de To: dev@ant.apache.org Subject: AW: XML Logger conceptual usage Date: Mon, 4 Oct 2004 16:56:39 +0200 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2657.72) Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01C4AA22.5A9EE7F0" X-Virus-Checked: Checked X-Spam-Rating: minotaur-2.apache.org 1.6.2 0/1000/N ------_=_NextPart_001_01C4AA22.5A9EE7F0 Content-Type: text/plain; charset="iso-8859-1" > My question would be: Is there any change request which > requests that the XMLLogger not to use DOM API, rather some stream? Not as I am aware off. But I havent looked at BugZilla. > PS: By the time I solved the problem, I made a workaround, > but the problem is still there... :( Have you tried the Log4J-Logger with XMLAppender? Jan ------_=_NextPart_001_01C4AA22.5A9EE7F0--