[ https://issues.jboss.org/browse/CDI-587?page=com.atlassian.jira.plugin.sy... ] Romain Manni-Bucau edited comment on CDI-587 at 7/18/18 9:43 AM: ----------------------------------------------------------------- Since CDI 2 we could have a simple solution reusing RequestContextController and adding a method to be able to manipulate the context: {code} RequestContextController scope = controller.handler(); // do something // start a new thread or eq () -> { scope.activate(); try { /*...*/} finally { scope.deactivate(); } // }; {code} It would: 1. let to the caller the thread safety responsability 2. use some kind of reference counting to not destroy the scope too early (before all deactivate are called) was (Author: rmannibucau): Since CDI 2 we could have a simple solution reusing RequestContextController and adding a method to be able to manipulate the context: {code} RequestContextController scope = controller.handler(); // do something // start a new thread or eq () -> { scope.activate(); try { /*...*/} finally { scope.deactivate(); } // }; It would: 1. let to the caller the thread safety responsability 2. use some kind of reference counting to not destroy the scope too early (before all deactivate are called) -- This message was sent by Atlassian JIRA (v7.5.0#75005)