diff --git a/src/reference/docbook/images/logo.png b/src/reference/docbook/images/logo.png
deleted file mode 100644
index a9f6d959e7..0000000000
Binary files a/src/reference/docbook/images/logo.png and /dev/null differ
diff --git a/src/reference/docbook/index.xml b/src/reference/docbook/index.xml
index 7758606a0a..4f38687421 100644
--- a/src/reference/docbook/index.xml
+++ b/src/reference/docbook/index.xml
@@ -8,18 +8,6 @@
Spring Integration
${version}
-
-
-
-
-
-
-
-
-
-
-
Mark
diff --git a/src/reference/docbook/preface.xml b/src/reference/docbook/preface.xml
index f2f90d6b1c..b749a7b2fb 100644
--- a/src/reference/docbook/preface.xml
+++ b/src/reference/docbook/preface.xml
@@ -1,27 +1,75 @@
- Preface
-
+ Preface
+
+ Requirements
+
+ This section details the compatible
+ Java
+ and Spring Framework
+ versions.
+
+
+ Compatible Java Versions
+
+ For Spring Integration 3.0.x,
+ the minimum compatible Java
+ version is Java SE 6.
+ Older versions of Java will not be supported any longer.
+
+
+ Spring Integration 3.0.x
+ is also compatible with Java SE 7 as well
+ as Java SE 8 (once released).
+
+
+ Spring Integration 2.2.x
+ is the last version that is compatible with Java 5 (J2SE 5.0).
+
+
+
+ Compatible Versions of the Spring Framework
+
+ The default dependency used by Spring Integration
+ 3.0.0.RELEASE is
+ Spring Framework 3.1.4.RELEASE.
+
+
+ Generally, Spring Integration 3.0.x
+ is compatible with the following Spring Framework releases:
+
+
+ Spring Framework 3.1.x
+ Spring Framework 3.2.x
+ Spring Framework 4.0.x
+
+
+ Spring Integration 2.2.x
+ is the last version that is compatible with Spring Framework
+ 3.0.x.
+
+
+
Code Conventions
- The Spring Framework 2.0 introduced support for namespaces, which
- simplifies the Xml configuration of the application context, and consequently
- Spring Integration provides broad namespace support. This reference guide
- applies the following conventions for all code examples that use namespace
- support:
+ The Spring Framework 2.0 introduced support for namespaces, which
+ simplifies the Xml configuration of the application context, and consequently
+ Spring Integration provides broad namespace support. This reference guide
+ applies the following conventions for all code examples that use namespace
+ support:
- The int namespace prefix will be used for
- Spring Integration's core namespace support. Each Spring Integration adapter
+ The int namespace prefix will be used for
+ Spring Integration's core namespace support. Each Spring Integration adapter
type (module) will provide its own namespace, which is configured using the
following convention:
-
- int- followed by the name of the module, e.g.
- int-twitter,
+
+ int- followed by the name of the module, e.g.
+ int-twitter,
int-stream, …
-
+
…
]]>
-
+
For a detailed explanation regarding Spring Integration's namespace support
see .
- Please note that the namespace prefix can be freely chosen. You may
- even choose not to use any namespace prefixes at all. Therefore,
- apply the convention that suits your application needs best. Be aware,
- though, that SpringSource Tool Suite™ (STS) uses the same namespace
- conventions for Spring Integration as used in this reference guide.
+ Please note that the namespace prefix can be freely chosen. You may
+ even choose not to use any namespace prefixes at all. Therefore,
+ apply the convention that suits your application needs best. Be aware,
+ though, that SpringSource Tool Suite™ (STS) uses the same namespace
+ conventions for Spring Integration as used in this reference guide.
-
+