| Class and Description |
|---|
| Activation
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!
|
| 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.
|
| 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
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
The rule instance is created in the EVM for a rule specification.
|
| RuleSpecification
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.
|
| Scheduler.ISchedulerFactory
Factory interface for preparing a scheduler for a given executor.
|
| Class and Description |
|---|
| RuleInstance
The rule instance is created in the EVM for a rule specification.
|
| Class and Description |
|---|
| Activation
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. |
| RuleBase
An RuleBase is associated to an
EventRealm and
it is responsible for creating, managing and disposing rules in
the Rule Engine. |
| RuleSpecification
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.
|
| Class and Description |
|---|
| Activation
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. |
| Class and Description |
|---|
| Activation
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.
|
| ExecutionSchema
An execution schema is a special rule engine and a facade
for accessing the EVM.
|
| Job
A job represents an action that can be executed on an activation
if it is in the state defined by the job.
|
| 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.
|
| RuleSpecification
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.ISchedulerFactory
Factory interface for preparing a scheduler for a given executor.
|
| Class and Description |
|---|
| RuleInstance
The rule instance is created in the EVM for a rule specification.
|
| Class and Description |
|---|
| Activation
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. |
| CompositeJob |
| 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.
|
| Job
A job represents an action that can be executed on an activation
if it is in the state defined by the job.
|
| Class and Description |
|---|
| ActivationLifeCycle
A life cycle describes how the state of an activation changes
in response to an event.
|
| Class and Description |
|---|
| Activation
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. |
| RuleSpecification
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.
|
| Class and Description |
|---|
| Activation
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. |
| Class and Description |
|---|
| Executor
The executor is responsible for firing enabled activations of its ruleBase,
when its scheduler notifies it.
|
| Scheduler
The scheduler is used to define when the executor of a schema should
start its execution strategy.
|
| Scheduler.ISchedulerFactory
Factory interface for preparing a scheduler for a given executor.
|
| Class and Description |
|---|
| Job
A job represents an action that can be executed on an activation
if it is in the state defined by the job.
|
| Class and Description |
|---|
| ExecutionSchema
An execution schema is a special rule engine and a facade
for accessing the EVM.
|