jackrabbit-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jukka Zitting (JIRA)" <j...@apache.org>
Subject [jira] Updated: (JCR-2007) Importing strings with special characters fails
Date Wed, 22 Apr 2009 14:03:47 GMT

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

Jukka Zitting updated JCR-2007:
-------------------------------

    Fix Version/s:     (was: 1.6.0)
                   1.5.5

Merged to the 1.5 branch in revision 767525.

> 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.5.5
>
>
> Both Session.importXML and Workspace.importXML don't work correctly in some cases.
> Importing very large foreign language (for example, Chinese) text property values could
result in incorrect values on some platforms. The reason is, BufferedStringValue (buffers
very large string to a temporary file) 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 an exported string value contains a carriage return (\r), this character was truncated
on some platforms.
> If an exported string value contains a characters with code below 32 excluding newline
(\n) and tab (\t) - for example form feed (\f) - the imported string value was base64 encoded.

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


Mime
View raw message