jackrabbit-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jan Kuzniak (JIRA)" <j...@apache.org>
Subject [jira] Commented: (JCR-690) Nodes' and properties' names with invalid XML characters export as invalid XML
Date Tue, 02 Jan 2007 10:07:27 GMT

    [ http://issues.apache.org/jira/browse/JCR-690?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12461702

Jan Kuzniak commented on JCR-690:

> I think we should adopt the same policy already now

Already? And what about compatibility issues? If there are people using invalid XML characters
as nodes' and properties' names, their repositories will become invalid with next release.
Well, it's OK if it is introduced in jackrabbit 2.0, but as a user I would not expect such
an issue while upgrading to 1.3.

Probably we should write some external program checking if given repository is compatible
with next release and maybe escaping invalid characters in the repository itself. 

Another approach is to implement escaping using _X0000_ pattern as a 1.x solution and restrict
allowed characters set starting from jackrabbit 2.x

> Nodes' and properties' names with invalid XML characters export as invalid XML
> ------------------------------------------------------------------------------
>                 Key: JCR-690
>                 URL: http://issues.apache.org/jira/browse/JCR-690
>             Project: Jackrabbit
>          Issue Type: Bug
>          Components: JCR 2.0, xml
>    Affects Versions: 1.1, 1.1.1
>            Reporter: Jan Kuzniak
>            Priority: Minor
> Session.exportSystemView method does check whether character should be escaped using
_X0000_ pattern or not. It just puts it into XML without any validation. It causes e.g. XML
attributes to contain entities like &#0;

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


View raw message