Package oracle.rules.sdk2.ruleset

Class Rule

java.lang.Object
oracle.rules.sdk2.dictionary.DictionaryObject
oracle.rules.sdk2.dictionary.DictionaryComponent<T>
oracle.rules.sdk2.ruleset.RuleComponent<T>
oracle.rules.sdk2.ruleset.RuleBase<T>
oracle.rules.sdk2.ruleset.RuleCommon<Rule>
oracle.rules.sdk2.ruleset.Rule
All Implemented Interfaces:
Serializable, Cloneable, Map<String,Object>, ActionContext, AutoBindingContext, VariableScope
public class Rule extends RuleCommon<Rule>
A Rule consists of a table of Patterns to be matched, and a table of Actions to be taken when a match occurs. See also RuleSet.

A Rule is structured as a set of nested tables. 

 Rule
 Pattern Table
 SimpleTest Table
 Action Table

E.g., The following rule has a PatternTable with 2 Patterns. Each pattern has one SimpleTest. The rule has an Action table with two actions. The second action has a parameter table with one parameter. 

 Rule myRule
 {
   if ((fact patternA && patternA.x == 1) &&
       (fact patternB && patternB.y = patternA.y))
   {
     retract(patternB);
     println(PatternB.y + "retracted");
   }
 }
The following applies to the Rule classes and to the nested classes it uses.

To be valid a Rule is required to have at least one Pattern but is not required to have any Actions.

On output, String properties can be accessed using specific getters, such as getName(), or generic getters, such as getProperty("name"). There are corresponding methods for accessing option lists for the properties and the selected option. See RuleComponent

On input, property values should be set back into the same instances. Use RuleDictionary.update(java.util.List<oracle.rules.sdk2.exception.SDKWarning>) to accept changes. On input, property values are always Strings.

Input events can be handled through use of specific methods on the classes or using theTableEditor class.

Validation is done when validate() is called rather than at set time.

See Also: