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

Jan Kuzniak commented on JCR-690:
---------------------------------

> Using the _x0000_ escapes is not a good solution [...]

Agreed.

> IMHO the only way to make the export/import of such names work is to add some 
> extra attribute that indicates the name encoding.

Do you mean something like:
<sv:node sv:name="[base64 encoded value]" jcr:nameEncoding="base64">
?

There is one point worth mentioning here: for repositories containing invalid 
XML values documents exported from Jackrabbit 1.3+ will not be importable by 
previous versions of Jackrabbit and other JCR repositories.

> [..] we could for now just make the name parser log warnings of invalid 
> characters

Agreed, good idea.

> 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

        

Reply via email to