From 9c5b074f1f71321b0fc73993d67a444d7073e031 Mon Sep 17 00:00:00 2001 From: Artem Bilan Date: Mon, 28 Nov 2011 17:14:47 +0200 Subject: [PATCH] INT-2274: Manual: Limitation of usage scoped beans in the command scripts for Groovy Control Bus. --- docs/src/reference/docbook/groovy.xml | 10 ++++++++-- 1 file changed, 8 insertions(+), 2 deletions(-) diff --git a/docs/src/reference/docbook/groovy.xml b/docs/src/reference/docbook/groovy.xml index 4378ee37bb..10b73326f2 100644 --- a/docs/src/reference/docbook/groovy.xml +++ b/docs/src/reference/docbook/groovy.xml @@ -80,9 +80,15 @@ customizes it with a GroovyObjectCustomizer, and then executes it. The Control Bus' customizer exposes all the beans in the application context that are annotated with @ManagedResource, implement Spring's - Lifecycleinterface or extend Spring's CustomizableThreadCreator base class + Lifecycle interface or extend Spring's CustomizableThreadCreator base class (e.g. several of the TaskExecutor and TaskScheduler implementations). - + + + Be careful about using managed beans with custom scopes (e.g. 'request') in the Control Bus' command scripts, especially + inside async message flow. If The Control Bus' customizer can't expose a bean + from the application context, it skips BeanCreationException and goes on to other beans. + + If you need to further customize the Groovy objects, you can also provide a reference to a bean that implements org.springframework.scripting.groovy.GroovyObjectCustomizer via