[jira] [Created] (SLING-4332) Malformed .content.xml files cause unhandled errors and break the content navigator

["Robert Munteanu (JIRA)" <ji...@apache.org>]

Robert Munteanu created SLING-4332:
--------------------------------------

             Summary: Malformed .content.xml files cause unhandled errors and break the content navigator
                 Key: SLING-4332
                 URL: https://issues.apache.org/jira/browse/SLING-4332
             Project: Sling
          Issue Type: Bug
          Components: IDE
    Affects Versions: Sling Eclipse IDE 1.0.4
            Reporter: Robert Munteanu
            Priority: Critical
             Fix For: Sling Eclipse IDE 1.0.6


Assume a broken XML file named .content.xml is placed in a content project, as below ( note the missing xmlns:rep attribute )

{code:xml}
<?xml version="1.0" encoding="UTF-8"?>
<jcr:root xmlns:sling="http://sling.apache.org/jcr/sling/1.0" xmlns:jcr="http://www.jcp.org/jcr/1.0"
    jcr:mixinTypes="[rep:AccessControllable]"
    jcr:primaryType="sling:OrderedFolder">
    <rep:policy/>
</jcr:root>
{code}

An unhandled exception will be propagated to the user and the content navigator will be broken - only the jcr_root entry will appear, without an icon, and can't be expanded.

We should be more resilient and skip resources with XML parsing errors. Perhaps we should also turn off namespace validation.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)