[
https://issues.apache.org/jira/browse/DELTASPIKE-651?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14047001#comment-14047001
]
John D. Ament commented on DELTASPIKE-651:
------------------------------------------
If you leave the default annotation in place (creates
SessionScope/RequestScope) that's two extra active contexts. While they may be
fast here, this optimization:
- Removes SE specific modules from the app server.
- Avoids creating two extra contexts by default.
- Doesn't muck with the default quartz job listeners, not needing the call back.
> Support for disabling scope activation globally
> -----------------------------------------------
>
> Key: DELTASPIKE-651
> URL: https://issues.apache.org/jira/browse/DELTASPIKE-651
> Project: DeltaSpike
> Issue Type: Improvement
> Components: Scheduler
> Affects Versions: 1.0.0
> Reporter: John D. Ament
> Assignee: John D. Ament
> Fix For: 1.0.1
>
>
> The Scheduler always attempts to start scopes listed. For basic use cases,
> if my job is ApplicationScoped that can be assumed to be started for the
> scheduler to operate. We should support a configuration parameter, more of a
> performance optimization, to not require the scopes to be activated.
> You can add deltaspike.scheduler.start_scopes_for_jobs to your ConfigSource
> with the value of false, and scopes won't be attempted to be started.
> As a result, the Scheduler now has an optional dependency on CDI SE/CDI
> Context Control module as well, which will help with adoption.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
