From 44be2a957a9132025aa8684ac6b6adaf6837db50 Mon Sep 17 00:00:00 2001 From: Oleg Zhurakousky Date: Mon, 22 Nov 2010 11:21:24 -0500 Subject: [PATCH] INT-1552 added schema docs for XMPP --- .../config/spring-integration-xmpp-2.0.xsd | 171 ++++++++++++++++-- 1 file changed, 155 insertions(+), 16 deletions(-) diff --git a/spring-integration-xmpp/src/main/resources/org/springframework/integration/xmpp/config/spring-integration-xmpp-2.0.xsd b/spring-integration-xmpp/src/main/resources/org/springframework/integration/xmpp/config/spring-integration-xmpp-2.0.xsd index 039801232e..e75e359b1c 100644 --- a/spring-integration-xmpp/src/main/resources/org/springframework/integration/xmpp/config/spring-integration-xmpp-2.0.xsd +++ b/spring-integration-xmpp/src/main/resources/org/springframework/integration/xmpp/config/spring-integration-xmpp-2.0.xsd @@ -21,13 +21,57 @@ - - - - - - - + + + + The user name (e.g., somuser@gmail.com) that will be used by this connection object + + + + + + + Lifecycle attribute signaling if this component should be started during Application Context startup. + Default is TRUE + + + + + + + The user's password + + + + + + + The host name to connect TO + + + + + + + The XMPP service name for this connection + + + + + + + The resource field specifies the XMPP resource you are using. The use of unique resources allows + you to connect to your XMPP server from multiple locations simultaneously. Resources might + + + + + + + The port on which the host is running + + + - - + + + + Specifies if generated Message payload should consist of only + the text of the XMPP message or the entire XMPP (Smack API specific) message. Default is true. + + + + + + + Lifecycle attribute signaling if this component should be started during Application Context startup. + + + @@ -63,6 +120,11 @@ + + Identifies channel attached to this adapter. Depending on the type of the adapter + this channel could be the receiving channel (e.g., outbound-channel-adapter) or channel where + messages will be sent to by this adapter (e.g., inbound-channel-adapter). + @@ -72,6 +134,9 @@ + + Reference to XMPP connection bean + @@ -95,6 +160,11 @@ + + Identifies channel attached to this adapter. Depending on the type of the adapter + this channel could be the receiving channel (e.g., outbound-channel-adapter) or channel where + messages will be sent to by this adapter (e.g., inbound-channel-adapter). + @@ -104,6 +174,9 @@ + + Reference to XMPP connection bean + @@ -117,8 +190,21 @@ - - + + + Specifies if generated Message payload should consist of only + the text of the XMPP Presence message or the entire XMPP Presence (Smack API specific) message. + Default is TRUE. + + + + + + Lifecycle attribute signaling if this component should be started during Application Context startup. + Default is TRUE + + + @@ -126,6 +212,11 @@ + + Identifies channel attached to this adapter. Depending on the type of the adapter + this channel could be the receiving channel (e.g., outbound-channel-adapter) or channel where + messages will be sent to by this adapter (e.g., inbound-channel-adapter). + @@ -135,6 +226,9 @@ + + Reference to XMPP connection bean + @@ -158,6 +252,11 @@ + + Identifies channel attached to this adapter. Depending on the type of the adapter + this channel could be the receiving channel (e.g., outbound-channel-adapter) or channel where + messages will be sent to by this adapter (e.g., inbound-channel-adapter). + @@ -167,6 +266,9 @@ + + Reference to XMPP connection bean + @@ -182,8 +284,21 @@ - - + + + + The id of the user you sending a message to (e.g., user@gmail.com) + + + + + + + The conversation thread id used to corelate XMPP packets as + belonging to a particular conversation + + + @@ -203,9 +318,27 @@ - - - + + + + Value of this header inside of a Message + + + + + + + Reference to a bean that contains a method that will compute the header value + + + + + + + SpEL expression that will compute the header value + + + @@ -227,6 +360,9 @@ + + The receiving Message channel of this endpoint + @@ -236,6 +372,9 @@ + + Identifies the Message channel where Message will be sent after it's being processed by this endpoint +