@NoImplement public interface ConfigurationComponentLocator
The location can be composed by many parts, each part separated by an slash.
The first part must be the name of the global element that contains the location. Location "myflow" indicates the global element with name myFlow.
Global elements that do not have a name cannot be referenced.
The following parts must be components contained within the global element. Location "myFlow/processors" indicates the processors part of the global element with name "myFlow"
Each part must be contained in the preceded component in the location. Location "myFlow/errorHandler/onErrors" indicates the onErrors components that are part of the errorHandler component which is also part of the "myFlow" global element.
When a component part has a collection of components, each component can be referenced individually with an index. THe first index is 0. Location "myFlow/processors/4" refers to the fifth processors inside the flow with name "myFlow"
When working with configuration templates such subflows or global error handlers there's no way to access the message processors that belong to them through this interface.
Modifier and Type | Field and Description |
---|---|
static String |
REGISTRY_KEY |
Modifier and Type | Method and Description |
---|---|
List<Component> |
find(ComponentIdentifier componentIdentifier)
Finds all the components with the given identifier within the artifact.
|
Optional<Component> |
find(Location location)
Finds a component in the configuration with the specified location.
|
List<ComponentLocation> |
findAllLocations()
Finds the locations of every component within the artifact.
|
static final String REGISTRY_KEY
Optional<Component> find(Location location)
location
- the location of the component.List<Component> find(ComponentIdentifier componentIdentifier)
componentIdentifier
- the component identifierList<ComponentLocation> findAllLocations()
This method may return locations for which there are no Component
found with find(ComponentIdentifier)
or
find(Location)
. This happens in the case when the parser knows a certain location exists but the component in that
location is not available (i.e.: is lazy)
ComponentLocation
s within the artifact.Copyright © 2018. All rights reserved.