Mailing-List: contact j-users-help@xerces.apache.org; run by ezmlm
Precedence: bulk
Reply-To: j-users@xerces.apache.org
Received-SPF: neutral (asf.osuosl.org: local policy)
Message-ID: <42E49636.1020606@myrealbox.com>
Date: Mon, 25 Jul 2005 10:35:18 +0300
From: Stanimir Stamenkov <stanio@myrealbox.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US;
 rv:1.8b2) Gecko/20050707 Netscape/7.2 (Spidey) SeaMonkey/1.0a
MIME-Version: 1.0
To: j-users@xerces.apache.org
Subject: Re: XMLSerializer Writer Constructor
References: <42E470E3.9090901@orionhealth.com>
In-Reply-To: <42E470E3.9090901@orionhealth.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

/Stephen Kestle/:

> Of course it is because Characters should not need to specify encoding, 
> but xml IS NOT a character stream - it's an encoded character stream 
> [...]

Don't want to spam the list but: XML _is_ a character stream. The 
byte encoded representation is for transport means as most data in 
the computer world is stored as sequences of bytes. Your sentence 
seems to me like: "DOM is not an object, it is an 'encoded' XML stream".

> Please stop the madness - just deprecate it and write a nice javadoc 
> explaining why.  You'll probably end up saving 1000s of developer hours 
> on that change alone.

You know, I've thought of that many times too, but what if I need to 
write to a character buffer and not a byte one? I think it is just 
problem of the less experienced developers which doesn't realize 
what actually happens when encoding text to a byte stream and in 
particular serializing XML.

-- 
Stanimir


---------------------------------------------------------------------
To unsubscribe, e-mail: j-users-unsubscribe@xerces.apache.org
For additional commands, e-mail: j-users-help@xerces.apache.org