You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@camel.apache.org by da...@apache.org on 2023/10/21 10:11:02 UTC

[camel] branch main updated: Regen for commit e6cede73c02c88d83ffd5876090e0072f9ea8e7b (#11796)

This is an automated email from the ASF dual-hosted git repository.

davsclaus pushed a commit to branch main
in repository https://gitbox.apache.org/repos/asf/camel.git


The following commit(s) were added to refs/heads/main by this push:
     new 99af625708b Regen for commit e6cede73c02c88d83ffd5876090e0072f9ea8e7b (#11796)
99af625708b is described below

commit 99af625708b0f05f64c8db82504d92f274c8f1ee
Author: github-actions[bot] <41...@users.noreply.github.com>
AuthorDate: Sat Oct 21 12:10:56 2023 +0200

    Regen for commit e6cede73c02c88d83ffd5876090e0072f9ea8e7b (#11796)
    
    Signed-off-by: GitHub <no...@github.com>
    Co-authored-by: davsclaus <da...@users.noreply.github.com>
---
 .../apache/camel/catalog/schemas/camel-spring.xsd  | 52 +++-------------------
 1 file changed, 6 insertions(+), 46 deletions(-)

diff --git a/catalog/camel-catalog/src/generated/resources/org/apache/camel/catalog/schemas/camel-spring.xsd b/catalog/camel-catalog/src/generated/resources/org/apache/camel/catalog/schemas/camel-spring.xsd
index 8b8aba708c5..50efc8aa176 100644
--- a/catalog/camel-catalog/src/generated/resources/org/apache/camel/catalog/schemas/camel-spring.xsd
+++ b/catalog/camel-catalog/src/generated/resources/org/apache/camel/catalog/schemas/camel-spring.xsd
@@ -75,7 +75,7 @@ Configures batch-processing resequence eip.
     <xs:annotation>
       <xs:documentation xml:lang="en">
 <![CDATA[
-Calls a Java bean
+Define custom beans that can be used in your Camel routes and in general.
 ]]>
       </xs:documentation>
     </xs:annotation>
@@ -1143,7 +1143,7 @@ Properties to use with properties placeholder
     <xs:annotation>
       <xs:documentation xml:lang="en">
 <![CDATA[
-A key value pair where the value is a literal value
+Bean property
 ]]>
       </xs:documentation>
     </xs:annotation>
@@ -3852,50 +3852,10 @@ Enables random backoff. Default value: false
     <xs:complexContent>
       <xs:extension base="tns:noOutputDefinition">
         <xs:sequence/>
-        <xs:attribute name="ref" type="xs:string">
-          <xs:annotation>
-            <xs:documentation xml:lang="en">
-<![CDATA[
-Sets a reference to an exiting bean to use, which is looked up from the registry.
-]]>
-            </xs:documentation>
-          </xs:annotation>
-        </xs:attribute>
-        <xs:attribute name="method" type="xs:string">
-          <xs:annotation>
-            <xs:documentation xml:lang="en">
-<![CDATA[
-Sets the method name on the bean to use.
-]]>
-            </xs:documentation>
-          </xs:annotation>
-        </xs:attribute>
-        <xs:attribute name="beanType" type="xs:string">
-          <xs:annotation>
-            <xs:documentation xml:lang="en">
-<![CDATA[
-Sets the class name (fully qualified) of the bean to use.
-]]>
-            </xs:documentation>
-          </xs:annotation>
-        </xs:attribute>
-        <xs:attribute name="scope" type="xs:string">
-          <xs:annotation>
-            <xs:documentation xml:lang="en">
-<![CDATA[
-Scope of bean. When using singleton scope (default) the bean is created or looked up only once and reused for the
-lifetime of the endpoint. The bean should be thread-safe in case concurrent threads is calling the bean at the same
-time. When using request scope the bean is created or looked up once per request (exchange). This can be used if you
-want to store state on a bean while processing a request and you want to call the same bean instance multiple times
-while processing the request. The bean does not have to be thread-safe as the instance is only called from the same
-request. When using prototype scope, then the bean will be looked up or created per call. However in case of lookup then
-this is delegated to the bean registry such as Spring or CDI (if in use), which depends on their configuration can act
-as either singleton or prototype scope. So when using prototype scope then this depends on the bean registry
-implementation. Default value: Singleton
-]]>
-            </xs:documentation>
-          </xs:annotation>
-        </xs:attribute>
+        <xs:attribute name="ref" type="xs:string"/>
+        <xs:attribute name="method" type="xs:string"/>
+        <xs:attribute name="beanType" type="xs:string"/>
+        <xs:attribute name="scope" type="xs:string"/>
       </xs:extension>
     </xs:complexContent>
   </xs:complexType>