Return-Path:
Mailing-List: contact general-help@xml.apache.org; run by ezmlm
Delivered-To: mailing list general@xml.apache.org
Received: (qmail 25425 invoked from network); 30 Jun 2000 06:34:14 -0000
Received: from ns.netnord.dk (HELO aalborg.netnord.dk) (mta@192.38.202.2)
by locus.apache.org with SMTP; 30 Jun 2000 06:34:14 -0000
Received: from kridt (kridt.geografik.dk [130.225.63.208])
by aalborg.netnord.dk (Post.Office MTA v3.5.1 release 219
ID# 0-52465U1200L200S0V35) with SMTP id dk
for ; Fri, 30 Jun 2000 08:34:12 +0200
From: dt@netnord.dk (Dennis Thrysoe - Netnord A/S)
To:
Subject: RE: Problem in XMLSerializer (1.2.1): Solved
Date: Fri, 30 Jun 2000 08:34:12 +0200
Message-ID: <000c01bfe25d$341f0fb0$d03fe182@geografik.dk>
MIME-Version: 1.0
Content-Type: text/plain;
charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook 8.5, Build 4.71.2173.0
X-MIMEOLE: Produced By Microsoft MimeOLE V5.00.2919.6600
Importance: Normal
In-Reply-To: <395B98AD.4B092599@apache.org>
X-Spam-Rating: locus.apache.org 1.6.2 0/1000/N
I gave the constructor a Writer, so that couldn't be it.
I found the problem though. Even though XMLSerializer exposes all the
methods of the ContentHandler interface, it only works if asContentHandler()
is called first. Perhaps this should be documented?
-dennis
> The serialize code changed and it now *requires* you to set the
> output stream (or writer) before using it for serialization.
> Assaf Arkin can give you more information on the implementation.