Update for first release
git-svn-id: https://svn.apache.org/repos/asf/aries/site/trunk/content@1750889 13f79535-47bb-0310-9956-ffa450edef68
diff --git a/modules/transactioncontrol.mdtext b/modules/transactioncontrol.mdtext
index 41e14a5..cfaf0b0 100644
--- a/modules/transactioncontrol.mdtext
+++ b/modules/transactioncontrol.mdtext
@@ -16,10 +16,12 @@
#Getting started
-If you're new to the Transaction Control service then we recommend that you read the
-[quickstart documentation first][2].
+The current released version of Transaction Control is 0.0.1, and it is available in [Maven Central][2]
-More detailed documentation is available in the [Aries Transaction Control Project][3]
+If you're new to the Transaction Control service then we recommend that you read the
+[quickstart documentation first][3].
+
+More detailed documentation is available in the [Aries Transaction Control Project][4]
## Why use the Transaction Control service?
@@ -29,33 +31,33 @@
In addition to being simple the Transaction Control service also makes transaction management explicit. As a
result it is easier to follow the transactions flowing throughout your code, and it protects you from the
-[proxy problem][4] that declarative transaction strategies often suffer from.
+[proxy problem][5] that declarative transaction strategies often suffer from.
## Modules
The following modules are available for use in OSGi
-1. [tx-control-service-local][5] :- A purely local transaction control service implementation. This can be
+1. [tx-control-service-local][6] :- A purely local transaction control service implementation. This can be
used with any resource-local capable ResourceProvider
-2. [tx-control-service-xa][6] :- An XA-capable transaction control service implementation based on the
+2. [tx-control-service-xa][7] :- An XA-capable transaction control service implementation based on the
Geronimo Transaction Manager. This can be used with XA capable resources, or with local resources.
Local resources will make use of the last-participant gambit.
-3. [tx-control-provider-jdbc-local][7] :- A JDBC resource provider that provides connection pooling and
+3. [tx-control-provider-jdbc-local][8] :- A JDBC resource provider that provides connection pooling and
that can integrate with local transactions. The JDBCConnectionProviderFactory service may be used
directly, or a service may be configured using the _org.apache.aries.tx.control.jdbc.local_ pid
-4. [tx-control-provider-jdbc-xa][8] :- A JDBC resource provider that provides connection pooling and
+4. [tx-control-provider-jdbc-xa][9] :- A JDBC resource provider that provides connection pooling and
that can integrate with local or XA transactions. The JDBCConnectionProviderFactory service may be
used directly, or a service may be configured using the _org.apache.aries.tx.control.jdbc.xa_ pid
-5. [tx-control-provider-jpa-local][9] :- A JPA resource provider that can integrate with local transactions.
+5. [tx-control-provider-jpa-local][10] :- A JPA resource provider that can integrate with local transactions.
The JPAEntityManagerProviderFactory service may be used directly, or a service may be configured using
the _org.apache.aries.tx.control.jpa.local_ pid. The implementation can also provide connection pooling
if required
-6. [tx-control-provider-jpa-xa][10] :- A JDBC resource provider that integrates with XA transactions.
+6. [tx-control-provider-jpa-xa][11] :- A JDBC resource provider that integrates with XA transactions.
The JPAEntityManagerProviderFactory service may be used directly, or a service may be configured using
the _org.apache.aries.tx.control.jpa.xa_ pid. The implementation can also provide connection pooling
if required
@@ -96,12 +98,13 @@
[1]: https://github.com/osgi/design/blob/master/rfcs/rfc0221/rfc-0221-TransactionControl.pdf
- [2]: tx-control/quickstart.html
- [3]: tx-control/index.html
- [4]: tx-control/spring-tx.html
- [5]: tx-control/localTransactions.html
- [6]: tx-control/xaTransactions.html
- [7]: tx-control/localJDBC.html
- [8]: tx-control/xaJDBC.html
- [9]: tx-control/localJPA.html
- [10]: tx-control/xaJPA.html
\ No newline at end of file
+ [2]: https://mvnrepository.com/artifact/org.apache.aries.tx-control
+ [3]: tx-control/quickstart.html
+ [4]: tx-control/index.html
+ [5]: tx-control/spring-tx.html
+ [6]: tx-control/localTransactions.html
+ [7]: tx-control/xaTransactions.html
+ [8]: tx-control/localJDBC.html
+ [9]: tx-control/xaJDBC.html
+ [10]: tx-control/localJPA.html
+ [11]: tx-control/xaJPA.html
\ No newline at end of file
diff --git a/modules/tx-control/quickstart.mdtext b/modules/tx-control/quickstart.mdtext
index bd1b812..15d41b3 100644
--- a/modules/tx-control/quickstart.mdtext
+++ b/modules/tx-control/quickstart.mdtext
@@ -21,10 +21,10 @@
To make use of scoped resources and transactions using the transaction control service you need two things:
* A <code>org.osgi.service.transaction.control.TransactionControl</code> implementation
-(found in the service registry)
+(found in the service registry). You may want to start with [local transactions][1].
* A <code>org.osgi.service.transaction.control.ResourceProvider</code> for each of the
-resources that you want to use.
+resources that you want to use. You may want to start with [local JDBC][2].
##Scoping Work using TransactionControl
@@ -62,15 +62,15 @@
methods can be used to ensure that a _No Transaction_ scope has been started.
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.
-There are also some things to consider if you're [migrating from Spring or Java EE][3].
+[more advanced scope control techniques][3] or [exception management][4] once you've mastered the basics.
+There are also some things to consider if you're [migrating from Spring or Java EE][5].
##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][4].
+needed you can [make your own ResourceProvider][6].
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
@@ -126,7 +126,9 @@
}
- [1]: advancedScopes.html
- [2]: exceptionManagement.html
- [3]: spring-tx.html
- [4]: advancedResourceProviders.html
\ No newline at end of file
+ [1]: localTransactions.html
+ [2]: localJDBC.html
+ [3]: advancedScopes.html
+ [4]: exceptionManagement.html
+ [5]: spring-tx.html
+ [6]: advancedResourceProviders.html
\ No newline at end of file
