[jira] Closed: (SLING-667) sling:VanityPath may not be registered during bundle update

["Felix Meschberger (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/SLING-667?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Felix Meschberger closed SLING-667.
-----------------------------------

    Resolution: Fixed

Created three node type definition files -- folder.cnd, resource.cnd, and vanitypath.cnd -- to minimize effects of node type registration failure. The background of this split is, that registration of node types from a single definition file is an all-or-nothing game. So if some node types fail to register, none are registered.

Fixed in Rev. 696946.

> sling:VanityPath may not be registered during bundle update
> -----------------------------------------------------------
>
>                 Key: SLING-667
>                 URL: https://issues.apache.org/jira/browse/SLING-667
>             Project: Sling
>          Issue Type: Bug
>          Components: JCR Resource
>    Affects Versions: JCR Resource 2.0.4
>            Reporter: Felix Meschberger
>            Assignee: Felix Meschberger
>             Fix For: JCR Resource 2.0.4
>
>
> If the jcr/resource bundle is updated from an earlier version to the current trunk version, the registration of sling:VanityPath may fail and thus the JcrResourceResolver may fail because the query in JcrResourceResolver.searchVanityPath will fail due to the missing node type.
> Solution is to split the node type definition file such that the sling:VanityPath node type is defined in its own file.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.