Move XSD to correct folder

Author: davsclaus

…a/spring-xml/camel-spring-xml-4.13.0.xsd …ic/schema/spring/camel-spring-4.13.0.xsdstatic/schema/spring-xml/camel-spring-xml-4.13.0.xsd renamed to static/schema/spring/camel-spring-4.13.0.xsd static/schema/spring-xml/camel-spring-xml-4.13.0.xsd renamed to static/schema/spring/camel-spring-4.13.0.xsd

@@ -414,7 +414,7 @@ Rest DELETE command
     <xs:annotation>
       <xs:documentation xml:lang="en">
 <![CDATA[
-Handle DFDL (Data Format Description Language) transformation.
+Transforms fixed format data such as EDI message from/to XML using a Data Format Description Language (DFDL).
 ]]>
       </xs:documentation>
     </xs:annotation>
@@ -574,20 +574,20 @@ Flatpack library.
       </xs:documentation>
     </xs:annotation>
   </xs:element>
-  <xs:element name="from" type="tns:fromDefinition">
+  <xs:element name="fory" type="tns:foryDataFormat">
     <xs:annotation>
       <xs:documentation xml:lang="en">
 <![CDATA[
-Act as a message source as input to a route
+Serialize and deserialize messages using Apache Fory
 ]]>
       </xs:documentation>
     </xs:annotation>
   </xs:element>
-  <xs:element name="fury" type="tns:furyDataFormat">
+  <xs:element name="from" type="tns:fromDefinition">
     <xs:annotation>
       <xs:documentation xml:lang="en">
 <![CDATA[
-Serialize and deserialize messages using Apache Fury
+Act as a message source as input to a route
 ]]>
       </xs:documentation>
     </xs:annotation>
@@ -2976,6 +2976,15 @@ is often named build (used by default). Default value: build
         <xs:documentation xml:lang="en">
 <![CDATA[
 The script language to use when using inlined script for creating the bean, such as groovy, java, javascript etc.
+]]>
+        </xs:documentation>
+      </xs:annotation>
+    </xs:attribute>
+    <xs:attribute name="scriptPropertyPlaceholders" type="xs:string">
+      <xs:annotation>
+        <xs:documentation xml:lang="en">
+<![CDATA[
+Whether the script should support using Camel property placeholder syntax {{ }}. Default value: true
 ]]>
         </xs:documentation>
       </xs:annotation>
@@ -3541,7 +3550,9 @@ size is 10. Default value: 10
             <xs:documentation xml:lang="en">
 <![CDATA[
 Whether to throw io.github.resilience4j.circuitbreaker.CallNotPermittedException when the call is rejected due circuit
-breaker is half open or open. Default value: false
+breaker is half open (and was not attempted but rejected immediately) or open (always rejected). This option is only in
+use when there is NOT a fallback configured on the circuit breaker. When there is a fallback then the fallback is always
+executed and CallNotPermittedException is not thrown. Default value: false
 ]]>
             </xs:documentation>
           </xs:annotation>
@@ -4466,7 +4477,7 @@ Ignore the invalidate endpoint exception when try to create a producer with that
           <xs:annotation>
             <xs:documentation xml:lang="en">
 <![CDATA[
-Whether to allow components to optimise enricher if they are org.apache.camel.spi.SendDynamicAware . Default value: true
+Whether to allow components to optimise enricher if they are org.apache.camel.spi.SendDynamicAware. Default value: true
 ]]>
             </xs:documentation>
           </xs:annotation>
@@ -6212,7 +6223,7 @@ messages, or any custom logic needed before the looping executes.
             <xs:element ref="tns:fhirJson"/>
             <xs:element ref="tns:fhirXml"/>
             <xs:element ref="tns:flatpack"/>
-            <xs:element ref="tns:fury"/>
+            <xs:element ref="tns:fory"/>
             <xs:element ref="tns:grok"/>
             <xs:element ref="tns:gzipDeflater"/>
             <xs:element ref="tns:hl7"/>
@@ -7532,7 +7543,7 @@ References to a custom parser factory to lookup in the registry.
       </xs:extension>
     </xs:complexContent>
   </xs:complexType>
-  <xs:complexType name="furyDataFormat">
+  <xs:complexType name="foryDataFormat">
     <xs:complexContent>
       <xs:extension base="tns:dataFormat">
         <xs:sequence/>
@@ -7558,16 +7569,16 @@ Whether to require register classes. Default value: true
           <xs:annotation>
             <xs:documentation xml:lang="en">
 <![CDATA[
-Whether to use the threadsafe fury. Default value: true
+Whether to use the threadsafe Fory. Default value: true
 ]]>
             </xs:documentation>
           </xs:annotation>
         </xs:attribute>
-        <xs:attribute name="allowAutoWiredFury" type="xs:string">
+        <xs:attribute name="allowAutoWiredFory" type="xs:string">
           <xs:annotation>
             <xs:documentation xml:lang="en">
 <![CDATA[
-Whether to auto-discover Fury from the registry. Default value: true
+Whether to auto-discover Fory from the registry. Default value: true
 ]]>
             </xs:documentation>
           </xs:annotation>
@@ -10578,12 +10589,12 @@ recommended to use a timeout value. Default value: -1
 Sets the maximum size used by the org.apache.camel.spi.ConsumerCache which is used to cache and reuse consumers when
 uris are reused. Beware that when using dynamic endpoints then it affects how well the cache can be utilized. If each
 dynamic endpoint is unique then its best to turn off caching by setting this to -1, which allows Camel to not cache both
-the producers and endpoints; they are regarded as prototype scoped and will be stopped and discarded after use. This
-reduces memory usage as otherwise producers/endpoints are stored in memory in the caches. However if there are a high
-degree of dynamic endpoints that have been used before, then it can benefit to use the cache to reuse both producers and
+the consumers and endpoints; they are regarded as prototype scoped and will be stopped and discarded after use. This
+reduces memory usage as otherwise consumers/endpoints are stored in memory in the caches. However, if there are a high
+degree of dynamic endpoints that have been used before, then it can benefit to use the cache to reuse both consumers and
 endpoints and therefore the cache size can be set accordingly or rely on the default size (1000). If there is a mix of
 unique and used before dynamic endpoints, then setting a reasonable cache size can help reduce memory usage to avoid
-storing too many non frequent used producers.
+storing too many non-frequent used consumers.
 ]]>
             </xs:documentation>
           </xs:annotation>
@@ -10592,7 +10603,7 @@ storing too many non frequent used producers.
           <xs:annotation>
             <xs:documentation xml:lang="en">
 <![CDATA[
-Ignore the invalidate endpoint exception when try to create a producer with that endpoint. Default value: false
+Ignore the invalidate endpoint exception when try to create a consumer with that endpoint. Default value: false
 ]]>
             </xs:documentation>
           </xs:annotation>
@@ -10601,7 +10612,7 @@ Ignore the invalidate endpoint exception when try to create a producer with that
           <xs:annotation>
             <xs:documentation xml:lang="en">
 <![CDATA[
-Whether to allow components to optimise if they are org.apache.camel.spi.SendDynamicAware . Default value: true
+Whether to allow components to optimise if they are org.apache.camel.spi.PollDynamicAware. Default value: true
 ]]>
             </xs:documentation>
           </xs:annotation>
@@ -13197,6 +13208,15 @@ Sets the maximum number of tokens on each segment.
             <xs:documentation xml:lang="en">
 <![CDATA[
 Sets the maximum number of tokens that can overlap in each segment.
+]]>
+            </xs:documentation>
+          </xs:annotation>
+        </xs:attribute>
+        <xs:attribute name="modelName" type="xs:string" use="required">
+          <xs:annotation>
+            <xs:documentation xml:lang="en">
+<![CDATA[
+Sets the model name.
 ]]>
             </xs:documentation>
           </xs:annotation>
@@ -13480,7 +13500,7 @@ To type used as a target data type in the transformation.
             <xs:element ref="tns:fhirJson"/>
             <xs:element ref="tns:fhirXml"/>
             <xs:element ref="tns:flatpack"/>
-            <xs:element ref="tns:fury"/>
+            <xs:element ref="tns:fory"/>
             <xs:element ref="tns:grok"/>
             <xs:element ref="tns:gzipDeflater"/>
             <xs:element ref="tns:hl7"/>
@@ -13761,6 +13781,15 @@ cool stuff.
           <xs:documentation xml:lang="en">
 <![CDATA[
 Allows to configure custom CORS headers.
+]]>
+          </xs:documentation>
+        </xs:annotation>
+      </xs:element>
+      <xs:element maxOccurs="unbounded" minOccurs="0" name="validationLevels" type="tns:restPropertyDefinition">
+        <xs:annotation>
+          <xs:documentation xml:lang="en">
+<![CDATA[
+Allows to configure custom validation levels when using camel-openapi-validator with client request/response validator.
 ]]>
           </xs:documentation>
         </xs:annotation>
@@ -13953,6 +13982,18 @@ returns HTTP Status 415 if validation error. 2) Accept header matches what the R
 406 if validation error. 3) Missing required data (query parameters, HTTP headers, body); returns HTTP Status 400 if
 validation error. 4) Parsing error of the message body (JSon, XML or Auto binding mode must be enabled); returns HTTP
 Status 400 if validation error. Default value: false
+]]>
+        </xs:documentation>
+      </xs:annotation>
+    </xs:attribute>
+    <xs:attribute name="clientResponseValidation" type="xs:string">
+      <xs:annotation>
+        <xs:documentation xml:lang="en">
+<![CDATA[
+Whether to check what Camel is returning as response to the client: 1) Status-code and Content-Type matches Rest DSL
+response messages. 2) Check whether expected headers is included according to the Rest DSL repose message headers. 3) If
+the response body is JSon then check whether its valid JSon. Returns 500 if validation error detected. Default value:
+false
 ]]>
         </xs:documentation>
       </xs:annotation>
@@ -14124,6 +14165,18 @@ returns HTTP Status 415 if validation error. 2) Accept header matches what the R
 406 if validation error. 3) Missing required data (query parameters, HTTP headers, body); returns HTTP Status 400 if
 validation error. 4) Parsing error of the message body (JSon, XML or Auto binding mode must be enabled); returns HTTP
 Status 400 if validation error. Default value: false
+]]>
+            </xs:documentation>
+          </xs:annotation>
+        </xs:attribute>
+        <xs:attribute name="clientResponseValidation" type="xs:string">
+          <xs:annotation>
+            <xs:documentation xml:lang="en">
+<![CDATA[
+Whether to check what Camel is returning as response to the client: 1) Status-code and Content-Type matches Rest DSL
+response messages. 2) Check whether expected headers is included according to the Rest DSL repose message headers. 3) If
+the response body is JSon then check whether its valid JSon. Returns 500 if validation error detected. Default value:
+false
 ]]>
             </xs:documentation>
           </xs:annotation>
@@ -14533,6 +14586,18 @@ returns HTTP Status 415 if validation error. 2) Accept header matches what the R
 406 if validation error. 3) Missing required data (query parameters, HTTP headers, body); returns HTTP Status 400 if
 validation error. 4) Parsing error of the message body (JSon, XML or Auto binding mode must be enabled); returns HTTP
 Status 400 if validation error. Default value: false
+]]>
+            </xs:documentation>
+          </xs:annotation>
+        </xs:attribute>
+        <xs:attribute name="clientResponseValidation" type="xs:string">
+          <xs:annotation>
+            <xs:documentation xml:lang="en">
+<![CDATA[
+Whether to check what Camel is returning as response to the client: 1) Status-code and Content-Type matches Rest DSL
+response messages. 2) Check whether expected headers is included according to the Rest DSL repose message headers. 3) If
+the response body is JSon then check whether its valid JSon. Returns 500 if validation error detected. Default value:
+false
 ]]>
             </xs:documentation>
           </xs:annotation>
@@ -14731,6 +14796,15 @@ Examples of response messages.
         <xs:documentation xml:lang="en">
 <![CDATA[
 The response code such as a HTTP status code. Default value: 200
+]]>
+        </xs:documentation>
+      </xs:annotation>
+    </xs:attribute>
+    <xs:attribute name="contentType" type="xs:string">
+      <xs:annotation>
+        <xs:documentation xml:lang="en">
+<![CDATA[
+The response content-type such as application/json.
 ]]>
         </xs:documentation>
       </xs:annotation>
@@ -15699,7 +15773,7 @@ Set a reference to a custom Expression to use.
         <xs:element ref="tns:fhirJson"/>
         <xs:element ref="tns:fhirXml"/>
         <xs:element ref="tns:flatpack"/>
-        <xs:element ref="tns:fury"/>
+        <xs:element ref="tns:fory"/>
         <xs:element ref="tns:grok"/>
         <xs:element ref="tns:gzipDeflater"/>
         <xs:element ref="tns:hl7"/>
@@ -16404,6 +16478,18 @@ returns HTTP Status 415 if validation error. 2) Accept header matches what the R
 406 if validation error. 3) Missing required data (query parameters, HTTP headers, body); returns HTTP Status 400 if
 validation error. 4) Parsing error of the message body (JSon, XML or Auto binding mode must be enabled); returns HTTP
 Status 400 if validation error. Default value: false
+]]>
+            </xs:documentation>
+          </xs:annotation>
+        </xs:attribute>
+        <xs:attribute name="clientResponseValidation" type="xs:string">
+          <xs:annotation>
+            <xs:documentation xml:lang="en">
+<![CDATA[
+Whether to check what Camel is returning as response to the client: 1) Status-code and Content-Type matches Rest DSL
+response messages. 2) Check whether expected headers is included according to the Rest DSL repose message headers. 3) If
+the response body is JSon then check whether its valid JSon. Returns 500 if validation error detected. Default value:
+false
 ]]>
             </xs:documentation>
           </xs:annotation>
@@ -16537,7 +16623,7 @@ Set the 'to' data type name. If you specify 'json:XYZ', the transformer will be
             <xs:element ref="tns:fhirJson"/>
             <xs:element ref="tns:fhirXml"/>
             <xs:element ref="tns:flatpack"/>
-            <xs:element ref="tns:fury"/>
+            <xs:element ref="tns:fory"/>
             <xs:element ref="tns:grok"/>
             <xs:element ref="tns:gzipDeflater"/>
             <xs:element ref="tns:hl7"/>