[JCR-2007] Importing strings with special characters fails

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 1.5.5
• Component/s: jackrabbit-core
• Assignee: Thomas Mueller
• Reporter: Thomas Mueller
• Created: 05/Mar/09 11:13
• Updated: 29/Apr/09 07:50
• Resolved: 11/Mar/09 14:42

Description

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.

Issue Links

• is blocked by: JCR-2017 System view export truncates carriage return
• is duplicated by: JCR-2012 BufferedStringValue corrupts non ISO-8859-1 characters on large Strings