Mailing-List: contact dev-help@jackrabbit.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@jackrabbit.apache.org
Message-ID: <1784091792.1236781490572.JavaMail.jira@brutus>
Date: Wed, 11 Mar 2009 07:24:50 -0700 (PDT)
From: "Thomas Mueller (JIRA)" <jira@apache.org>
To: dev@jackrabbit.apache.org
Subject: [jira] Updated: (JCR-2007) Importing strings with special
 characters fails
In-Reply-To: <929630143.1236251638997.JavaMail.jira@brutus>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


     [ https://issues.apache.org/jira/browse/JCR-2007?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Thomas Mueller updated JCR-2007:
--------------------------------

    Description: 
Both Session.importXML and Workspace.importXML don't work correctly in some cases.

Importing very large foreign language (for example, Chinese) text properties could fail on some platforms. BufferedStringValue buffers very large string to a temporary file. It uses the platform default encoding to read and write the text.

BufferedStringValue is relatively slow on some systems when importing large texts or binary data because of using FD().sync().

If a string contains a carriage return (\r), this character was truncated on some platforms.

If a string contains a characters < 32 excluding newline (\n) and tab (\t) - for example form feed (\f) - the imported string was base64 encoded.


  was:BufferedStringValue buffers very large string to a temporary file. It uses the platform default encoding to read and write the text. Usually this is not a problem, however importing very large foreign language (for example, Chinese) text properties could fail on some platforms.

        Summary: Importing strings with special characters fails  (was: Importing very large strings could fail in some situations)

> Importing strings with special characters fails
> -----------------------------------------------
>
>                 Key: JCR-2007
>                 URL: https://issues.apache.org/jira/browse/JCR-2007
>             Project: Jackrabbit Content Repository
>          Issue Type: Bug
>          Components: jackrabbit-core
>            Reporter: Thomas Mueller
>            Assignee: Thomas Mueller
>
> Both Session.importXML and Workspace.importXML don't work correctly in some cases.
> Importing very large foreign language (for example, Chinese) text properties could fail on some platforms. BufferedStringValue buffers very large string to a temporary file. It uses the platform default encoding to read and write the text.
> BufferedStringValue is relatively slow on some systems when importing large texts or binary data because of using FD().sync().
> If a string contains a carriage return (\r), this character was truncated on some platforms.
> If a string contains a characters < 32 excluding newline (\n) and tab (\t) - for example form feed (\f) - the imported string was base64 encoded.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.