[
https://issues.apache.org/jira/browse/SLING-766?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12656985#action_12656985
]
Carsten Ziegeler commented on SLING-766:
----------------------------------------
Changed this in revision 727047:
Don't uninstall content when bundle is stopped. The content is now only
uninstalled when the bundle is uninstalled. During installation a string
array containing all paths that will be removed later on is collected which
makes the uninstall easier. Also refactored the classes and packages a little
bit.
I'll leave the bug open for further testing
> 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.
