[ http://issues.apache.org/jira/browse/JCR-674?page=all ]
Jukka Zitting updated JCR-674:
------------------------------
Component/s: JCR 1.0.1
Priority: Minor (was: Major)
> String properties with invalid XML characters export as invalid XML
> -------------------------------------------------------------------
>
> Key: JCR-674
> URL: http://issues.apache.org/jira/browse/JCR-674
> Project: Jackrabbit
> Issue Type: Bug
> Components: xml, JCR 1.0.1
> Affects Versions: 1.1.1
> Reporter: Joshua Levy
> Priority: Minor
>
> 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.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
