Expand my Community achievements bar.

Don’t miss the AEM Skill Exchange in SF on Nov 14—hear from industry leaders, learn best practices, and enhance your AEM strategy with practical tips.
SOLVED

Apache Sling Scheduler + OSGI annotations on 6.1

Avatar

Level 2
1 Accepted Solution

Avatar

Correct answer by
Level 10

This should be supported if you setup the POM dependencies, etc. This Github project was build for AEM. There is no reason why these annotations would not work.

View solution in original post

2 Replies

Avatar

Correct answer by
Level 10

This should be supported if you setup the POM dependencies, etc. This Github project was build for AEM. There is no reason why these annotations would not work.

Avatar

Level 2

Ok, it does work. My class has a configuration to configure property "scheduler.period". The mistake I made was that I had the following properties as part of the @Component annotation

"scheduler.concurrent=false",
"scheduler.immediate=true",
"scheduler.runOn=SINGLE"

So apparently you cannot spread scheduler properties between a config class and the Component annotation. But then how can you make those 3 properties private i.e. non-configurable while still have the ability to configure property "scheduler.period"?