[ https://issues.redhat.com/browse/WFLY-11808?page=com.atlassian.jira.plugi... ] Cheng Fang edited comment on WFLY-11808 at 8/10/20 12:20 AM: ------------------------------------------------------------- We could pass {{EEModuleDescription}} to {{BatchEnvironmentService}} instead of {{JobOperatorService}}. In {{BatchEnvironmentService}} when we create {{NamespaceContextHandle}}, we can just use the selector from {{EEModuleDescription}}, by changing {{NamespaceContextHandle}} constructor to take the deployment's namespace selector, without using the one from the thread. This should work for job executions started from either application, or from management. This will allow us to keep the naming context switch logic inside {{NamespaceContextHandle}}. This class sets the correct contextual objects on the thread that will be running batch job tasks, and reset it from the thread when it's done processing batch tasks. was (Author: cfang): We could pass {{EEModuleDescription}} to {{BatchEnvironmentService}} instead of {{JobOperatorService}}. In {{BatchEnvironmentService}} when we create {{NamespaceContextHandle}}, we can just use the selector from {{EEModuleDescription}}, by changing {{NamespaceContextHandle}} constructor to take the deployment's namespace selector, without using the one from the thread. This should work for job executions started from either application, or from management. -- This message was sent by Atlassian Jira (v7.13.8#713008)