aries-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
Subject svn commit: r1744546 - /aries/site/trunk/content/modules/tx-control/quickstart.mdtext
Date Thu, 19 May 2016 09:46:01 GMT
Author: timothyjward
Date: Thu May 19 09:46:01 2016
New Revision: 1744546

Add a link to Exception Management in the quick start


Modified: aries/site/trunk/content/modules/tx-control/quickstart.mdtext
--- aries/site/trunk/content/modules/tx-control/quickstart.mdtext (original)
+++ aries/site/trunk/content/modules/tx-control/quickstart.mdtext Thu May 19 09:46:01 2016
@@ -61,14 +61,15 @@ The scope starts immediately before the
 _Transactional_ scope has been started. The <code>supports</code> and <code>notSupported</code>
 methods can be used to ensure that a _No Transaction_ scope has been started.
-For more advanced scope control techniques look [here][1]
+Simple scope management is perfect in most situations, but you may also wish to read about
+[more advanced scope control techniques][1] or [exception management][2] once you've mastered
the basics.
 ##Accessing Resources
 A <code>ResourceProvider</code> is a generic factory for scoped resources. Typically
you will use a more 
 specific interface for type safety. For example the Transaction Control specification defines

 <code>JDBCConnectionProvider</code> and <code>JPAEntityManagerProvider</code>
interfaces. If
-needed you can [make your own ResourceProvider][2].
+needed you can [make your own ResourceProvider][3].
 To create your scoped resource you make one call to <code>getResource</code>
passing in the 
 <code>TransactionControl</code> service that the resource should integrate with.
The returned object
@@ -123,5 +124,7 @@ The transactionality and lifecycle of th
   [1]: advancedScopes.html
-  [2]: advancedResourceProviders.html
\ No newline at end of file
+  [2]: exceptionManagement.html
+  [3]: advancedResourceProviders.html
\ No newline at end of file

View raw message