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
><interfacename>ApplicationContext</interfacename></ulink> interface, which
extends the <interfacename>BeanFactory</interfacename> interface, in
addition to extending other interfaces to provide additional functionality
@ -635,7 +635,7 @@ argument.required=Ebagum lad, the '{0}' argument is required, I say, required.</
@@ -635,7 +635,7 @@ argument.required=Ebagum lad, the '{0}' argument is required, I say, required.</
@ -150,7 +150,7 @@ component-scanning in the exact same way as when using Spring annotations:
@@ -150,7 +150,7 @@ component-scanning in the exact same way as when using Spring annotations:
<row>
<entry>@Component</entry>
<entry>@Named</entry>
<entry>—</entry>
<entry>—</entry>
</row>
<row>
<entry>@Scope("singleton")</entry>
@ -174,21 +174,21 @@ component-scanning in the exact same way as when using Spring annotations:
@@ -174,21 +174,21 @@ component-scanning in the exact same way as when using Spring annotations:
@ -29,11 +29,11 @@ The footnote should x-ref to first section in that chapter but I can't find the
@@ -29,11 +29,11 @@ The footnote should x-ref to first section in that chapter but I can't find the
<para>The <literal>org.springframework.beans</literal> and
<literal>org.springframework.context</literal> packages are the basis for
Spring Framework's IoC container. The <interfacename><ulink
>ApplicationContext</ulink></literal> is a sub-interface of
<interfacename>BeanFactory.</interfacename> It adds easier integration
with Spring's AOP features; message resource handling (for use in
@ -80,9 +80,9 @@ The footnote should x-ref to first section in that chapter but I can't find the
@@ -80,9 +80,9 @@ The footnote should x-ref to first section in that chapter but I can't find the
<classname>ApplicationContext</classname> interface are supplied
out-of-the-box with Spring. In standalone applications it is common to
<!-- MLP: Beverly to review --> While XML has been the traditional format
for defining configuration metadata you can instruct the container to use
@ -109,7 +109,7 @@ The footnote should x-ref to first section in that chapter but I can't find the
@@ -109,7 +109,7 @@ The footnote should x-ref to first section in that chapter but I can't find the
@ -2600,93 +2600,74 @@ public class TitlesAfterDateStoredProcedure extends StoredProcedure {
@@ -2600,93 +2600,74 @@ public class TitlesAfterDateStoredProcedure extends StoredProcedure {
of a <classname>DefaultLobHandler</classname>. You typically set this
value through dependency injection.<!--Rewording ok? (What does what through dependency injection?) TR: Revised.--></para>
<!--
<programlistingco>
<areaspec>
<areacoords="8"id="jdbc.lobhandler.variableref"/>
<areacoords="12"id="jdbc.lobhandler.setClob"/>
<areacoords="13"id="jdbc.lobhandler.setBlob"/>
</areaspec>
<programlistinglanguage="java">final File blobIn = new File("spring2004.jpg");
<programlistinglanguage="java"><![CDATA[final File blobIn = new File("spring2004.jpg");
final InputStream blobIs = new FileInputStream(blobIn);
final File clobIn = new File("large.txt");
final InputStream clobIs = new FileInputStream(clobIn);
final InputStreamReader clobReader = new InputStreamReader(clobIs);
jdbcTemplate.execute(
"INSERT INTO lob_table (id, a_clob, a_blob) VALUES (?, ?, ?)",
new AbstractLobCreatingPreparedStatementCallback(lobHandler) {
new AbstractLobCreatingPreparedStatementCallback(lobHandler) {]]><coid="lobHandler"/><![CDATA[
@ -97,7 +97,7 @@ TR: This section doesn't read well and I think we should try to rewrite it.-->Nu
@@ -97,7 +97,7 @@ TR: This section doesn't read well and I think we should try to rewrite it.-->Nu
@ -680,7 +691,7 @@ public class Application {
@@ -680,7 +691,7 @@ public class Application {
This will make sure that only the registered classes are eligible for unmarshalling.
</para>
<para>
Additionally, you can register <ulinkurl="http://static.springsource.org/spring/docs/3.0.x/javadoc-api/org/springframework/oxm/xstream/XStreamMarshaller.html#setConverters(com.thoughtworks.xstream.converters.ConverterMatcher[])">
Additionally, you can register <ulinkurl="http://static.springsource.org/spring/docs/current/api/org/springframework/oxm/xstream/XStreamMarshaller.html#setConverters(com.thoughtworks.xstream.converters.ConverterMatcher[])">
custom converters</ulink> to make sure that only your supported classes can be unmarshalled.
@ -718,7 +718,8 @@ TR: OK AS IS. images don't show up in the editor, but they do show up in the gen
@@ -718,7 +718,8 @@ TR: OK AS IS. images don't show up in the editor, but they do show up in the gen
@ -1847,13 +1848,18 @@ TR: REVISED, PLS REVIEW - changed it back; it's not just settings, the section d
@@ -1847,13 +1848,18 @@ TR: REVISED, PLS REVIEW - changed it back; it's not just settings, the section d
Find below an example which shows how a <literal>static</literal> field is exposed, by
using the <ulinkurl="http://static.springframework.org/spring/docs/3.0.x/javadoc-api/org/springframework/beans/factory/config/FieldRetrievingFactoryBean.html#setStaticField(java.lang.String)"><literal>staticField</literal></ulink>
using the <ulinkurl="http://static.springframework.org/spring/docs/current/api/org/springframework/beans/factory/config/FieldRetrievingFactoryBean.html#setStaticField(java.lang.String)"><literal>staticField</literal></ulink>
Chris Beams
14 years ago