From b90260f8d2df58ac639048bea683d4aae78fdea9 Mon Sep 17 00:00:00 2001
From: Chris Beams <cbeams@vmware.com>
Date: Wed, 11 Aug 2010 06:36:00 +0000
Subject: [PATCH] Link to Spring Integration at end of event coverage

---
 spring-framework-reference/src/beans.xml | 12 ++++++++++++
 1 file changed, 12 insertions(+)

diff --git a/spring-framework-reference/src/beans.xml b/spring-framework-reference/src/beans.xml
index a3523309527..f6669f8378b 100644
--- a/spring-framework-reference/src/beans.xml
+++ b/spring-framework-reference/src/beans.xml
@@ -7163,6 +7163,18 @@ argument.required=Ebagum lad, the '{0}' argument is required, I say, required.</
         <interfacename>ApplicationListener</interfacename> and thus receives the
         <classname>BlackListEvent</classname>, at which point it can notify
         appropriate parties.</para>
+
+        <note>
+          <para>Spring's eventing mechanism is designed for simple communication
+          between Spring beans within the same application context. However, for
+          more sophisticated enterprise integration needs, the separately-maintained
+          <ulink
+          url="http://springsource.org/spring-integration">Spring Integration</ulink>
+          project provides complete support for building lightweight, <ulink
+          url="http://www.enterpriseintegrationpatterns.com">pattern-oriented</ulink>,
+          event-driven architectures that build upon the well-known Spring
+          programming model.</para>
+        </note>
     </section>
 
     <section id="context-functionality-resources">