86b5066a96
Problems
- Eliminate — in favor of —
— was causing 'no such entity' errors during docbook
processing; — produces the equivalent output.
- Fix column issues in appendices
column counts were set to 3, when they are in fact 4. This passed
under DocBook 4 and Spring Build for unknown reasons, but caused a
hard stop under DocBook 5 and the docbook-reference-plugin.
- Add jdbc callout section in docbook 5-friendly style
use <co/> tags as advertised in DocBook documentation.
- Set correct widths for PDF ref doc images
images were rendering larger than the PDF page; just set all to
width=400 and everything looks good.
Polish
- Update reference doc copyright to 2012
- Remove "work-in-progress" language from ref docs
- Update maven URLs to repo.springsource.org
- Update javadoc urls from 3.0.x/javadoc-api => current/api
- Replace hardcoded "3.1" with ${version} in ref doc
39 lines
2.1 KiB
XML
39 lines
2.1 KiB
XML
<?xml version="1.0" encoding="UTF-8"?>
|
|
<preface xmlns="http://docbook.org/ns/docbook" version="5.0"
|
|
xmlns:xlink="http://www.w3.org/1999/xlink"
|
|
xmlns:xi="http://www.w3.org/2001/XInclude"
|
|
xml:id="preface">
|
|
<title>Preface</title>
|
|
|
|
<para>Developing software applications is hard enough even with good tools
|
|
and technologies. Implementing applications using platforms which promise
|
|
everything but turn out to be heavy-weight, hard to control and not very
|
|
efficient during the development cycle makes it even harder. Spring provides
|
|
a light-weight solution for building enterprise-ready applications, while
|
|
still supporting the possibility of using declarative transaction
|
|
management, remote access to your logic using RMI or web services, and
|
|
various options for persisting your data to a database. Spring provides a
|
|
full-featured <link linkend="mvc-introduction">MVC framework</link>, and
|
|
transparent ways of integrating <link linkend="aop-introduction">AOP</link>
|
|
into your software.</para>
|
|
|
|
<para>Spring could potentially be a one-stop-shop for all your enterprise
|
|
applications; however, Spring is modular, allowing you to use just those
|
|
parts of it that you need, without having to bring in the rest. You can use
|
|
the IoC container, with Struts on top, but you could also choose to use just
|
|
the <link linkend="orm-hibernate">Hibernate integration code</link> or the
|
|
<link linkend="jdbc-introduction">JDBC abstraction layer</link></para>
|
|
|
|
<para>Spring has been (and continues to be) designed to be non-intrusive,
|
|
meaning dependencies, from your domain logic code, on the framework itself
|
|
are generally none. For your integration layer like the data access layer
|
|
there will of course be some dependencies on the data access technology in
|
|
use and also on the Spring libraries, but these dependencies should be easy
|
|
to isolate from the rest of your code base.</para>
|
|
|
|
<para>This document provides a reference guide to Spring's features. If you
|
|
have any requests or comments, please add an issue at
|
|
<ulink url="http://jira.springsource.org/SPR" />.
|
|
</para>
|
|
</preface>
|