You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: modules/ROOT/pages/rest-validator-extension.adoc
+3-3Lines changed: 3 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -5,7 +5,7 @@ endif::[]
5
5
6
6
The REST validator extension enables you to perform schema validations that use a RAML or OAS specification against the attributes of a request. Additionally, the extension adds default values to attributes, if they are already not set in the request.
7
7
8
-
Unless otherwise noted, this documentation applies exclusively to REST validator extension v2.x. To use the REST validator extension in your Mule artifact, such as a Mule runtime engine (Mule) application XML, you must:
8
+
Unless otherwise noted, this documentation applies only to REST validator extension v2.x. To use the REST validator extension in your Mule artifact, such as a Mule runtime engine (Mule) application XML, you must:
9
9
10
10
. <<include-dependency,Include the dependency in your pom.xml file>>.
11
11
. <<add-namespace-and-schema,Add the namespace and schema to your Mule artifact>>.
@@ -97,7 +97,7 @@ If the request does not violate the defined schema, the validation ends successf
97
97
98
98
*Error Types*
99
99
100
-
The ‘validate-request’ operation might raise different errors if a problem occurs when retrieving a file or if the validation does not end successfully:
100
+
The `validate-request` operation might raise different errors if a problem occurs when retrieving a file or if the validation does not end successfully:
101
101
102
102
* `REST-VALIDATOR:BAD_REQUEST`
103
103
+
@@ -143,7 +143,7 @@ If you must use the console operation, set this property to `true`. The default
143
143
If you are using a REST validator version that is later than 2.0.0, use the `keepRamlBaseUri` attribute. | No
144
144
| `queryParamsStrictValidation` | Validates whether all the query parameters in the request are defined in the specification file. If some of the parameters are not specified, the validation fails. The default value is `false`. | No
145
145
| `headersStrictValidation` | Validates whether all the required headers defined in the specification are defined in the request. If some of the parameters are not specified, the validation fails. The default value is `false`. | No
146
-
| attributesDeserializingStrategies` | Allows parsing of the HTTP headers that contain an array of values that are separated by commas. | No
146
+
| `attributesDeserializingStrategies` | Allows parsing of the HTTP headers that contain an array of values that are separated by commas. | No
147
147
|===
148
148
149
149
== REST Validator and APIkit Compatibility Reference
0 commit comments