Index Changes
Page Difference

Difference between version and version     

Back to Fuji EIPCBR, or Fuji EIPCBR Info


At line 24 changed 1 line.
[when [ value | condition-identifier inline-rules-definition] to route-name ]*
[when [ value | condition-identifier inline-rules-definition] to [route-name | service-name] ]*
At line 40 changed 2 lines.
\\
There exists one configuration parameter: firstMatch. Default value is true. If set to false, the condition based rule matching will only trigger if a single rule is found to match. Otherwise if multiple rules match, or no rules match, the else clause will be selected.
\\ \\
There exists one configuration parameter: {{{match=first|last|unique}}}. Default value is {{{first}}}. In this case the first condition based rule that matches will trigger. If set to {{{last}}}, the last condition based rule that matches will trigger. If set to {{{unique}}}, the condition based rule matching will trigger only if a single rule is found to match. Otherwise, if multiple rules match, or no rules match, the else clause will be selected.
At line 47 added 1 line.
email "exception-service"
At line 53 changed 1 line.
else to "other-transaction"
else to "exception-service"
At line 59 added 1 line.
email "other-service"
At line 62 changed 1 line.
when "false" to "other-transaction
when "false" to "other-service"
At line 110 changed 1 line.
Another useful feature is a new property that controls the selection policy. By default, the selection policy is first match. Also, rules can be grouped and ordered within groups to control the evaluation order. The selection policy can be changed to unique match. In this instance it will trigger a rule only if it is the only rule that matches. In the case of multiple matches, the else clause will be selected if it exists. Otherwise, and error is returned.
Another useful feature is a new property that controls the selection policy. By default, the selection policy is first match. Also, rules can be grouped and ordered within groups to control the evaluation order. The selection policy can be changed to either last match or unique match. When last match is used, the last matching rule triggers, or the else if there is no match. When unique match is used, a rule triggers only if it is the only rule that matches. In the case of multiple matches, the else clause will be selected if it exists. Otherwise, an error is returned.
At line 112 changed 1 line.
Example of firstMatch property:
Example of match property:
At line 115 changed 1 line.
select any ("firstMatch=false") do
select any ("match=unique") do
At line 120 removed 3 lines.
If Value==5 and Time==now then the else clause will be triggered.
If firstMatch is not true then "service-a" would have been invoked.
At line 123 added 2 lines.
If Value==5 and Time==now then the else clause will be triggered.
If, in the above case, match is set to first then "service-a" would be invoked, and if match is set to last then "service-b" would be invoked.
G'day, Anonymous Guest

JSPWiki v2.4.100
[RSS]
« Home Index Changes Prefs
This page (revision-31) was last changed on 03-Nov-09 23:12 PM, -0800 by MarkWhite