[
https://issues.apache.org/jira/browse/SLING-3422?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13918206#comment-13918206
]
Bertrand Delacretaz commented on SLING-3422:
--------------------------------------------
IIUC the failure scenario is as follows:
# A service S that's registered with the Sling scheduler uses an @Modified
annotation to be informed of configuration changes
# When that service's config changes, The @Modified method of S gets invoked,
but the Sling scheduler is not informed of the configuration change
If I'm correct that's by design, as I assume (haven't checked) that the Sling
scheduler identifies changes in scheduler.expression values by listening to the
service activations and deactivations. If S handles the "config modified" event
itself there's no deactivation/reactivation and the Sling scheduler sees
nothing.
We might then just document this behavior in the Sling scheduler docs/javadocs.
> Sling Scheduler Not Updated For Runnable with Modified method
> -------------------------------------------------------------
>
> Key: SLING-3422
> URL: https://issues.apache.org/jira/browse/SLING-3422
> Project: Sling
> Issue Type: Bug
> Components: Commons
> Affects Versions: Commons Scheduler 2.3.4
> Environment: Mac OS X 10.9.1
> Java 1.6.0_65
> Reporter: Ian Reasor
> Priority: Minor
>
> When changing the scheduler.expression value for an OSGi service, the
> scheduler status screen was not showing the updated time. Any time the
> bundle would be redeployed, the updated time would be shown. We were able to
> work around the issue by removing the Modified annotation from the OSGi
> service.
> If relevant, the activate method had been marked with both Activate and
> Modified annotations.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
