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] Resolved: (JCR-1708) Impossible to import a string containing _x0020_ with Session.importXml
Date Wed, 03 Sep 2008 09:19:44 GMT

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

Jukka Zitting resolved JCR-1708.

    Resolution: Fixed
      Assignee: Jukka Zitting

I turned off the decodeBlanks option in revision 691550. We don't encode blanks when exporting,
so there's no point in trying to (even incorrectly) decode them when importing.

Resolving as Fixed.

> Impossible to import a string containing _x0020_  with Session.importXml
> ------------------------------------------------------------------------
>                 Key: JCR-1708
>                 URL: https://issues.apache.org/jira/browse/JCR-1708
>             Project: Jackrabbit
>          Issue Type: Bug
>          Components: jackrabbit-core
>    Affects Versions: core 1.4.5
>            Reporter: Bart van der Schans
>            Assignee: Jukka Zitting
>            Priority: Minor
>             Fix For: core 1.4.6
> The importXml uses the ValueHelper.serialize methods. The option "decodeBlanks" does
a simple string replace which replaces _x0020_ in spaces (line 695 and 793). This option is
always set to true unless the imported data is binary. See: BufferedStringValue and StringValue
getValue methods.
> The result is that it is now impossible to import a string with _x0020_ in it, because
it gets translated in a space. The simple solution would be to just turn off the declodeBlanks
option, but I'm not sure why it was added in the first place. Another option would be to use
real encoding instead of a replace like the o.a.j.util.ISO9075.

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

View raw message