Spring/spring-batch
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

I didn't actually solve the problem. I don't know why the contents of repeat template being moved to a new chapter is causing site to fail. I commented out the <programlisting> fragment since Dave is refactoring the chapter anyway.

Browse Source
This commit is contained in:
wxlund
2008-03-06 18:41:22 +00:00
parent ce33690a89
commit 0dec169d9e
1 changed files with 27 additions and 20 deletions
Download Patch File Download Diff File Expand all files Collapse all files

47
docs/src/site/docbook/reference/repeat.xml
View File

@@ -24,7 +24,10 @@
as a queue or database. A common scenario when a batch job is a datastream
coming from a flat file interface is to have a file or files as input
sources and a database resource as the output source. In this case the
repeat templates can be used like the following:<!--
repeat templates can be used like the following:
</para>
<para>
<mediaobject>
<imageobject role="fo">
<imagedata align="center"
@@ -38,10 +41,12 @@
format="PNG" />
</imageobject>
<caption><para>Figure 2: Simple Batch Pseduo code for Repeat
Templates</para></caption>
<caption>
<para>Figure 2: Simple Batch Pseduo code for Repeat
Templates</para>
</caption>
</mediaobject>
--></para>
</para>
<para>In this batch scenario an outer RepeatTemplate initialies the
continuous flow, a TransactionTemplate wraps the input and output
@@ -55,22 +60,24 @@
the business processing is within the RepeatTemplates. It's only job is to
keep the flow moving from the Item Provider to the Item Processor as
quickly as possible. The repeat template can process records irrespective
of the batch architecture. A simple example would be: <programlisting>
RepeatTemplate template = new RepeatTemplate();
Resource resource = new FileSystemResource("resources/trades.csv");
TradeProcessor executor = new TradeProcessor();
TradeItemProvider provider = null;
try {
provider = new TradeItemProvider(resource);
} catch (Exception e) {
// TODO Auto-generated catch block
e.printStackTrace();
}
template.iterate(new ItemProviderRepeatCallback(provider, executor));
</programlisting></para>
of the batch architecture. A simple example would be:
<!--
<programlisting>
RepeatTemplate template = new RepeatTemplate();
Resource resource = new FileSystemResource("resources/trades.csv");
TradeProcessor executor = new TradeProcessor();
TradeItemProvider provider = null;
try {
provider = new TradeItemProvider(resource);
} catch (Exception e) {
// TODO Auto-generated catch block
e.printStackTrace();
}
template.iterate(new ItemProviderRepeatCallback(provider, executor));
</programlisting>
-->
</para>
<para>A RepeatTemplate has an exception policy that can be
leveraged</para>
</section>
</chapter>
</chapter>