Class and Description |
---|
BaseSpec
BaseSpec interface that provide a way to get its own pathElement and an apply(...)
method to process the spec using input, output and context
|
Class and Description |
---|
BaseSpec
BaseSpec interface that provide a way to get its own pathElement and an apply(...)
method to process the spec using input, output and context
|
OrderedCompositeSpec
An ordered composite spec denotes the spec will have Literal and Computed children that
must be Ordered Spec, which should be subject to sorting to before applying any of the
determined execution strategies!
This is not enforced directly, but these interface methods ensure the executionStrategy
gets the literal and computed children lists to process its exec strategy
The order is provided by a Map
|
Class and Description |
---|
BaseSpec
BaseSpec interface that provide a way to get its own pathElement and an apply(...)
method to process the spec using input, output and context
|
Class and Description |
---|
SpecBuilder
Factory class that provides a factory method create(...) that takes itself
as argument to specify how to handle child specs
|
Class and Description |
---|
BaseSpec
BaseSpec interface that provide a way to get its own pathElement and an apply(...)
method to process the spec using input, output and context
|
OrderedCompositeSpec
An ordered composite spec denotes the spec will have Literal and Computed children that
must be Ordered Spec, which should be subject to sorting to before applying any of the
determined execution strategies!
This is not enforced directly, but these interface methods ensure the executionStrategy
gets the literal and computed children lists to process its exec strategy
The order is provided by a Map
|
Class and Description |
---|
SpecBuilder
Factory class that provides a factory method create(...) that takes itself
as argument to specify how to handle child specs
|
Class and Description |
---|
BaseSpec
BaseSpec interface that provide a way to get its own pathElement and an apply(...)
method to process the spec using input, output and context
|
OrderedCompositeSpec
An ordered composite spec denotes the spec will have Literal and Computed children that
must be Ordered Spec, which should be subject to sorting to before applying any of the
determined execution strategies!
This is not enforced directly, but these interface methods ensure the executionStrategy
gets the literal and computed children lists to process its exec strategy
The order is provided by a Map
|
SpecBuilder
Factory class that provides a factory method create(...) that takes itself
as argument to specify how to handle child specs
|