[jira] [Closed] (SLING-4286) "obsolete" resources resource cleanup tool

["Nicolas Peltier (JIRA)" <ji...@apache.org>]

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

Nicolas Peltier closed SLING-4286.
----------------------------------

> "obsolete" resources resource cleanup tool
> ------------------------------------------
>
>                 Key: SLING-4286
>                 URL: https://issues.apache.org/jira/browse/SLING-4286
>             Project: Sling
>          Issue Type: New Feature
>          Components: Extensions
>            Reporter: Nicolas Peltier
>            Priority: Minor
>
> Hi,
> along a repository life, some JCR resources whose resource type don't exist anymore accumulate. 
> Those are not all to remove (e.g. a resource type can be set without renderer), but some others are just obsolete resources that will almost silently exist. 
> Most common example is resource meant to be rendered without renderer (removed AEM component e.g.), that will generate following ERROR message in the logs, but not break anything:
> 21.08.2013 07:41:50.367 ERROR [10.5.81.178 [1377096110089] GET /content/blah/mother/resource.html HTTP/1.0] org.apache.sling.servlets.get.impl.DefaultGetServlet No renderer for extension html, cannot render resource Paragraph, path=/content/blah/mother/resource/jcr:content/par/title, type=obsolete/component/title, cssClass=default, column=0/0, diffInfo=[null], resource=[, type=obsolete/component/title, path=/content/blah/mother/resource/jcr:content/par/title, resource=[JcrNodeResource, type=obsolete/component/title, superType=null, path=/content/blah/mother/resource/jcr:content/par/title]]
> i've written a small tool to clean those up safely in there 
> https://github.com/npeltier/org.apache.sling.typecleanup
> i'd be happy to contribute if useful. Please comment :-)



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)