You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cayenne.apache.org by aa...@apache.org on 2019/10/30 08:34:36 UTC
[cayenne-website] branch asf-site updated: republishing docs
This is an automated email from the ASF dual-hosted git repository.
aadamchik pushed a commit to branch asf-site
in repository https://gitbox.apache.org/repos/asf/cayenne-website.git
The following commit(s) were added to refs/heads/asf-site by this push:
new fb38f6e republishing docs
fb38f6e is described below
commit fb38f6e40629934d408bdc1d59f892532011442c
Author: Andrus Adamchik <an...@objectstyle.com>
AuthorDate: Wed Oct 30 11:34:32 2019 +0300
republishing docs
---
.DS_Store | Bin 6148 -> 0 bytes
docs/4.0/cayenne-guide/index.html | 9 ++++-----
docs/4.1/cayenne-guide/index.html | 9 ++++-----
img/cayenne-modeler-40rc1-a464d37d53.png | Bin 54843 -> 0 bytes
img/favicon/android-chrome-192x192-c8e800d2b0.png | Bin 1118 -> 0 bytes
img/favicon/android-chrome-512x512-f4a2f5a020.png | Bin 3391 -> 0 bytes
img/favicon/mstile-144x144-5f1d044e49.png | Bin 1144 -> 0 bytes
img/favicon/mstile-144x144-a94ba73eaf.png | Bin 1047 -> 0 bytes
img/favicon/mstile-150x150-0fe674a907.png | Bin 869 -> 0 bytes
img/favicon/mstile-150x150-13e731f590.png | Bin 1043 -> 0 bytes
img/favicon/mstile-310x150-0d0c5a17af.png | Bin 1141 -> 0 bytes
img/favicon/mstile-310x150-ff5e1a04ff.png | Bin 861 -> 0 bytes
img/favicon/mstile-310x310-a40d63b59e.png | Bin 1781 -> 0 bytes
img/favicon/mstile-310x310-b51c330c59.png | Bin 2371 -> 0 bytes
img/favicon/mstile-70x70-6e391d6d5c.png | Bin 650 -> 0 bytes
img/favicon/mstile-70x70-c524897489.png | Bin 724 -> 0 bytes
img/logo_mono_full-b893724c6c.svg.png | Bin 1468 -> 0 bytes
img/modeler-4-24b0368dc2.0-screen.png | Bin 52711 -> 0 bytes
img/modeler-dbimport-58df3bd3e6.png | Bin 74222 -> 0 bytes
img/modeler-screen-368bbb5de6.png | Bin 52415 -> 0 bytes
schema/.DS_Store | Bin 6148 -> 0 bytes
21 files changed, 8 insertions(+), 10 deletions(-)
diff --git a/.DS_Store b/.DS_Store
deleted file mode 100644
index cff8ab3..0000000
Binary files a/.DS_Store and /dev/null differ
diff --git a/docs/4.0/cayenne-guide/index.html b/docs/4.0/cayenne-guide/index.html
index 5ea2969..42851ea 100644
--- a/docs/4.0/cayenne-guide/index.html
+++ b/docs/4.0/cayenne-guide/index.html
@@ -1801,10 +1801,10 @@ generic.writeProperty("name", "New Name");</code></pre>
<p>Considering how much attention is given to managing transactions in most other ORMs, transactions have been conspicuously absent from the ObjectContext discussion till now. The reason is that transactions are seamless in Cayenne in all but a few special cases. ObjectContext is an in-memory container of objects that is disconnected from the database, except when it needs to run an operation. So it does not care about any surrounding transaction scope. Sure enough all database oper [...]
</div>
<div class="paragraph">
- <p>Two cases where transactions need to be taken into consideration are container-managed and application-managed transactions.</p>
+ <p>Two cases where transactions need to be taken into consideration are container- and application-managed transactions.</p>
</div>
<div class="paragraph">
- <p>If you are using an EJB container (or some other JTA environment), you’ll likely need to switch Cayenne runtime into "external transactions mode". This is done by setting DI configuration property defined in <code>Constants.SERVER_EXTERNAL_TX_PROPERTY</code> (see Appendix A). If this property is set to "true", Cayenne assumes that JDBC Connections obtained by runtime whenever that might happen are all coming from a transactional DataSource managed by the container. In this case C [...]
+ <p>If you are using Spring, EJB or another environment that manages transactions, you’ll likely need to switch Cayenne runtime into "external transactions mode". This is done by setting DI configuration property defined in <code>Constants.SERVER_EXTERNAL_TX_PROPERTY</code> (see Appendix A). If this property is set to "true", Cayenne assumes that JDBC Connections obtained by runtime whenever that might happen are all coming from a transactional DataSource managed by the container. In [...]
</div>
<div class="paragraph">
<p>In the second scenario, an application might need to define its own transaction scope that spans more than one Cayenne operation. E.g. two sequential commits that need to be rolled back together in case of failure. This can be done via <code>ServerRuntime.performInTransaction</code> method:</p>
@@ -1826,12 +1826,11 @@ generic.writeProperty("name", "New Name");</code></pre>
</div>
</div>
<div class="paragraph">
- <p>When inside the transaction, current thread Transaction object can be accessed via a static method. E.g. here is an example that initializes transaction JDBC connection with a custom connection object :</p>
+ <p>When inside a transaction, current thread Transaction object can be accessed via a static method:</p>
</div>
<div class="listingblock">
<div class="content">
- <pre class="highlight"><code class="language-java java" data-lang="java">Transaction tx = BaseTransaction.getThreadTransaction();
-tx.addConnection("mydatanode", myConnection);</code></pre>
+ <pre class="highlight"><code class="language-java java" data-lang="java">Transaction tx = BaseTransaction.getThreadTransaction();</code></pre>
</div>
</div>
</div>
diff --git a/docs/4.1/cayenne-guide/index.html b/docs/4.1/cayenne-guide/index.html
index e73c53d..8647cd9 100644
--- a/docs/4.1/cayenne-guide/index.html
+++ b/docs/4.1/cayenne-guide/index.html
@@ -1840,10 +1840,10 @@ generic.writeProperty("name", "New Name");</code></pre>
<p>Considering how much attention is given to managing transactions in most other ORMs, transactions have been conspicuously absent from the ObjectContext discussion till now. The reason is that transactions are seamless in Cayenne in all but a few special cases. ObjectContext is an in-memory container of objects that is disconnected from the database, except when it needs to run an operation. So it does not care about any surrounding transaction scope. Sure enough all database oper [...]
</div>
<div class="paragraph">
- <p>Two cases where transactions need to be taken into consideration are container-managed and application-managed transactions.</p>
+ <p>Two cases where transactions need to be taken into consideration are container- and application-managed transactions.</p>
</div>
<div class="paragraph">
- <p>If you are using an EJB container (or some other JTA environment), you’ll likely need to switch Cayenne runtime into "external transactions mode". This is done by setting DI configuration property defined in <code>Constants.SERVER_EXTERNAL_TX_PROPERTY</code> (see Appendix A). If this property is set to "true", Cayenne assumes that JDBC Connections obtained by runtime whenever that might happen are all coming from a transactional DataSource managed by the container. In this case C [...]
+ <p>If you are using Spring, EJB or another environment that manages transactions, you’ll likely need to switch Cayenne runtime into "external transactions mode". This is done by setting DI configuration property defined in <code>Constants.SERVER_EXTERNAL_TX_PROPERTY</code> (see Appendix A). If this property is set to "true", Cayenne assumes that JDBC Connections obtained by runtime whenever that might happen are all coming from a transactional DataSource managed by the container. In [...]
</div>
<div class="paragraph">
<p>In the second scenario, an application might need to define its own transaction scope that spans more than one Cayenne operation. E.g. two sequential commits that need to be rolled back together in case of failure. This can be done via <code>ServerRuntime.performInTransaction</code> method:</p>
@@ -1865,12 +1865,11 @@ generic.writeProperty("name", "New Name");</code></pre>
</div>
</div>
<div class="paragraph">
- <p>When inside the transaction, current thread Transaction object can be accessed via a static method. E.g. here is an example that initializes transaction JDBC connection with a custom connection object :</p>
+ <p>When inside a transaction, current thread Transaction object can be accessed via a static method:</p>
</div>
<div class="listingblock">
<div class="content">
- <pre class="highlight"><code class="language-java java" data-lang="java">Transaction tx = BaseTransaction.getThreadTransaction();
-tx.addConnection("mydatanode", myConnection);</code></pre>
+ <pre class="highlight"><code class="language-java java" data-lang="java">Transaction tx = BaseTransaction.getThreadTransaction();</code></pre>
</div>
</div>
<div class="paragraph">
diff --git a/img/cayenne-modeler-40rc1-a464d37d53.png b/img/cayenne-modeler-40rc1-a464d37d53.png
deleted file mode 100644
index 155d77c..0000000
Binary files a/img/cayenne-modeler-40rc1-a464d37d53.png and /dev/null differ
diff --git a/img/favicon/android-chrome-192x192-c8e800d2b0.png b/img/favicon/android-chrome-192x192-c8e800d2b0.png
deleted file mode 100644
index 2d7a971..0000000
Binary files a/img/favicon/android-chrome-192x192-c8e800d2b0.png and /dev/null differ
diff --git a/img/favicon/android-chrome-512x512-f4a2f5a020.png b/img/favicon/android-chrome-512x512-f4a2f5a020.png
deleted file mode 100644
index 53eaf3a..0000000
Binary files a/img/favicon/android-chrome-512x512-f4a2f5a020.png and /dev/null differ
diff --git a/img/favicon/mstile-144x144-5f1d044e49.png b/img/favicon/mstile-144x144-5f1d044e49.png
deleted file mode 100644
index e9ad16c..0000000
Binary files a/img/favicon/mstile-144x144-5f1d044e49.png and /dev/null differ
diff --git a/img/favicon/mstile-144x144-a94ba73eaf.png b/img/favicon/mstile-144x144-a94ba73eaf.png
deleted file mode 100644
index b0c413a..0000000
Binary files a/img/favicon/mstile-144x144-a94ba73eaf.png and /dev/null differ
diff --git a/img/favicon/mstile-150x150-0fe674a907.png b/img/favicon/mstile-150x150-0fe674a907.png
deleted file mode 100644
index c7e2f37..0000000
Binary files a/img/favicon/mstile-150x150-0fe674a907.png and /dev/null differ
diff --git a/img/favicon/mstile-150x150-13e731f590.png b/img/favicon/mstile-150x150-13e731f590.png
deleted file mode 100644
index 2a23695..0000000
Binary files a/img/favicon/mstile-150x150-13e731f590.png and /dev/null differ
diff --git a/img/favicon/mstile-310x150-0d0c5a17af.png b/img/favicon/mstile-310x150-0d0c5a17af.png
deleted file mode 100644
index 39eb111..0000000
Binary files a/img/favicon/mstile-310x150-0d0c5a17af.png and /dev/null differ
diff --git a/img/favicon/mstile-310x150-ff5e1a04ff.png b/img/favicon/mstile-310x150-ff5e1a04ff.png
deleted file mode 100644
index a16a0fb..0000000
Binary files a/img/favicon/mstile-310x150-ff5e1a04ff.png and /dev/null differ
diff --git a/img/favicon/mstile-310x310-a40d63b59e.png b/img/favicon/mstile-310x310-a40d63b59e.png
deleted file mode 100644
index 1038484..0000000
Binary files a/img/favicon/mstile-310x310-a40d63b59e.png and /dev/null differ
diff --git a/img/favicon/mstile-310x310-b51c330c59.png b/img/favicon/mstile-310x310-b51c330c59.png
deleted file mode 100644
index bfd3116..0000000
Binary files a/img/favicon/mstile-310x310-b51c330c59.png and /dev/null differ
diff --git a/img/favicon/mstile-70x70-6e391d6d5c.png b/img/favicon/mstile-70x70-6e391d6d5c.png
deleted file mode 100644
index 960737d..0000000
Binary files a/img/favicon/mstile-70x70-6e391d6d5c.png and /dev/null differ
diff --git a/img/favicon/mstile-70x70-c524897489.png b/img/favicon/mstile-70x70-c524897489.png
deleted file mode 100644
index 5c85dac..0000000
Binary files a/img/favicon/mstile-70x70-c524897489.png and /dev/null differ
diff --git a/img/logo_mono_full-b893724c6c.svg.png b/img/logo_mono_full-b893724c6c.svg.png
deleted file mode 100644
index d0f01cd..0000000
Binary files a/img/logo_mono_full-b893724c6c.svg.png and /dev/null differ
diff --git a/img/modeler-4-24b0368dc2.0-screen.png b/img/modeler-4-24b0368dc2.0-screen.png
deleted file mode 100644
index ccbda61..0000000
Binary files a/img/modeler-4-24b0368dc2.0-screen.png and /dev/null differ
diff --git a/img/modeler-dbimport-58df3bd3e6.png b/img/modeler-dbimport-58df3bd3e6.png
deleted file mode 100644
index 9ee5af7..0000000
Binary files a/img/modeler-dbimport-58df3bd3e6.png and /dev/null differ
diff --git a/img/modeler-screen-368bbb5de6.png b/img/modeler-screen-368bbb5de6.png
deleted file mode 100644
index b73b2c6..0000000
Binary files a/img/modeler-screen-368bbb5de6.png and /dev/null differ
diff --git a/schema/.DS_Store b/schema/.DS_Store
deleted file mode 100644
index b83a83c..0000000
Binary files a/schema/.DS_Store and /dev/null differ