Uploaded image for project: 'Weld'
  1. Weld
  2. WELD-2573

Async event notification should preserve TCCL

    Details

    • Type: Bug
    • Status: Resolved (View Workflow)
    • Priority: Major
    • Resolution: Done
    • Affects Version/s: 3.1.0.Final
    • Fix Version/s: 3.1.1.Final
    • Component/s: Events
    • Labels:
      None

      Description

      When firing async events, various executors can be used.
      In doing so, their TCCL changes and other technologies that may rely on it will fail (WFLY-11907). On WFLY, this also causes problem once you try to use CDI.current() as WFLY attempts to decide which Weld container belongs to that call based on TCCL (WFLY-11906).

      We can try and wrap each notification with privileged action that sets the TCCL to what it was originally and unsets it when done.

        Gliffy Diagrams

          Attachments

            Issue Links

              Activity

                People

                • Assignee:
                  manovotn Matěj Novotný
                  Reporter:
                  manovotn Matěj Novotný
                • Votes:
                  0 Vote for this issue
                  Watchers:
                  2 Start watching this issue

                  Dates

                  • Created:
                    Updated:
                    Resolved: