[jira] Closed: (SLING-766) Initial Content should not be removed on bundle stop

["Carsten Ziegeler (JIRA)" <ji...@apache.org>]

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

Carsten Ziegeler closed SLING-766.
----------------------------------

    Resolution: Fixed

No further comments, so I'll close this bug. If any problems arise please open new bugs.

> Initial Content should not be removed on bundle stop
> ----------------------------------------------------
>
>                 Key: SLING-766
>                 URL: https://issues.apache.org/jira/browse/SLING-766
>             Project: Sling
>          Issue Type: Bug
>          Components: JCR Contentloader
>    Affects Versions: JCR Contentloader 2.0.2
>            Reporter: Carsten Ziegeler
>            Assignee: Carsten Ziegeler
>             Fix For: JCR Contentloader 2.0.4
>
>
> Currently the initial content is removed on a bundle stop - while this is logically ok (content is installed on bundle start, and content shouldn't be available when bundle is not running anymore), this creates problems when the server is shutdown as the bundle is stopped and therefore removes all content on shutdown.
> (of course the content is added again on server startup)
> Therefore it's better to remove the content only when the bundle is uninstalled. As a consequence of not uninstalling the initial content anymore when the bundle is stopped, content update when the bundle is updated must be adapted and take care on properly replacing old content with new content.

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