jackrabbit-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Thomas Mueller (JIRA)" <j...@apache.org>
Subject [jira] Commented: (JCR-2007) Importing strings with special characters fails
Date Wed, 11 Mar 2009 15:06:50 GMT

    [ https://issues.apache.org/jira/browse/JCR-2007?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12680886#action_12680886

Thomas Mueller commented on JCR-2007:

Julian - see the test case please.

> 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
>             Fix For: 1.6.0
> 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.

View raw message