<div dir="ltr">All,<div><br></div><div>I've started a PR for API changes to support starting/stopping the built in contexts, which you can find here: <a href="https://github.com/cdi-spec/cdi/pull/291/files">https://github.com/cdi-spec/cdi/pull/291/files</a></div><div><br></div><div>It's visibly based on what is in DeltaSpike's CDI Ctrl plus some of the external stuff (e.g. <a href="https://github.com/apache/deltaspike/blob/master/deltaspike/modules/scheduler/api/src/main/java/org/apache/deltaspike/scheduler/api/Scheduled.java#L40">https://github.com/apache/deltaspike/blob/master/deltaspike/modules/scheduler/api/src/main/java/org/apache/deltaspike/scheduler/api/Scheduled.java#L40</a> ) so I'd like to get some input.</div><div><br></div><div>I don't suspect that this will be an SE only feature, today I use programmatic context starting even while on an app server. Even though I'm not using whats provided in DS, it was identified as a clear cross cutting concern hence why there's an interceptor as well.</div><div><br></div><div>John</div></div>