Details

    • Type: Epic
    • Status: Open (View Workflow)
    • Priority: Major
    • Resolution: Unresolved
    • Affects Version/s: 1.2.Final
    • Fix Version/s: None
    • Component/s: Contexts
    • Labels:
      None
    • Epic Name:
      Context propagation
    • Epic Status:
      To Do

      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

        Gliffy Diagrams

          Attachments

            Activity

              People

              • Assignee:
                Unassigned
                Reporter:
                rmannibucau Romain Manni-Bucau
              • Votes:
                2 Vote for this issue
                Watchers:
                9 Start watching this issue

                Dates

                • Created:
                  Updated: