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

Georg Henzler updated SLING-3624:
---------------------------------

    Attachment: SLING-3624-HC-annotation-with-additional-properties.patch

Attached the patch for mbean name and async cron expression. Also cleaned up a 
bit on the way:
- name is optional for annotation now (to be in line with documentation at 
org.apache.sling.hc.api.HealthCheck.NAME)
- if label and description for the metatype descriptor is not set, a reasonable 
default will be chosen automatically (using HC Name)
- HC properties get the metatype label/description set


> Add SlingHealthCheck annotation
> -------------------------------
>
>                 Key: SLING-3624
>                 URL: https://issues.apache.org/jira/browse/SLING-3624
>             Project: Sling
>          Issue Type: Improvement
>          Components: Health Check
>    Affects Versions: Health Check Core 1.1.0
>            Reporter: Bjoern Weide
>            Assignee: Bertrand Delacretaz
>            Priority: Minor
>             Fix For: Health Check Core 1.1.2
>
>         Attachments: 
> SLING-3624-HC-annotation-with-additional-properties.patch, 
> slinghealthcheck_annotation.txt
>
>
> Add a SlingHealthCheck annotation (similar to SlingServlet). The metatype 
> property should set to true per default since its probably common to 
> configure healthchecks. Usage examples:
> {code:title=Examples|borderStyle=solid}
> @SlingHealthCheck(name = BundlesStartedCheck.HC_NAME, label = "Apache Sling 
> Health Check - " + BundlesStartedCheck.HC_NAME, description = "Checks whether 
> all bundles are started.", tags = "osgi")
> @SlingHealthCheck(name = DiskSpaceCheck.HC_NAME, label = "Apache Sling Health 
> Check - " + DiskSpaceCheck.HC_NAME,
>         description = "Checks whether enough disk space is available.", tags 
> = "resources", configurationFactory = true,
>         configurationPolicy = ConfigurationPolicy.REQUIRE)
> {code}



--
This message was sent by Atlassian JIRA
(v6.2#6252)

Reply via email to