| Interface | Description |
|---|---|
| Scheduler.ISchedulerFactory |
Factory interface for preparing a scheduler for a given executor.
|
| Class | Description |
|---|---|
| Activation<EventAtom> |
An
Activation is a created for a RuleInstance when the preconditions (LHS) are fully satisfied with
some domain model elements and the instance becomes eligible for execution. |
| ActivationLifeCycle |
A life cycle describes how the state of an activation changes
in response to an event.
|
| Agenda |
Sole purpose is the management all and ordering of enabled activations!
|
| CompositeJob<EventAtom> | |
| Context |
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.
|
| EventDrivenVM |
Utility class for creating new rule engines and execution schemes.
|
| ExecutionSchema |
An execution schema is a special rule engine and a facade
for accessing the EVM.
|
| Executor |
The executor is responsible for firing enabled activations of its ruleBase,
when its scheduler notifies it.
|
| Job<EventAtom> |
A job represents an action that can be executed on an activation
if it is in the state defined by the job.
|
| RuleBase |
An RuleBase is associated to an
EventRealm and
it is responsible for creating, managing and disposing rules in
the Rule Engine. |
| RuleEngine |
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.
|
| RuleInstance<EventAtom> |
The rule instance is created in the EVM for a rule specification.
|
| RuleSpecification<EventAtom> |
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.
|
| Scheduler |
The scheduler is used to define when the executor of a schema should
start its execution strategy.
|