[
https://issues.apache.org/jira/browse/KARAF-751?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13727420#comment-13727420
]
Carsten Ziegeler commented on KARAF-751:
----------------------------------------
While I'm a fan of SCR, this is not a must - now, I really think - as Robert
suggests - it would make sense to use Sling's scheduler as-is and benefit from
reusable modules. A lot of modules out there use SCR and its - like Blueprint -
part of the OSGi spec. So in my opinion an OSGi stack should contain SCR. The
beauty of OSGi and the service registry is, that the components play well
together regardless of which technology is used to define/register them.
Now, if it turns on, that the dependency to SCR is the only problem which
prevents you from reusing the module and there is absolutely no chance to
include SCR in the stack, a patch to the Sling scheduler which changes the code
to rely on just the framework API could be an option. We can also discuss other
changes like making the thread pool optional. The Sling dev list is a good
place to discuss this :)
> Provide a Timer Service in Karaf
> --------------------------------
>
> Key: KARAF-751
> URL: https://issues.apache.org/jira/browse/KARAF-751
> Project: Karaf
> Issue Type: New Feature
> Components: karaf-osgi
> Affects Versions: 3.0.0
> Reporter: Ioannis Canellos
> Assignee: Ioannis Canellos
> Fix For: 3.1.0
>
> Attachments: Scheduler_20130430.patch, Scheduler_20130729.patch
>
>
> In many cases there is need to have recurring tasks run for a period of time.
> It would be great if Karaf provided some short of a TimerService that would
> allow the user to easily schedule task execution.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
