diff --git a/spring-integration-reference/src/router.xml b/spring-integration-reference/src/router.xml index afac6e2ce1..3f6ba57d26 100644 --- a/spring-integration-reference/src/router.xml +++ b/spring-integration-reference/src/router.xml @@ -123,7 +123,7 @@ The "router" element provides a simple way to connect a router to an input channel, and also accepts the optional default output channel. The "ref" may provide the bean name to one of the implementations described - above or custom Router (MessageHandler) implementations: + above or a custom Router implementation (extending AbstractMessageRouter): @@ -136,16 +136,20 @@ "ref" may be combined with an explicit "method" name. When specifying a "method", the same behavior applies as described in the @Router annotation section below. ]]> - Using a "ref" attribute is generally recommended if custom router handler implementation can be reused in other <router> definitions. However -if custom router handler implementation has to be scoped to a concrete definition of the <router>, starting with v1.0.3, Spring Integration supports -inner bean definitions for custom router handlers within the <router> element: + Using a "ref" attribute is generally recommended if the custom router implementation can be reused in other + <router> definitions. However if the custom router implementation should be scoped to a + concrete definition of the <router>, starting with v1.0.3, Spring Integration supports inner + bean definitions for custom routers within the <router> element: ]]> - - - Using both "ref" attribute and inner handler definition in the same <router> configuration is not allowed, as it creates an ambiguous condition and will result in Exception being thrown - + + + + Using both the "ref" attribute and an inner handler definition in the same <router> configuration + is not allowed, as it creates an ambiguous condition and will result in Exception being thrown. + +