Mailing-List: contact abdera-user-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: abdera-user@incubator.apache.org
Received-SPF: pass (athena.apache.org: domain of ixjonez@gmail.com designates
 209.85.198.187 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=beta;
        h=received:message-id:date:from:sender:to:subject:mime-version:content-type:content-transfer-encoding:content-disposition:x-google-sender-auth;
        b=LpFLFbqNlMdwCbTrywP1BjzExjNqj6GvtHSNaY9OTO8oT1RdkLIkzIO/Jm0K7vs+bvjAcFdnI1etqjuMBUR72e9kSCUOmui9PNhvpaPew3UagM0q/Qu8XkHkhVLU4aEeZI7LQCEg998zmgK1n8EUMRV6gydsUkzbNU0uBRsbfbc=
Message-ID: <29a761a00708071046y113792d2i7ca125f271d37e27@mail.gmail.com>
Date: Tue, 7 Aug 2007 13:46:07 -0400
From: "Brian Moseley" <bcm@osafoundation.org>
Sender: ixjonez@gmail.com
To: abdera-user@incubator.apache.org
Subject: xml restricted characters
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

whose responsibility is it to account for entry content that contains
characters restricted in xml?

i'm generating an entry with content of type "text/json". the content
contains a control character. the feed is serialized and written to
the output stream with no problems.

my expectation is that an exception would be thrown by the axiom xml
serializer when it encounters a restricted character. should i instead
be detecting them in my content before setting it on the entry? is
there a utility for filtering them out? xml doesn't define any
escaping rules for restricted characters does it?