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

Fix typos (SPR-7339)

Browse Source
This commit is contained in:
Chris Beams
2010-08-07 13:57:23 +00:00
parent 5ce4cada53
commit d97f899bee
17 changed files with 85 additions and 80 deletions
Download Patch File Download Diff File Expand all files Collapse all files

13
spring-framework-reference/src/transaction.xml
View File

@@ -354,10 +354,9 @@ TR:REVISED, PLS REVIEW-->
<property name="password" value="${jdbc.password}" />
&lt;/bean&gt;</programlisting>
<para>The related <interfacename>The
PlatformTransactionManager</interfacename> bean definition will then have
a reference to the <interfacename>DataSource</interfacename> definition.
It will look like this:</para>
<para>The related <interfacename>PlatformTransactionManager</interfacename>
bean definition will then have a reference to the
<interfacename>DataSource</interfacename> definition. It will look like this:</para>
<programlisting language="xml">&lt;bean id="txManager" class="org.springframework.jdbc.datasource.DataSourceTransactionManager"&gt;
&lt;property name="dataSource" ref="dataSource"/&gt;
@@ -629,7 +628,7 @@ TR: REVISED, PLS REVIEW - rewrote this to hoefully make it more clear--></para>
<para>The Spring Framework enables you to customize transactional
behavior, by using AOP. For example, you can insert custom behavior in
the case of transaction rollback. You can also add arbitrary advice,
along with the transactional advice. With EJB CMT, cannot influence
along with the transactional advice. With EJB CMT, you cannot influence
the container's transaction management except with
<methodname>setRollbackOnly()</methodname>.</para>
</listitem>
@@ -1858,7 +1857,7 @@ TR: REVISED, PLS REVIEW - changed it back; it's not just settings, the section d
<para>When the propagation setting is
<literal>PROPAGATION_REQUIRED</literal>, a
<emphasis>logical</emphasis> transaction scope is created for each
method that to which the setting is applied. Each such logical
method upon which the setting is applied. Each such logical
transaction scope can determine rollback-only status individually,
with an outer transaction scope being logically independent from the
inner transaction scope. Of course, in case of standard
@@ -2137,7 +2136,7 @@ TR: REVISED, PLS REVIEW. changed to 'desired'; seems clear that the desired orde
the aspect. The simplest way to configure the transaction management
aspect is to use the <literal>&lt;tx:annotation-driven/&gt;</literal>
element and specify the <literal>mode</literal> attribute to
<literal>asepctj</literal> as described in <xref
<literal>aspectj</literal> as described in <xref
linkend="transaction-declarative-annotations" />. Because we're focusing
here on applications running outside of a Spring container, we'll show
you how to do it programmatically.</para>