You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sling.apache.org by "Robert Munteanu (JIRA)" <ji...@apache.org> on 2013/09/19 15:37:53 UTC
[jira] [Commented] (SLING-3086) [Tooling] proper handle xml-encoded
path-parts
[ https://issues.apache.org/jira/browse/SLING-3086?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13771889#comment-13771889 ]
Robert Munteanu commented on SLING-3086:
----------------------------------------
Fixed in http://svn.apache.org/viewvc?view=revision&revision=1524739
> [Tooling] proper handle xml-encoded path-parts
> ----------------------------------------------
>
> Key: SLING-3086
> URL: https://issues.apache.org/jira/browse/SLING-3086
> Project: Sling
> Issue Type: Bug
> Components: IDE
> Reporter: Stefan Egli
> Assignee: Robert Munteanu
> Fix For: Sling Eclipse IDE 1.0.0
>
>
> when creating a .content.xml, vault needs to escape node names to be an xml-compliant element name. There is a class is jackrabbit which does that: ISO9075. We should check where exactly we need to escape/unescape paths, but for example one place which causes issues at the moment is UpdateNodePropertiesCommand.updatePath(), there the path contains escaped parts while the lookup with session.nodeExists() expects a unescaped path..
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira