INT-3418: xsd-2.1 -> 2.2
This commit is contained in:
Artem Bilan
File diff suppressed because it is too large
Load Diff
@@ -11,7 +11,7 @@
|
||||
<xsd:import namespace="http://www.springframework.org/schema/beans"/>
|
||||
<xsd:import namespace="http://www.springframework.org/schema/tool"/>
|
||||
<xsd:import namespace="http://www.springframework.org/schema/integration"
|
||||
schemaLocation="http://www.springframework.org/schema/integration/spring-integration-2.0.xsd"/>
|
||||
schemaLocation="http://www.springframework.org/schema/integration/spring-integration-2.1.xsd"/>
|
||||
|
||||
<xsd:annotation>
|
||||
<xsd:documentation><![CDATA[
|
||||
@@ -127,7 +127,7 @@
|
||||
</xsd:annotation>
|
||||
</xsd:element>
|
||||
</xsd:sequence>
|
||||
<xsd:attribute name="id" type="xsd:ID" use="required">
|
||||
<xsd:attribute name="id" type="xsd:string" use="required">
|
||||
<xsd:annotation>
|
||||
<xsd:documentation>
|
||||
ID for this channel. Required.
|
||||
@@ -377,6 +377,35 @@
|
||||
</xsd:documentation>
|
||||
</xsd:annotation>
|
||||
</xsd:attribute>
|
||||
<xsd:attribute name="subscription-durable" type="xsd:string">
|
||||
<xsd:annotation>
|
||||
<xsd:documentation>
|
||||
Boolean property indicating whether to make the subscription durable. The durable subscription name to be used can be specified
|
||||
through the "durableSubscriptionName" property. Default is "false". Set this to "true" to register a durable subscription,
|
||||
typically in combination with a "durableSubscriptionName" value (unless your message listener class name is good enough as
|
||||
subscription name). Only makes sense when listening to a topic (pub-sub domain).
|
||||
</xsd:documentation>
|
||||
</xsd:annotation>
|
||||
</xsd:attribute>
|
||||
<xsd:attribute name="durable-subscription-name" type="xsd:string">
|
||||
<xsd:annotation>
|
||||
<xsd:documentation>
|
||||
The name of a durable subscription to create. To be applied in case of a topic (pub-sub domain) with subscription durability
|
||||
activated. The durable subscription name needs to be unique within this client's JMS client id. Default is the class name of the
|
||||
specified message listener. Note: Only 1 concurrent consumer (which is the default of this message listener container) is allowed
|
||||
for each durable subscription.
|
||||
</xsd:documentation>
|
||||
</xsd:annotation>
|
||||
</xsd:attribute>
|
||||
<xsd:attribute name="client-id" type="xsd:string">
|
||||
<xsd:annotation>
|
||||
<xsd:documentation>
|
||||
The JMS client id for a shared Connection created and used by this container. Note that client ids need to be unique among all
|
||||
active Connections of the underlying JMS provider. Furthermore, a client id can only be assigned if the original ConnectionFactory
|
||||
hasn't already assigned one.
|
||||
</xsd:documentation>
|
||||
</xsd:annotation>
|
||||
</xsd:attribute>
|
||||
<xsd:attribute name="channel" type="xsd:string">
|
||||
<xsd:annotation>
|
||||
<xsd:appinfo>
|
||||
@@ -422,14 +451,11 @@
|
||||
</xsd:appinfo>
|
||||
</xsd:annotation>
|
||||
</xsd:attribute>
|
||||
<xsd:attribute name="concurrent-consumers" type="xsd:string"/>
|
||||
<xsd:attribute name="max-concurrent-consumers" type="xsd:string"/>
|
||||
<xsd:attribute name="cache-level" type="xsd:string"/>
|
||||
<xsd:attribute name="max-messages-per-task" type="xsd:string"/>
|
||||
|
||||
<xsd:attribute name="receive-timeout" type="xsd:string"/>
|
||||
<xsd:attribute name="recovery-interval" type="xsd:string"/>
|
||||
<xsd:attribute name="idle-consumer-limit" type="xsd:string"/>
|
||||
<xsd:attribute name="idle-task-execution-limit" type="xsd:string"/>
|
||||
|
||||
<xsd:attributeGroup ref="dmlcAttributeGroup"/>
|
||||
|
||||
</xsd:extension>
|
||||
</xsd:complexContent>
|
||||
</xsd:complexType>
|
||||
@@ -621,14 +647,39 @@
|
||||
</xsd:appinfo>
|
||||
</xsd:annotation>
|
||||
</xsd:attribute>
|
||||
<xsd:attribute name="concurrent-consumers" type="xsd:string"/>
|
||||
<xsd:attribute name="max-concurrent-consumers" type="xsd:string"/>
|
||||
<xsd:attribute name="cache-level" type="xsd:string"/>
|
||||
<xsd:attribute name="max-messages-per-task" type="xsd:string"/>
|
||||
<xsd:attribute name="subscription-durable" type="xsd:string">
|
||||
<xsd:annotation>
|
||||
<xsd:documentation>
|
||||
Boolean property indicating whether to make the subscription durable. The durable subscription name to be used can be specified
|
||||
through the "durableSubscriptionName" property. Default is "false". Set this to "true" to register a durable subscription,
|
||||
typically in combination with a "durableSubscriptionName" value (unless your message listener class name is good enough as
|
||||
subscription name). Only makes sense when listening to a topic (pub-sub domain).
|
||||
</xsd:documentation>
|
||||
</xsd:annotation>
|
||||
</xsd:attribute>
|
||||
<xsd:attribute name="durable-subscription-name" type="xsd:string">
|
||||
<xsd:annotation>
|
||||
<xsd:documentation>
|
||||
The name of a durable subscription to create. To be applied in case of a topic (pub-sub domain) with subscription durability
|
||||
activated. The durable subscription name needs to be unique within this client's JMS client id. Default is the class name of the
|
||||
specified message listener. Note: Only 1 concurrent consumer (which is the default of this message listener container) is allowed
|
||||
for each durable subscription.
|
||||
</xsd:documentation>
|
||||
</xsd:annotation>
|
||||
</xsd:attribute>
|
||||
<xsd:attribute name="client-id" type="xsd:string">
|
||||
<xsd:annotation>
|
||||
<xsd:documentation>
|
||||
The JMS client id for a shared Connection created and used by this container. Note that client ids need to be unique among all
|
||||
active Connections of the underlying JMS provider. Furthermore, a client id can only be assigned if the original ConnectionFactory
|
||||
hasn't already assigned one.
|
||||
</xsd:documentation>
|
||||
</xsd:annotation>
|
||||
</xsd:attribute>
|
||||
<xsd:attribute name="receive-timeout" type="xsd:string"/>
|
||||
<xsd:attribute name="recovery-interval" type="xsd:string"/>
|
||||
<xsd:attribute name="idle-consumer-limit" type="xsd:string"/>
|
||||
<xsd:attribute name="idle-task-execution-limit" type="xsd:string"/>
|
||||
|
||||
<xsd:attributeGroup ref="dmlcAttributeGroup"/>
|
||||
|
||||
<xsd:attribute name="reply-time-to-live" type="xsd:string"/>
|
||||
<xsd:attribute name="reply-priority" type="xsd:string"/>
|
||||
<xsd:attribute name="reply-delivery-persistent" type="xsd:string"/>
|
||||
@@ -648,7 +699,7 @@
|
||||
<xsd:sequence>
|
||||
<xsd:element ref="integration:poller" minOccurs="0" maxOccurs="1"/>
|
||||
</xsd:sequence>
|
||||
<xsd:attribute name="id" type="xsd:ID"/>
|
||||
<xsd:attribute name="id" type="xsd:string"/>
|
||||
<xsd:attribute name="request-channel" type="xsd:string">
|
||||
<xsd:annotation>
|
||||
<xsd:appinfo>
|
||||
@@ -686,7 +737,9 @@
|
||||
<xsd:documentation>
|
||||
A reference to a javax.jms.Destination by bean name. As an alternative to a bean
|
||||
reference, use 'request-destination-name' and 'request-pub-sub-domain' which will rely
|
||||
upon the DestinationResolver strategy (DynamicDestinationResolver by default).
|
||||
upon the DestinationResolver strategy (DynamicDestinationResolver by default). This
|
||||
attribute is mutually exclusive with 'request-destination-name' and
|
||||
'request-destination-expression'.
|
||||
</xsd:documentation>
|
||||
<xsd:appinfo>
|
||||
<tool:annotation kind="ref">
|
||||
@@ -695,8 +748,34 @@
|
||||
</xsd:appinfo>
|
||||
</xsd:annotation>
|
||||
</xsd:attribute>
|
||||
<xsd:attribute name="request-destination-name" type="xsd:string"/>
|
||||
<xsd:attribute name="request-pub-sub-domain" type="xsd:string"/>
|
||||
<xsd:attribute name="request-destination-name" type="xsd:string">
|
||||
<xsd:annotation>
|
||||
<xsd:documentation>
|
||||
Name of a destination to which request messages will be sent. This name will be handled
|
||||
by this gateway's DestinationResolver. This attribute is mutually exclusive with
|
||||
'request-destination' and 'request-destination-expression'.
|
||||
</xsd:documentation>
|
||||
</xsd:annotation>
|
||||
</xsd:attribute>
|
||||
<xsd:attribute name="request-destination-expression" type="xsd:string">
|
||||
<xsd:annotation>
|
||||
<xsd:documentation>
|
||||
A SpEL expression to be evaluated at runtime against each Spring Integration request Message as
|
||||
the root object. The result should be either a Destination instance or a String representing
|
||||
the destination name. In the latter case, it will be passed to this adapter's DestinationResolver.
|
||||
This attribute is mutually exclusive with 'request-destination' and 'request-destination-name'.
|
||||
</xsd:documentation>
|
||||
</xsd:annotation>
|
||||
</xsd:attribute>
|
||||
<xsd:attribute name="request-pub-sub-domain" type="xsd:string">
|
||||
<xsd:annotation>
|
||||
<xsd:documentation>
|
||||
When resolving a request destination name (rather than having a 'request-destination' reference),
|
||||
a true value here specifies that the DestinationResolver should resolve Topics rather than Queues.
|
||||
Default is false.
|
||||
</xsd:documentation>
|
||||
</xsd:annotation>
|
||||
</xsd:attribute>
|
||||
<xsd:attribute name="reply-destination" type="xsd:string">
|
||||
<xsd:annotation>
|
||||
<xsd:documentation>
|
||||
@@ -823,7 +902,8 @@
|
||||
<xsd:documentation>
|
||||
A reference to a javax.jms.Destination by bean name. As an alternative to a bean
|
||||
reference, use 'destination-name' and 'pub-sub-domain' which will rely upon the
|
||||
DestinationResolver strategy (DynamicDestinationResolver by default).
|
||||
DestinationResolver strategy (DynamicDestinationResolver by default). This attribute
|
||||
is mutually exclusive with 'destination-name' and 'destination-expression'.
|
||||
</xsd:documentation>
|
||||
<xsd:appinfo>
|
||||
<tool:annotation kind="ref">
|
||||
@@ -832,8 +912,33 @@
|
||||
</xsd:appinfo>
|
||||
</xsd:annotation>
|
||||
</xsd:attribute>
|
||||
<xsd:attribute name="destination-name" type="xsd:string"/>
|
||||
<xsd:attribute name="pub-sub-domain" type="xsd:string"/>
|
||||
<xsd:attribute name="destination-name" type="xsd:string">
|
||||
<xsd:annotation>
|
||||
<xsd:documentation>
|
||||
Name of the destination to which JMS Messages will be sent. This will be passed to the
|
||||
adapter's DestinationResolver. This attribute is mutually exclusive with 'destination'
|
||||
and 'destination-expression'.
|
||||
</xsd:documentation>
|
||||
</xsd:annotation>
|
||||
</xsd:attribute>
|
||||
<xsd:attribute name="destination-expression" type="xsd:string">
|
||||
<xsd:annotation>
|
||||
<xsd:documentation>
|
||||
A SpEL expression to be evaluated at runtime against each Spring Integration Message as
|
||||
the root object. The result should be either a Destination instance or a String representing
|
||||
the destination name. In the latter case, it will be passed to this adapter's DestinationResolver.
|
||||
If the evaluation result is null, messages will be sent to the default destination of the
|
||||
underlying JmsTemplate. This attribute is mutually exclusive with 'destination' and 'destination-name'.
|
||||
</xsd:documentation>
|
||||
</xsd:annotation>
|
||||
</xsd:attribute>
|
||||
<xsd:attribute name="pub-sub-domain" type="xsd:string">
|
||||
<xsd:annotation>
|
||||
<xsd:documentation>
|
||||
If true, specifies that destination names should resolve to Topics rather than Queues. Default is false.
|
||||
</xsd:documentation>
|
||||
</xsd:annotation>
|
||||
</xsd:attribute>
|
||||
<xsd:attribute name="channel" type="xsd:string">
|
||||
<xsd:annotation>
|
||||
<xsd:appinfo>
|
||||
@@ -1014,7 +1119,7 @@
|
||||
Common configuration for JMS-based adapters.
|
||||
</xsd:documentation>
|
||||
</xsd:annotation>
|
||||
<xsd:attribute name="id" type="xsd:ID"/>
|
||||
<xsd:attribute name="id" type="xsd:string"/>
|
||||
<xsd:attribute name="connection-factory" type="xsd:string">
|
||||
<xsd:annotation>
|
||||
<xsd:appinfo>
|
||||
@@ -1050,7 +1155,7 @@
|
||||
</xsd:complexType>
|
||||
|
||||
<xsd:complexType name="transformerType">
|
||||
<xsd:attribute name="id" type="xsd:ID"/>
|
||||
<xsd:attribute name="id" type="xsd:string"/>
|
||||
<xsd:attribute name="input-channel" type="xsd:string">
|
||||
<xsd:annotation>
|
||||
<xsd:appinfo>
|
||||
@@ -1070,5 +1175,92 @@
|
||||
</xsd:annotation>
|
||||
</xsd:attribute>
|
||||
</xsd:complexType>
|
||||
|
||||
<xsd:attributeGroup name="dmlcAttributeGroup">
|
||||
<xsd:attribute name="concurrent-consumers" type="xsd:string">
|
||||
<xsd:annotation>
|
||||
<xsd:documentation>
|
||||
Specify the number of concurrent consumers to create. Default is 1.
|
||||
Specifying a higher value for this setting will increase the standard
|
||||
level of scheduled concurrent consumers at runtime: This is effectively
|
||||
the minimum number of concurrent consumers which will be scheduled
|
||||
at any given time. This is a static setting; for dynamic scaling,
|
||||
consider specifying the "maxConcurrentConsumers" setting instead.
|
||||
Raising the number of concurrent consumers is recommendable in order
|
||||
to scale the consumption of messages coming in from a queue. However,
|
||||
note that any ordering guarantees are lost once multiple consumers are
|
||||
registered
|
||||
</xsd:documentation>
|
||||
</xsd:annotation>
|
||||
</xsd:attribute>
|
||||
<xsd:attribute name="max-concurrent-consumers" type="xsd:string">
|
||||
<xsd:annotation>
|
||||
<xsd:documentation>
|
||||
Specify the maximum number of concurrent consumers to create. Default is 1.
|
||||
If this setting is higher than "concurrentConsumers", the listener container
|
||||
will dynamically schedule new consumers at runtime, provided that enough
|
||||
incoming messages are encountered. Once the load goes down again, the number of
|
||||
consumers will be reduced to the standard level ("concurrentConsumers") again.
|
||||
Raising the number of concurrent consumers is recommendable in order
|
||||
to scale the consumption of messages coming in from a queue. However,
|
||||
note that any ordering guarantees are lost once multiple consumers are
|
||||
registered.
|
||||
</xsd:documentation>
|
||||
</xsd:annotation>
|
||||
</xsd:attribute>
|
||||
<xsd:attribute name="cache-level" type="xsd:string">
|
||||
<xsd:annotation>
|
||||
<xsd:documentation>
|
||||
Specify the level of caching that this listener container is allowed to apply:
|
||||
CACHE_NONE = 0
|
||||
CACHE_CONNECTION = 1
|
||||
CACHE_SESSION = 2
|
||||
CACHE_CONSUMER = 3
|
||||
</xsd:documentation>
|
||||
</xsd:annotation>
|
||||
</xsd:attribute>
|
||||
<xsd:attribute name="max-messages-per-task" type="xsd:string">
|
||||
<xsd:annotation>
|
||||
<xsd:documentation>
|
||||
Specify the maximum number of messages to process in one task.
|
||||
More concretely, this limits the number of message reception attempts
|
||||
per task, which includes receive iterations that did not actually
|
||||
pick up a message until they hit their timeout
|
||||
</xsd:documentation>
|
||||
</xsd:annotation>
|
||||
</xsd:attribute>
|
||||
|
||||
<xsd:attribute name="recovery-interval" type="xsd:string">
|
||||
<xsd:annotation>
|
||||
<xsd:documentation>
|
||||
Interval in miliseconds between the recovery attempts
|
||||
</xsd:documentation>
|
||||
</xsd:annotation>
|
||||
</xsd:attribute>
|
||||
<xsd:attribute name="idle-consumer-limit" type="xsd:string">
|
||||
<xsd:annotation>
|
||||
<xsd:documentation>
|
||||
Specify the limit for the number of consumers that are allowed to be idle at any given time.
|
||||
This limit is used to determine if a new invoker should be created. Increasing the limit causes
|
||||
invokers to be created more aggressively. This can be useful to ramp up the
|
||||
number of invokers faster.
|
||||
The default is 1, only scheduling a new invoker (which is likely to
|
||||
be idle initially) if none of the existing invokers is currently idle.
|
||||
</xsd:documentation>
|
||||
</xsd:annotation>
|
||||
</xsd:attribute>
|
||||
<xsd:attribute name="idle-task-execution-limit" type="xsd:string">
|
||||
<xsd:annotation>
|
||||
<xsd:documentation>
|
||||
Specify the limit for idle executions of a consumer task, not having
|
||||
received any message within its execution. If this limit is reached,
|
||||
the task will shut down and leave receiving to other executing tasks.
|
||||
The default is 1, closing idle resources early once a task didn't
|
||||
receive a message.
|
||||
</xsd:documentation>
|
||||
</xsd:annotation>
|
||||
</xsd:attribute>
|
||||
|
||||
</xsd:attributeGroup>
|
||||
|
||||
</xsd:schema>
|
||||
Reference in New Issue
Block a user