[cdi-dev] [JBoss JIRA] (CDI-587) Propose a way to propagate an existing context

[Romain Manni-Bucau (JIRA)]

     [ https://issues.jboss.org/browse/CDI-587?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Romain Manni-Bucau updated CDI-587:
-----------------------------------
    Description: 
The overall idea is to ensure that it is not cause the code becomes asynchronous/reactive/... that we loose the instances or get another context.

An example is starting an AsyncContext in a servlet.

One proposal is to add a flag to ask for propagation of the context in async managed threads: @RequestScoped(inherited = true) which would reuse the same instances for these "new" threads.

Note however this issue is not only bound to servlets even if it is the easiest example.

The original thread disucssion on the list: http://cdi-development-mailing-list.1064426.n5.nabble.com/RequestScope-Life-Cycle-td5712701.html

  was:
The overall idea is to ensure that it is not cause the code becomes asynchronous/reactive/... that we loose the instances or get another context.

An example is starting an AsyncContext in a servlet.

One proposal is to add a flag to ask for propagation of the context in async managed threads: @RequestScoped(inherited = true) which would reuse the same instances for these "new" threads.

Note however this issue is not only bound to servlets even if it is the easiest example.



> Propose a way to propagate an existing context
> ----------------------------------------------
>
>                 Key: CDI-587
>                 URL: https://issues.jboss.org/browse/CDI-587
>             Project: CDI Specification Issues
>          Issue Type: Epic
>          Components: Contexts
>    Affects Versions: 1.2.Final
>            Reporter: Romain Manni-Bucau
>
> The overall idea is to ensure that it is not cause the code becomes asynchronous/reactive/... that we loose the instances or get another context.
> An example is starting an AsyncContext in a servlet.
> One proposal is to add a flag to ask for propagation of the context in async managed threads: @RequestScoped(inherited = true) which would reuse the same instances for these "new" threads.
> Note however this issue is not only bound to servlets even if it is the easiest example.
> The original thread disucssion on the list: http://cdi-development-mailing-list.1064426.n5.nabble.com/RequestScope-Life-Cycle-td5712701.html



--
This message was sent by Atlassian JIRA
(v6.4.11#64026)