svn commit: r805575 - in /websites/staging/openejb/trunk: ./ content/configuring-datasources-in-tests.html

[bu...@apache.org]

Author: buildbot
Date: Tue Feb 21 01:54:29 2012
New Revision: 805575

Log:
Staging update by buildbot for openejb

Modified:
    websites/staging/openejb/trunk/   (props changed)
    websites/staging/openejb/trunk/content/configuring-datasources-in-tests.html

Propchange: websites/staging/openejb/trunk/
------------------------------------------------------------------------------
--- cms:source-revision (original)
+++ cms:source-revision Tue Feb 21 01:54:29 2012
@@ -1 +1 @@
-1291544
+1291548

Modified: websites/staging/openejb/trunk/content/configuring-datasources-in-tests.html
==============================================================================
--- websites/staging/openejb/trunk/content/configuring-datasources-in-tests.html (original)
+++ websites/staging/openejb/trunk/content/configuring-datasources-in-tests.html Tue Feb 21 01:54:29 2012
@@ -141,7 +141,7 @@
 <h1>InitialContext properties</h1>
 
 <p>You can configure data sources from within your test case (avoiding the
-need for an openejb.xml entirely) like so:</p>
+need for an <code>openejb.xml</code> entirely) like so:</p>
 
 <pre><code>Properties p = new Properties();
 p.put(Context.INITIAL_CONTEXT_FACTORY, "org.apache.openejb.client.LocalInitialContextFactory");
@@ -162,23 +162,23 @@ Context context = new InitialContext(p);
 
 <p><a name="ConfiguringDataSourcesinTests-Noteon<jta-data-source>and<non-jta-data-source>"></a></p>
 
-<h2>Note on <jta-data-source> and <non-jta-data-source></h2>
+<h2>Note on &lt;jta-data-source> and &lt;non-jta-data-source></h2>
 
 <p>When configuring DataSources to be used by persistence.xml files, the
-DataSource supplied for <jta-data-source> is typically identical to the
-<non-jta-data-source>, but with the JtaManaged property set differently. 
+DataSource supplied for <code>&lt;jta-data-source&gt;</code> is typically identical to the
+<code>&lt;non-jta-data-source&gt;</code>, but with the <code>JtaManaged</code> property set differently.
 Keeping with our philosophy to free you up from redundant configuration, we
 will happily auto-create a missing jta-data-source or non-jta-data-source
 based upon the supplied DataSource.</p>
 
 <p>In the example above, a new DataSource would be generated as an exact copy
-but with the name "myDataSourceUnmanaged" and its JtaManaged flag set to
-false.  If the supplied DataSource was not JtaManaged, then the generated
-DataSource would be called "myDataSourceJta" and have its JtaManaged flag
-set to true.</p>
+but with the name "myDataSourceUnmanaged" and its <code>JtaManaged</code> flag set to
+<code>false</code>.    If the supplied DataSource was not <code>JtaManaged</code>, then the generated
+DataSource would be called "myDataSourceJta" and have its <code>JtaManaged</code> flag
+set to <code>true</code>.</p>
 
 <p>When relying on this functionality it is not necessary to specify the name
-of the generated DataSource in the persistence.xml file.</p>
+of the generated DataSource in the <code>persistence.xml</code> file.</p>