Wrong namespace in the XML file for cq:EditConfig node about aem-eclipse-developer-tools

[rombert]

@patricklwy14 - thanks for the report. I was able to reproduce the error that you mentioned - for the record it is

Failed reading file at /sample004/jcr_root/content/example/comp/.xml
org.xml.sax.SAXParseException; lineNumber: 6; columnNumber: 26; The prefix "cq" for attribute "cq:layout" associated with an element type "jcr:root" is not bound.

Now, this simply says that you have added a cq:layout attribute without declaring the cq namespace in the XML file. The error will be avoided by adding that namespace to the XML file. I can see this being a bug if we were to have specific wizards for components and edit configs and those would have missing namespaces. But at the moment I'm not sure what we can do ... it's not 100% safe to 'detect' namespaces from the repository ( and we're not always connected to the repository ) and even that would be awkward to implement.

Thoughts?

[rombert]

Adding @AliShirazi from duplicate issue #62

Some things which we can do better here, in no particular order:

• validate the vault files and trigger errors in the editor. The standard XML validator from Eclipse is disabled as it generates ( in the vault file scenario ) spurious warnings but we can add a custom one with better messages
• when adding a (namespaced) property via the properties view, ensure that the prefix is a valid one and add the namespace if needed

Thoughts?

[kwin]

The XML Validation has been enabled now for content-package projects (https://issues.apache.org/jira/browse/SLING-6237) so with the upgrade to Sling IDE 1.2.0 there should be a proper error message once you use an undeclared namespace.

[gabrielwalt]

Closing this as there hasn't been activity for over a year.