Changes for page Asynchronous Routing
Last modified by Danniar Firdausy on 2024/09/04 09:01
From version 23.1
edited by Erik Bakker
on 2022/08/15 08:07
on 2022/08/15 08:07
Change comment:
There is no comment for this version
To version 32.1
edited by Carlijn Kokkeler
on 2022/10/05 12:24
on 2022/10/05 12:24
Change comment:
There is no comment for this version
Summary
-
Page properties (2 modified, 0 added, 0 removed)
Details
- Page properties
-
- Author
-
... ... @@ -1,1 +1,1 @@ 1 -XWiki. ebakker1 +XWiki.CarlijnKokkeler - Content
-
... ... @@ -34,9 +34,12 @@ 34 34 35 35 The best practice for setting up your asynchronous routing process is to use one SpEL expression that determines to which offramp queues a messages needs to be routed. 36 36 The SpEL expression looks as follows: 37 + 38 +{{code language=<xml>}} 39 +code: 40 + headers.{technicalnameofproject}\_targetSystem.split(',').![#this.trim()+#root.headers.{technicalnameofproject}_messageType] 41 +{{/code}} 37 37 38 -headers.{technicalnameofproject}\_targetSystem.split(',').![#this.trim()+#root.headers.{technicalnameofproject}_messageType] 39 - 40 40 This SpEL expression does the following things: 41 41 42 42 * It looks for the header called {technicalnameofproject}\_targetSystem and will split each entry based on the separator (a comma)