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-674) String properties with invalid XML characters export as invalid XML
Date Wed, 21 Nov 2007 23:53:44 GMT

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

Jukka Zitting updated JCR-674:
------------------------------

          Component/s: SPI
                       jackrabbit-core
    Affects Version/s: 0.9
                       1.0
                       1.0.1
                       1.1
                       1.2.1
                       1.2.2
                       1.2.3
                       1.3
                       1.3.1
                       1.3.3

> String properties with invalid XML characters export as invalid XML
> -------------------------------------------------------------------
>
>                 Key: JCR-674
>                 URL: https://issues.apache.org/jira/browse/JCR-674
>             Project: Jackrabbit
>          Issue Type: Bug
>          Components: jackrabbit-core, JCR 1.0.1, SPI, xml
>    Affects Versions: 0.9, 1.0, 1.0.1, 1.1, 1.1.1, 1.2.1, 1.2.2, 1.2.3, 1.3, 1.3.1, 1.3.3
>            Reporter: Joshua Levy
>            Assignee: Julian Reschke
>            Priority: Minor
>             Fix For: 1.4
>
>
> As noted in the current JCR 1.0.1 maintenance draft, sections 6.4.1,
> 6.4.2.6, XML export of string properties that contain invalid XML
> characters isn't well-defined currently, since those characters are
> not permissible in XML.  The proposed fix is to use base64
> encoding for such values in System View.
> Most characters below #x20 are examples of this.  Currently, these
> are escaped numerically in output (such as (amp)#0; )  but
> such escape sequences can't be parsed by the XML
> import methods.
> The current behavior is particularly problematic, because the user
> doesn't know the output is corrupt until later, when they try to import it
> and get InvalidSerializedDataException.
> If for some reason the base64 option is delayed, it might
> make sense, as an interim solution, to fail on export
> or to somehow patch import to relax its parsing and allow
> these escape codes.

-- 
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