This is an automated email from the ASF dual-hosted git repository.
lukaszlenart pushed a commit to branch WW-5289-executor
in repository https://gitbox.apache.org/repos/asf/struts-site.git
commit 8101dd218eeed89c449c7dc4c526f0af113b8aae
Author: Lukasz Lenart <lukaszlen...@apache.org>
AuthorDate: Sun Mar 26 14:15:45 2023 +0200
WW-5289 Updates docs about new extension point
---
source/core-developers/execute-and-wait-interceptor.md | 11 ++++++-----
1 file changed, 6 insertions(+), 5 deletions(-)
diff --git a/source/core-developers/execute-and-wait-interceptor.md
b/source/core-developers/execute-and-wait-interceptor.md
index 6cc90e21d..fed41ed50 100644
--- a/source/core-developers/execute-and-wait-interceptor.md
+++ b/source/core-developers/execute-and-wait-interceptor.md
@@ -67,18 +67,19 @@ process extension, extend `ExecuteAndWaitInterceptor` and
implement the `getNewB
## Using ExecutorProvider
-Since Struts 6.1.1 it is possible to use your own `ExecutorProvider` to run
_background tasks_. To use your own executor
+Since Struts 6.2.0 it is possible to use your own `ExecutorProvider` to run
_background tasks_. To use your own executor
you must implement interface
`org.apache.struts2.interceptor.exec.ExecutorProvider` and install the bean
using `struts.xml`
like follows:
```xml
-<bean type="org.apache.struts2.interceptor.exec.ExecutorProvider"
+<bean type="org.apache.struts2.interceptor.exec.ExecutorProvider"
name="myExecutor"
class="com.company.MyExecutorProvider"/>
-```
-Please take a look into example implementation in the Showcase App.
+<constant name="struts.executor.provider" value="myExecutor"/>
+```
-If no custom executor is defined, Struts will use
`org.apache.struts2.interceptor.exec.StrutsExecutorProvider` by default.
+Please take a look into example implementation in the Showcase App. If no
custom executor has been defined,
+Struts will use `org.apache.struts2.interceptor.exec.StrutsExecutorProvider`
by default.
## Examples
