Index Changes
Page Difference

Difference between version and version     

Back to Integration Flow Language Route Keyword, or Integration Flow Language Route Keyword Info


At line 3 removed 1 line.
!!route keyword
At line 4 added 2 lines.
!!route keyword
(Back to [Integration Flow Language Specification])
At line 6 changed 8 lines.
* [from|Integration Flow Language From Keyword] - pipe and filter pattern
* [to|Integration Flow Language To Keyword] - pipe and filter pattern
* [broadcast|Integration Flow Language Broadcast Keyword] - scatter-gather pattern
* [split|FujiEIPSplit] - splitter pattern
* [aggregate|FujiEIPAggregate] - aggregator pattern / scatter-gather pattern
* [select|FujiEIPCBR] - content-based router
* [filter|FujiEIPMessageFilter] - message filter pattern
* [tee|FujiEIPWireTap] - wire tap pattern
* [from|Integration Flow Language From Keyword]
** pipe and filter pattern
* [to|Integration Flow Language To Keyword]
** pipe and filter pattern
* [broadcast|Integration Flow Language Broadcast Keyword]
** scatter-gather pattern
* [split|FujiEIPSplit]
** splitter pattern
* [aggregate|FujiEIPAggregate]
** aggregator pattern / scatter-gather pattern
* [select|FujiEIPCBR]
** content-based router
* [filter|FujiEIPMessageFilter]
** message filter pattern
* [tee|FujiEIPWireTap]
** wire tap pattern
At line 15 changed 3 lines.
!Basic syntax
!!Basic syntax
At line 27 changed 1 line.
!Alternate simplified syntax
!!Alternate simplified syntax
At line 34 changed 2 lines.
!route With Composite Constructs
Adding composite constructs to the route such as broadcast:
!!route With Composite Constructs
Instead of the simple "to" of the pipe-and-filter pattern, the other EIP keywords can be inserted. For example adding a broadcast to the route:
At line 67 added 20 lines.
!!Named route
Routes can be named so they can be called and included in other routes. It can be thought of as defining a re-usable endpoint, breaking the routing up into re-usable pieces. Named routes do not have a "from", implicitly messages come from routing messages to that route name/endpoint.
{{{
route "<my-route-name>" do
to "<logical filter name 1>" # occurs 0 or more times
to "<logical service name>" # occurs once
end
}}}
The named route "endpoint" can be referenced in the other IFL construct like any other service, i.e. to call the above one or more other routes could state (assuming a name of my-route-name):
{{{
route do
from "my-trasnport"
to "some-transform"
to "my-route-name"
end
}}}
G'day, Anonymous Guest

JSPWiki v2.4.100
[RSS]
« Home Index Changes Prefs
This page (revision-13) was last changed on 10-Dec-09 10:19 AM, -0800 by AndiEgloff