[
https://issues.apache.org/jira/browse/DELTASPIKE-665?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14087127#comment-14087127
]
John D. Ament commented on DELTASPIKE-665:
------------------------------------------
I think I've found the pattern. Anytime the caller is using some kind of
thread pool, this issue pops up. When you use manually created threads, the
current approach works fine.
I'm not sure the differences yet, but it seems to be mostly used by servlet
containers, which makes sense based on IO workers.
> Add utility method to always get new context control.
> -----------------------------------------------------
>
> Key: DELTASPIKE-665
> URL: https://issues.apache.org/jira/browse/DELTASPIKE-665
> Project: DeltaSpike
> Issue Type: Improvement
> Components: CdiControl
> Affects Versions: 1.0.0
> Reporter: John D. Ament
> Assignee: John D. Ament
> Fix For: 1.0.2
>
>
> While working on DELTASPIKE-653 I got tripped up on the fact that the context
> controller returned by the CdiContainer is one specific to the container
> object.
> Ideally, if we expect the SE features to be available without core, we should
> add a method to the container that always gives back a new instance of the
> controller. Certainlly, internally the controller can be used by the
> container to start the primary contexts, but for consumers we need to
> manually start a context.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
