anchor.diff:  }
   ---------------------------------------------------------------------------------
   
  -In such Quartz-jobs CDI based dependency-injection is enabled.
  +As an alternative it's possible to annotate an implementation of `java.lang.Runnable` (since DeltaSpike v1.5.3):
  +
  +.Scheduled task based on java.lang.Runnable
  +[source,java]
  +---------------------------------------------------------------------------------
  +@Scheduled(cronExpression = "0 0/10 * * * ?")
  +public class CdiAwareRunnableJob implements java.lang.Runnable
  +{
  +    @Inject
  +    private MyService service;
  +
  +    @Override
  +    public void run()
  +    {
  +        //...
  +    }
  +}
  +---------------------------------------------------------------------------------
  +
  +Behind the scenes DeltaSpike registers an adapter for Quartz which just delegates to the `run`-method once the adapter gets called by Quartz.
  +Technically you end up with almost the same, just with a reduced API for implementing (all) your scheduled jobs.
  +Therefore the main difference is that your code is independent of Quartz-classes.
  +However, you need to select `org.quartz.Job` or `java.lang.Runnable` for all your scheduled-tasks, bot not both!
  +
  +In such scheduled-tasks CDI based dependency-injection is enabled.
   Furthermore, the request- and session-scope get started (and stopped)
   per job-execution. Therefore, the container-control module (of
   DeltaSpike) is required. That can be controlled via
  
positive.code: 
  With 'false' for `@Scheduled#onStartup`, it is even possible to
  schedule/install jobs dynamically.
  
  .Example
  [source,java]
  
negative.code: 
  [source,java]
  ---------------------------------------------------------------------------------
  public class DelegatingJobRunnableAdapter implements java.lang.Runnable
  {
      @Resource
      private ManagedExecutorService managedExecutorService;
  
      @Override
      public void run()
      {
          Class<? extends Runnable> jobClass =
              ClassUtils.tryToLoadClassForName(context.getJobDetail().getKey().getName(), Runnable.class);
  