You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@jackrabbit.apache.org by "Carl Hall (JIRA)" <ji...@apache.org> on 2010/08/21 19:08:16 UTC
[jira] Created: (JCR-2723) Exception when missing namespace in CND
file should have clearer message
Exception when missing namespace in CND file should have clearer message
------------------------------------------------------------------------
Key: JCR-2723
URL: https://issues.apache.org/jira/browse/JCR-2723
Project: Jackrabbit Content Repository
Issue Type: Improvement
Components: jackrabbit-jcr-commons, nodetype
Affects Versions: 2.1.1, 2.1.0
Reporter: Carl Hall
Attachments: types-bad.cnd, types-good.cnd
Using the attached CND file, when calling CndImporter.registerNodeTypes(..) the following message is in the returned exception:
"Unable to parse CND Input: Error setting name of sling:resourceType to sling:resourceType (bundle://23.0:0/SLING-INF/nodetypes/types.cnd, line 24)"
The issue with line 24 is that the "sling" namespace has not been included. The message should state that a namespace is missing and what prefix is not understood.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (JCR-2723) Exception when missing namespace in CND
file should have clearer message
Posted by "Carl Hall (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/JCR-2723?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Carl Hall updated JCR-2723:
---------------------------
Attachment: types-bad.cnd
types-good.cnd
types-bad.cnd is missing a namespace and causes the error noted in the description.
types.good.cnd contains the "sling" namespace and doesn't cause an exception when importing.
> Exception when missing namespace in CND file should have clearer message
> ------------------------------------------------------------------------
>
> Key: JCR-2723
> URL: https://issues.apache.org/jira/browse/JCR-2723
> Project: Jackrabbit Content Repository
> Issue Type: Improvement
> Components: jackrabbit-jcr-commons, nodetype
> Affects Versions: 2.1.0, 2.1.1
> Reporter: Carl Hall
> Attachments: types-bad.cnd, types-good.cnd
>
>
> Using the attached CND file, when calling CndImporter.registerNodeTypes(..) the following message is in the returned exception:
> "Unable to parse CND Input: Error setting name of sling:resourceType to sling:resourceType (bundle://23.0:0/SLING-INF/nodetypes/types.cnd, line 24)"
> The issue with line 24 is that the "sling" namespace has not been included. The message should state that a namespace is missing and what prefix is not understood.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Resolved: (JCR-2723) Exception when missing namespace in CND
file should have clearer message
Posted by "Stefan Guggisberg (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/JCR-2723?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Stefan Guggisberg resolved JCR-2723.
------------------------------------
Fix Version/s: 2.2.0
Resolution: Fixed
fixed in svn r99544
> Exception when missing namespace in CND file should have clearer message
> ------------------------------------------------------------------------
>
> Key: JCR-2723
> URL: https://issues.apache.org/jira/browse/JCR-2723
> Project: Jackrabbit Content Repository
> Issue Type: Improvement
> Components: jackrabbit-jcr-commons, nodetype
> Affects Versions: 2.1.0, 2.1.1
> Reporter: Carl Hall
> Fix For: 2.2.0
>
> Attachments: types-bad.cnd, types-good.cnd
>
>
> Using the attached CND file, when calling CndImporter.registerNodeTypes(..) the following message is in the returned exception:
> "Unable to parse CND Input: Error setting name of sling:resourceType to sling:resourceType (bundle://23.0:0/SLING-INF/nodetypes/types.cnd, line 24)"
> The issue with line 24 is that the "sling" namespace has not been included. The message should state that a namespace is missing and what prefix is not understood.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.