From 66519d30f1236bf57bab0cdb4b0bc30a74089620 Mon Sep 17 00:00:00 2001 From: Mark Fisher Date: Mon, 3 Nov 2008 03:41:18 +0000 Subject: [PATCH] de-emphasized message bus --- .../src/{namespaces.xml => configuration.xml} | 51 +++++++++++-------- spring-integration-reference/src/overview.xml | 16 ------ .../src/spring-integration-reference.xml | 2 +- 3 files changed, 30 insertions(+), 39 deletions(-) rename spring-integration-reference/src/{namespaces.xml => configuration.xml} (91%) diff --git a/spring-integration-reference/src/namespaces.xml b/spring-integration-reference/src/configuration.xml similarity index 91% rename from spring-integration-reference/src/namespaces.xml rename to spring-integration-reference/src/configuration.xml index aef70d3b46..ac195e30e8 100644 --- a/spring-integration-reference/src/namespaces.xml +++ b/spring-integration-reference/src/configuration.xml @@ -1,8 +1,10 @@ - - Namespace Support - + + Configuration +
+ Introduction + Spring Integration offers a number of configuration options. Which option you choose depends upon your particular needs and at what level you prefer to work. As with the Spring framework in general, it is also possible to mix and match the various techniques according to the particular problem at hand. For example, you may choose the @@ -11,13 +13,17 @@ match the names of annotations, and the attributes of those XML elements will match the names of annotation properties. Direct usage of the API is of course always an option, but we expect that most users will choose one of the higher-level options, or a combination of the namespace-based and annotation-driven configuration. - - + +
+ +
+ Namespace Support + Spring Integration components can be configured with XML elements that map directly to the terminology and concepts of enterprise integration. In many cases, the element names match those of the Enterprise Integration Patterns. - - + + To enable Spring Integration's core namespace support within your Spring configuration files, add the following namespace reference and schema mapping in your top-level 'beans' element: http://www.springframework.org/schema/integration http://www.springframework.org/schema/integration/spring-integration-1.0.xsd"> - - + + You can choose any name after "xmlns:"; integration is used here for clarity, but you might prefer a shorter abbreviation. Of course if you are using an XML-editor or IDE support, then the availability of auto-completion may convince you to keep the longer name for clarity. Alternatively, you can create configuration @@ -40,8 +46,8 @@ http://www.springframework.org/schema/beans/spring-beans-2.5.xsd http://www.springframework.org/schema/integration http://www.springframework.org/schema/integration/spring-integration-1.0.xsd">]]> - - + + When using this alternative, no prefix is necessary for the Spring Integration elements. On the other hand, if you want to define a generic Spring "bean" within the same configuration file, then a prefix would be required for the bean element (<beans:bean ... />). Since it is generally a good idea to modularize the @@ -49,13 +55,13 @@ use the latter approach in the integration-focused configuration files, since generic beans are seldom necessary within those same files. For purposes of this documentation, we will assume the "integration" namespace is primary. - - - Many other namespaces are provided within the Spring Integration distribution. In fact, each adapter type (JMS, - File, etc.) that provides namespace support defines its elements within a separate schema. In order to use these - elements, simply add the necessary namespaces with an "xmlns" entry and the corresponding "schemaLocation" mapping. - For example, the following root element shows several of these namespace declarations: - + + + Many other namespaces are provided within the Spring Integration distribution. In fact, each adapter type (JMS, + File, etc.) that provides namespace support defines its elements within a separate schema. In order to use these + elements, simply add the necessary namespaces with an "xmlns" entry and the corresponding "schemaLocation" mapping. + For example, the following root element shows several of these namespace declarations: + ... ]]> - The reference manual provides specific examples of the various elements in their corresponding chapters. Here, the - main thing to recognize is the consistency of the naming for each namespace URI and schema location. - + The reference manual provides specific examples of the various elements in their corresponding chapters. Here, the + main thing to recognize is the consistency of the naming for each namespace URI and schema location. + +
Configuring the Message Bus @@ -127,7 +134,7 @@
- Annotations + Annotation Support In addition to the XML namespace support for configuring Message Endpoints, it is also possible to use annotations. First, Spring Integration provides the class-level @MessageEndpoint diff --git a/spring-integration-reference/src/overview.xml b/spring-integration-reference/src/overview.xml index a4d84dacb8..d785e7b5d5 100644 --- a/spring-integration-reference/src/overview.xml +++ b/spring-integration-reference/src/overview.xml @@ -162,22 +162,6 @@ non-invasive way to use each of these.
- -
- Message Bus - - The Message Bus is the primary example of inversion of control within Spring Integration. Essentially, it - forms a logical extension of the Spring application context into the messaging domain. For example, it will - automatically detect Message Channels and Message Endpoints from within the application context. It handles the - scheduling of pollers, and the lifecycle management of all messaging components that can be initialized, - started, and stopped. - - - - - - -
diff --git a/spring-integration-reference/src/spring-integration-reference.xml b/spring-integration-reference/src/spring-integration-reference.xml index 6bcdc3161a..6b7ae0893b 100644 --- a/spring-integration-reference/src/spring-integration-reference.xml +++ b/spring-integration-reference/src/spring-integration-reference.xml @@ -62,7 +62,7 @@ - + \ No newline at end of file