diff --git a/docs/src/reference/docbook/index.xml b/docs/src/reference/docbook/index.xml index 3317238c14..5b6086cc61 100644 --- a/docs/src/reference/docbook/index.xml +++ b/docs/src/reference/docbook/index.xml @@ -91,7 +91,7 @@ - + diff --git a/docs/src/reference/docbook/samples.xml b/docs/src/reference/docbook/samples.xml index b2ca7d18fe..9ab5f6e2b6 100644 --- a/docs/src/reference/docbook/samples.xml +++ b/docs/src/reference/docbook/samples.xml @@ -136,7 +136,6 @@ That includes Samples, so if you can't find what you are looking for let us know -
Samples @@ -146,6 +145,7 @@ That includes Samples, so if you can't find what you are looking for let us know However, certain samples require a more detailed and some times graphical explanation. In these section you'll find details on samples that we believe require special attention. +
Loan Broker @@ -184,6 +184,7 @@ That includes Samples, so if you can't find what you are looking for let us know + The details and variations of this use case are very nicely described in Chapter 9 of the EIP Book, but here is the brief summary; A Consumer while shopping for the best Loan Quote(s) subscribes to the services of a Loan Broker, which handles details such as: @@ -247,7 +248,7 @@ That includes Samples, so if you can't find what you are looking for let us know The Messaging Gateway pattern provides a simple mechanism to access messaging systems, including our Loan Broker. In SI you define the Gateway as a Plain Old Java Interface (no need to provide an implementation), configure it via the - XML <gateway&gr; element or via annotation and use it as any other Spring bean. SI will take care of + XML <gateway> element or via annotation and use it as any other Spring bean. SI will take care of delegating and mapping method invocations to the Messaging infrastructure by generating a Message (payload is mapped to an input parameter of the method) and sending it to the designated channel. Conclusion As you can see a rather complex process was assembled based on POJO (read existing, legacy), light weight, embeddable messaging - framework (Sprig Integration) with a loosely coupled programming model intended to simplify integration of heterogeneous systems + framework (Spring Integration) with a loosely coupled programming model intended to simplify integration of heterogeneous systems without requiring a heavy-weight ESB-like engine or proprietary development and deployment environment, becouse as a developer you should not be porting your Swing or console-based application to an ESB-like server or implementing proprietary interfaces just because you have an integration concern. @@ -383,9 +384,7 @@ That includes Samples, so if you can't find what you are looking for let us know and should not require change in design, testing and deployment strategy if such applications need to integrate with one another.
- - - +
The Cafe Sample @@ -658,5 +657,4 @@ That includes Samples, so if you can't find what you are looking for let us know
-