Mailing-List: contact users-help@jackrabbit.apache.org; run by ezmlm
Precedence: bulk
Reply-To: users@jackrabbit.apache.org
Received-SPF: pass (herse.apache.org: domain of lists@nabble.com designates
 72.21.53.35 as permitted sender)
Message-ID: <7842936.post@talk.nabble.com>
Date: Tue, 12 Dec 2006 14:16:42 -0800 (PST)
From: Joshua Levy <levy@csl.sri.com>
To: users@jackrabbit.apache.org
Subject: Re: Invalid XML characters in export
In-Reply-To: <510143ac0612121253h647ac1c8r737841da22f7a7b1@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
References: <7840519.post@talk.nabble.com>
 <510143ac0612121253h647ac1c8r737841da22f7a7b1@mail.gmail.com>


Jukka Zitting wrote:
> 
>> Is there a way to deal with this issue? I wasn't able to find
>> much clarification on what the correct behavior should
>> be from the spec (String properties are supposed to
>> be like java.lang.Strings, but Sec 6.4.4 doesn't mention
>> ways to escape non-XML characters).
> 
> It's a known issue with JSR-170, invalid XML characters in string
> properties break the XML imports. See the JSR-170 maintenance draft
> for the proposed solution (use Base64 encoding for such string
> properties) to this issue.
> 
> Note that Jackrabbit does not yet implement this solution, so for now
> the only workaround is to either avoid such characters in string
> properties or to use custom import/export mechanisms.
> 

Aha, I see.  Thanks, Jukka.

Roughly, is there an expected time frame for such
maintenance draft features to get finalized and implemented?

Regards,
Joshua
-- 
View this message in context: http://www.nabble.com/Invalid-XML-characters-in-export-tf2809830.html#a7842936
Sent from the Jackrabbit - Users mailing list archive at Nabble.com.