INT-3418: xsd-2.2 -> 3.0

This commit is contained in:
Artem Bilan
2014-05-30 20:22:15 +03:00
parent 9bd441c8d0
commit 9e5e7514e0
51 changed files with 2822 additions and 15903 deletions

View File

@@ -1,214 +0,0 @@
<?xml version="1.0" encoding="UTF-8"?>
<xsd:schema xmlns="http://www.springframework.org/schema/integration/jmx" xmlns:xsd="http://www.w3.org/2001/XMLSchema"
xmlns:beans="http://www.springframework.org/schema/beans" xmlns:tool="http://www.springframework.org/schema/tool"
xmlns:integration="http://www.springframework.org/schema/integration" targetNamespace="http://www.springframework.org/schema/integration/jmx"
elementFormDefault="qualified" attributeFormDefault="unqualified">
<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.2.xsd" />
<xsd:annotation>
<xsd:documentation><![CDATA[
Defines the configuration elements for Spring Integration's JMX adapters.
]]></xsd:documentation>
</xsd:annotation>
<xsd:element name="attribute-polling-channel-adapter">
<xsd:annotation>
<xsd:documentation>
Defines an inbound Channel Adapter that polls for JMX attribute values.
</xsd:documentation>
</xsd:annotation>
<xsd:complexType>
<xsd:complexContent>
<xsd:extension base="adapterType">
<xsd:sequence minOccurs="0" maxOccurs="1">
<xsd:element ref="integration:poller" />
</xsd:sequence>
<xsd:attribute name="attribute-name" type="xsd:string" use="required" />
<xsd:attribute name="auto-startup" type="xsd:string" default="true" />
</xsd:extension>
</xsd:complexContent>
</xsd:complexType>
</xsd:element>
<xsd:element name="operation-invoking-outbound-gateway">
<xsd:annotation>
<xsd:documentation>
Defines an outbound Gateway which allows for Message-driven invocation of managed operations that
return values
</xsd:documentation>
</xsd:annotation>
<xsd:complexType>
<xsd:complexContent>
<xsd:extension base="operationInvokingType">
<xsd:all>
<xsd:element name="request-handler-advice-chain" type="integration:adviceChainType" minOccurs="0" maxOccurs="1" />
</xsd:all>
<xsd:attribute name="request-channel" type="xsd:string" />
<xsd:attribute name="reply-channel" type="xsd:string" use="optional" />
</xsd:extension>
</xsd:complexContent>
</xsd:complexType>
</xsd:element>
<xsd:element name="operation-invoking-channel-adapter">
<xsd:annotation>
<xsd:documentation>
Defines an outbound Channel Adapter for invoking JMX operations.
</xsd:documentation>
</xsd:annotation>
<xsd:complexType>
<xsd:complexContent>
<xsd:extension base="operationInvokingType">
<xsd:all>
<xsd:element name="request-handler-advice-chain" type="integration:adviceChainType" minOccurs="0" maxOccurs="1" />
</xsd:all>
<xsd:attribute name="channel" type="xsd:string" use="optional" />
</xsd:extension>
</xsd:complexContent>
</xsd:complexType>
</xsd:element>
<xsd:element name="notification-listening-channel-adapter">
<xsd:annotation>
<xsd:documentation><![CDATA[
Defines an inbound Channel Adapter that listens for JMX notifications. The 'object-name'
attribute on this endpoint can contain an ObjectName pattern and the MBeanServer will
be queried for MBeans with ObjectNames matching the pattern. In addition, it can contain
a SpEL expression that references a <util:list/> of ObjectNames or ObjectName patterns.
]]></xsd:documentation>
</xsd:annotation>
<xsd:complexType>
<xsd:complexContent>
<xsd:extension base="adapterType">
<xsd:attribute name="notification-filter" type="xsd:string" use="optional" />
<xsd:attribute name="handback" type="xsd:string" use="optional" />
<xsd:attribute name="send-timeout" type="xsd:string" use="optional" />
</xsd:extension>
</xsd:complexContent>
</xsd:complexType>
</xsd:element>
<xsd:element name="notification-publishing-channel-adapter">
<xsd:annotation>
<xsd:documentation>
Defines an outbound Channel Adapter that publishes JMX notifications.
</xsd:documentation>
</xsd:annotation>
<xsd:complexType>
<xsd:complexContent>
<xsd:extension base="adapterType">
<xsd:all>
<xsd:element name="request-handler-advice-chain" type="integration:adviceChainType" minOccurs="0" maxOccurs="1" />
</xsd:all>
<xsd:attribute name="default-notification-type" type="xsd:string" use="optional" />
</xsd:extension>
</xsd:complexContent>
</xsd:complexType>
</xsd:element>
<xsd:element name="mbean-export">
<xsd:annotation>
<xsd:documentation>
Exports Message Channels and Endpoints as MBeans.
</xsd:documentation>
</xsd:annotation>
<xsd:complexType>
<xsd:complexContent>
<xsd:extension base="mbeanServerIdentifyerType">
<xsd:attribute name="default-domain" use="optional">
<xsd:annotation>
<xsd:documentation>
The domain name for the MBeans exported by this Exporter.
</xsd:documentation>
</xsd:annotation>
</xsd:attribute>
<xsd:attribute name="object-name-static-properties" use="optional">
<xsd:annotation>
<xsd:appinfo>
<tool:annotation kind="ref">
<tool:expected-type type="java.util.Properties" />
</tool:annotation>
</xsd:appinfo>
<xsd:documentation>
Static object properties to be used for this domain. These properties are appended to
the ObjectName of all MBeans registered by this component.
</xsd:documentation>
</xsd:annotation>
</xsd:attribute>
<xsd:attribute name="managed-components" use="optional">
<xsd:annotation>
<xsd:documentation>
Comma separated list of simple patterns for component names to register (defaults to '*').
The pattern is applied to all components before they are registered, looking for a match on
the 'name' property of the ObjectName. A MessageChannel and a MessageHandler (for instance)
can share a name because they have a different type, so in that case they would either both
be included or both excluded.
</xsd:documentation>
</xsd:annotation>
</xsd:attribute>
<xsd:attribute name="shutdown-executor" use="optional">
<xsd:annotation>
<xsd:appinfo>
<tool:annotation kind="ref">
<tool:expected-type type="java.util.concurrent.Executor" />
</tool:annotation>
</xsd:appinfo>
<xsd:documentation>
An Executor used when shutting down the application using the 'stopActiveComponents()'
method. Only required when invoking the operation on a Spring-managed thread, such as
via a <control-bus/> from, say, an error flow. Using this executor avoids the
problem where the shutdown will wait for the current thread to terminate, time out,
and then force-close other components. When a dedicated executor is supplied,
the method will not wait on its threads to complete, and will terminate normally.
It is recommended that the executor used here is dedicated for this purpose and
not used elsewhere.
</xsd:documentation>
</xsd:annotation>
</xsd:attribute>
</xsd:extension>
</xsd:complexContent>
</xsd:complexType>
</xsd:element>
<xsd:complexType name="adapterType">
<xsd:annotation>
<xsd:documentation>
Defines inbound operation invoking type
</xsd:documentation>
</xsd:annotation>
<xsd:complexContent>
<xsd:extension base="mbeanServerIdentifyerType">
<xsd:attribute name="channel" type="xsd:string" />
<xsd:attribute name="object-name" type="xsd:string" use="required" />
</xsd:extension>
</xsd:complexContent>
</xsd:complexType>
<xsd:complexType name="operationInvokingType">
<xsd:annotation>
<xsd:documentation>
Defines outbound operation invoking type
</xsd:documentation>
</xsd:annotation>
<xsd:complexContent>
<xsd:extension base="mbeanServerIdentifyerType">
<xsd:attribute name="object-name" type="xsd:string" use="required" />
<xsd:attribute name="operation-name" type="xsd:string" use="required" />
</xsd:extension>
</xsd:complexContent>
</xsd:complexType>
<xsd:complexType name="mbeanServerIdentifyerType">
<xsd:attribute name="id" type="xsd:string" use="optional" />
<xsd:attribute name="server" type="xsd:string" default="mbeanServer">
<xsd:annotation>
<xsd:documentation>
Defines the name of the MBeanServer bean to connect to.
</xsd:documentation>
</xsd:annotation>
</xsd:attribute>
</xsd:complexType>
</xsd:schema>

View File

@@ -6,7 +6,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.1.xsd" />
<xsd:import namespace="http://www.springframework.org/schema/integration" schemaLocation="http://www.springframework.org/schema/integration/spring-integration-2.2.xsd" />
<xsd:annotation>
<xsd:documentation><![CDATA[
@@ -42,7 +42,10 @@
<xsd:complexType>
<xsd:complexContent>
<xsd:extension base="operationInvokingType">
<xsd:attribute name="request-channel" type="xsd:string" use="required" />
<xsd:all>
<xsd:element name="request-handler-advice-chain" type="integration:adviceChainType" minOccurs="0" maxOccurs="1" />
</xsd:all>
<xsd:attribute name="request-channel" type="xsd:string" />
<xsd:attribute name="reply-channel" type="xsd:string" use="optional" />
</xsd:extension>
</xsd:complexContent>
@@ -58,6 +61,9 @@
<xsd:complexType>
<xsd:complexContent>
<xsd:extension base="operationInvokingType">
<xsd:all>
<xsd:element name="request-handler-advice-chain" type="integration:adviceChainType" minOccurs="0" maxOccurs="1" />
</xsd:all>
<xsd:attribute name="channel" type="xsd:string" use="optional" />
</xsd:extension>
</xsd:complexContent>
@@ -66,9 +72,12 @@
<xsd:element name="notification-listening-channel-adapter">
<xsd:annotation>
<xsd:documentation>
Defines an inbound Channel Adapter that listens for JMX notifications.
</xsd:documentation>
<xsd:documentation><![CDATA[
Defines an inbound Channel Adapter that listens for JMX notifications. The 'object-name'
attribute on this endpoint can contain an ObjectName pattern and the MBeanServer will
be queried for MBeans with ObjectNames matching the pattern. In addition, it can contain
a SpEL expression that references a <util:list/> of ObjectNames or ObjectName patterns.
]]></xsd:documentation>
</xsd:annotation>
<xsd:complexType>
<xsd:complexContent>
@@ -90,6 +99,9 @@
<xsd:complexType>
<xsd:complexContent>
<xsd:extension base="adapterType">
<xsd:all>
<xsd:element name="request-handler-advice-chain" type="integration:adviceChainType" minOccurs="0" maxOccurs="1" />
</xsd:all>
<xsd:attribute name="default-notification-type" type="xsd:string" use="optional" />
</xsd:extension>
</xsd:complexContent>
@@ -136,6 +148,25 @@
</xsd:documentation>
</xsd:annotation>
</xsd:attribute>
<xsd:attribute name="shutdown-executor" use="optional">
<xsd:annotation>
<xsd:appinfo>
<tool:annotation kind="ref">
<tool:expected-type type="java.util.concurrent.Executor" />
</tool:annotation>
</xsd:appinfo>
<xsd:documentation>
An Executor used when shutting down the application using the 'stopActiveComponents()'
method. Only required when invoking the operation on a Spring-managed thread, such as
via a <control-bus/> from, say, an error flow. Using this executor avoids the
problem where the shutdown will wait for the current thread to terminate, time out,
and then force-close other components. When a dedicated executor is supplied,
the method will not wait on its threads to complete, and will terminate normally.
It is recommended that the executor used here is dedicated for this purpose and
not used elsewhere.
</xsd:documentation>
</xsd:annotation>
</xsd:attribute>
</xsd:extension>
</xsd:complexContent>
</xsd:complexType>
@@ -144,7 +175,7 @@
<xsd:complexType name="adapterType">
<xsd:annotation>
<xsd:documentation>
Defines inbound operation invoking type
Defines inbound operation invoking type
</xsd:documentation>
</xsd:annotation>
<xsd:complexContent>
@@ -158,7 +189,7 @@
<xsd:complexType name="operationInvokingType">
<xsd:annotation>
<xsd:documentation>
Defines outbound operation invoking type
Defines outbound operation invoking type
</xsd:documentation>
</xsd:annotation>
<xsd:complexContent>
@@ -180,4 +211,4 @@
</xsd:attribute>
</xsd:complexType>
</xsd:schema>
</xsd:schema>