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 jasnell@gmail.com designates
 66.249.82.235 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=beta;
        h=received:message-id:date:from:user-agent:mime-version:to:subject:references:in-reply-to:content-type:content-transfer-encoding;
        b=a97WFUTW6mRJrd9j/S31hC3lDhX6zIISS7o0Ixx2+XcE+diePlQ1+5LlQ9/quzA4EvYI1XYWt++55Nl8hF6eP6L4+9hfvEdrednYQzFg27ExiHMCMmFTzIBC6/KErbZuPVyLs8ADhiJ6uIht/LuzORsjmTxxdAd5N7fKPgbhzic=
Message-ID: <46B8B0D6.1010300@gmail.com>
Date: Tue, 07 Aug 2007 10:50:14 -0700
From: James M Snell <jasnell@gmail.com>
User-Agent: Thunderbird 2.0.0.0 (X11/20070326)
MIME-Version: 1.0
To: abdera-user@incubator.apache.org
Subject: Re: xml restricted characters
References: <29a761a00708071046y113792d2i7ca125f271d37e27@mail.gmail.com>
In-Reply-To: <29a761a00708071046y113792d2i7ca125f271d37e27@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit

The trunk now includes support for filtering out restricted characters
when parsing.  When enabled in ParserOptions, those characters are
ignored completely and never appear within the parsed document.  If you
parse a doc with restricted chars then reserialize, they should not be
present at all.  There currently is no mechanism for filtering out
restricted chars on serialization due to a limitation in the Axiom
serialization code.  I'm looking to resolve that later.  In the
meantime, there is a reader implementation that can do the filtering for
you if you'd like. Look in org.apache.abdera.util.* for the reader.

- James

Brian Moseley wrote:
> 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?
>