You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sling.apache.org by "Felix Meschberger (JIRA)" <ji...@apache.org> on 2008/03/10 16:55:46 UTC

[jira] Resolved: (SLING-294) Nodetypes not registered if repository becomes available after bundle is loaded

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

Felix Meschberger resolved SLING-294.
-------------------------------------

       Resolution: Fixed
    Fix Version/s: 2.0.0
         Assignee: Felix Meschberger

After SLING-132 has been implemented this issue should also be fixed at the same time, as now node types are loaded as soon as the repository becomes available.

Please close, if your issue is fixed. Thanks.

> Nodetypes not registered if repository becomes available after bundle is loaded
> -------------------------------------------------------------------------------
>
>                 Key: SLING-294
>                 URL: https://issues.apache.org/jira/browse/SLING-294
>             Project: Sling
>          Issue Type: Bug
>          Components: Repository, Resource
>            Reporter: Bertrand Delacretaz
>            Assignee: Felix Meschberger
>             Fix For: 2.0.0
>
>
> Related to SLING-132: if the repository service becomes available after a bundle that contains nodetype definitions was loaded, it seems like the nodetypes are never registered.
> The initial content loading seems to work in such a case.
> I haven't done extensive tests yet, creating the issue so that we don't forget to look at it.

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