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

BATCH-1192: updated docos to show transaction manager being used with MapJobRepositoryFactoryBean.

Browse Source
This commit is contained in:
dsyer
2009-04-08 12:48:37 +00:00
parent 4f39902ee8
commit 5c4f5906b8
1 changed files with 14 additions and 2 deletions
Download Patch File Download Diff File Expand all files Collapse all files

16
src/site/docbook/reference/job.xml
View File

@@ -370,14 +370,26 @@
this reason, Spring batch provides an in-memory Map version of the job
respository:</para>
<programlisting> &lt;bean id="jobRepository"
class="org.springframework.batch.core.repository.support.MapJobRepositoryFactoryBean" /&gt;</programlisting>
<programlisting><![CDATA[<bean id="jobRepository"
class="org.springframework.batch.core.repository.support.MapJobRepositoryFactoryBean">
<property name="transactionManager" ref="transactionManager"/>
</bean>
]]></programlisting>
<para>Note that the in-memory repository is volatile and so does not
allow restart between JVM instances. It also cannot guarantee that two
job instances with the same parameters are launched simultaneously. So
use the database version of the repository wherever you need quality of
service.</para>
<para>However it does require a transaction manager to be
defined because there are rollback semantics within the
repository, and because the business logic might still be
transactional (e.g. RDBMS access). For testing purposes many
people find
the <classname>ResourcelessTransactionManager</classname>
useful.</para>
</section>
<section>