Interface that defines the main entry points of EVM based execution.
Factory interface for preparing a scheduler for a given executor.
A life cycle describes how the state of an activation changes in response to an event.
Sole purpose is the management all and ordering of enabled activations!
Iterator that iterates through the elements of a
A context is an associative store that is accessible during the execution of the EVM, and thus usable by the Sceduler, Executor, RuleBase, Rule Instances, Activations and Jobs.
This class is responsible for handling notifications sent by rule instances when an activation changes state.
Utility class for creating new rule engines and execution schemes.
An execution schema is a special rule engine and a facade for accessing the EVM.
A job represents an action that can be executed on an activation if it is in the state defined by the job.
An RuleBase is associated to an
A rule engine is a facade for accessing the EVM, it allows the retrieval of all activations and filtered access by state, specification or both.
The rule instance is created in the EVM for a rule specification.
A rule specification specifies how the set of individual rule activations and their states are computed, what jobs (operations) to perform when an activation is executed, and how events affect the state of the activations based on a life-cycle model.
The scheduler is used to define when the executor of a schema should start its execution strategy.