Uploaded image for project: 'Sling'
  1. Sling
  2. SLING-36

Repository Based components not cleaned up when not existing any longer

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Critical
    • Resolution: Won't Fix
    • Affects Version/s: 3
    • Fix Version/s: 3
    • Component/s: Engine
    • Labels:
      None

      Description

      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.

        Attachments

          Activity

            People

            • Assignee:
              Unassigned
              Reporter:
              fmeschbe Felix Meschberger
            • Votes:
              0 Vote for this issue
              Watchers:
              0 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: