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 97d5b9737b5 Regen
97d5b9737b5 is described below

commit 97d5b9737b5e0940e3a7242542f446282b90df77
Author: Claus Ibsen <claus.ib...@gmail.com>
AuthorDate: Mon Jun 10 07:03:44 2024 +0200

    Regen
---
 .../apache/camel/catalog/schemas/camel-spring.xsd  | 50 +++++++++++++++++++---
 1 file changed, 45 insertions(+), 5 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 ece74309fe5..e92a71aeca2 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[
-Define custom beans that can be used in your Camel routes and in general.
+Calls a Java bean
 ]]>
       </xs:documentation>
     </xs:annotation>
@@ -3973,10 +3973,50 @@ Enables random backoff. Default value: false
     <xs:complexContent>
       <xs:extension base="tns:noOutputDefinition">
         <xs:sequence/>
-        <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:attribute name="ref" type="xs:string">
+          <xs:annotation>
+            <xs:documentation xml:lang="en">
+<![CDATA[
+Sets a reference to an existing 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:extension>
     </xs:complexContent>
   </xs:complexType>

Reply via email to