Class DefaultControlExpressionParser
java.lang.Object
org.citrusframework.validation.matcher.DefaultControlExpressionParser
- All Implemented Interfaces:
ControlExpressionParser
Default implementation of control expression parser.
- Since:
- 2.5
- Author:
- Martin Maher
-
Field Summary
Fields inherited from interface org.citrusframework.validation.matcher.ControlExpressionParser
DEFAULT_DELIMITER -
Constructor Summary
Constructors -
Method Summary
Modifier and TypeMethodDescriptionextractControlValues(String controlExpression, Character delimiter) Some validation matchers can optionally contain one or more control values nested within a control expression.
-
Constructor Details
-
DefaultControlExpressionParser
public DefaultControlExpressionParser()
-
-
Method Details
-
extractControlValues
Description copied from interface:ControlExpressionParserSome validation matchers can optionally contain one or more control values nested within a control expression. Matchers implementing this interface should take care of extracting the individual control values from the expression.
For example, theorg.citrusframework.validation.matcher.core.DateRangeValidationMatcherexpects between 2 to 3 control values (dateFrom, dateTo and optionally datePattern) to be provided. It's ControlExpressionParser would be expected to parse the control expression, returning each individual control value for each nested parameter found within the control expression.- Specified by:
extractControlValuesin interfaceControlExpressionParser- Parameters:
controlExpression- the control expression to be parseddelimiter- the delimiter to use. When NULL theControlExpressionParser.DEFAULT_DELIMITERis assumed.- Returns:
-