[
https://issues.apache.org/jira/browse/SLING-36?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Felix Meschberger closed SLING-36.
----------------------------------
Resolution: Won't Fix
Issue pertains to former Component API and has no correspondence with the new
Sling API. Closing.
> Repository Based components not cleaned up when not existing any longer
> -----------------------------------------------------------------------
>
> Key: SLING-36
> URL: https://issues.apache.org/jira/browse/SLING-36
> Project: Sling
> Issue Type: Bug
> Components: Core
> Affects Versions: 2.0.0
> Reporter: Felix Meschberger
> Priority: Critical
> Fix For: 2.0.0
>
>
> The RepositoryComponentRegistration services access the JCR repository to see
> whether there are any component descriptors stored in the repository and
> updates the component registry in case of new, modified or removed components.
> Unfortunately, this service does not pay attention to the fact, that a bundle
> providing mappings for such components may be stopped, removed, added or
> updated. In such cases the registered components are not touched and stay. In
> fact new components will not be visible until after a restart of the
> RepositoryComponentResgistration.
> The registration of JCR based components must be modified to take into
> account that OCM mappings for such components may be added and/or removed at
> run time and that there is another influence on the state of registered
> components than just the repository.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
