svn commit: r792503 - in /websites/staging/openejb/trunk/content: configuring-persistenceunits-in-tests.html local-client-injection.html

[bu...@apache.org]

Author: buildbot
Date: Sun Jul 10 23:52:59 2011
New Revision: 792503

Log:
Staging update by buildbot

Modified:
    websites/staging/openejb/trunk/content/configuring-persistenceunits-in-tests.html
    websites/staging/openejb/trunk/content/local-client-injection.html

Modified: websites/staging/openejb/trunk/content/configuring-persistenceunits-in-tests.html
==============================================================================
--- websites/staging/openejb/trunk/content/configuring-persistenceunits-in-tests.html (original)
+++ websites/staging/openejb/trunk/content/configuring-persistenceunits-in-tests.html Sun Jul 10 23:52:59 2011
@@ -181,70 +181,65 @@ if we had to adjust the DataSources of y
 <p>You can override any property in your test setup via either system
 properties or the initial context properties.  The format is:</p>
 
-<p>{quote}<unit-name>.<property>=<value>{quote}</p>
+<p><code>&lt;unit-name&gt;.&lt;property&gt;=&lt;value&gt;</code></p>
 
 <p>So for example with the following persistence.xml:</p>
 
-<p>{code:xml|title=persistence.xml}
-<persistence>
-  <persistence-unit name="movie-unit">
-    <provider>org.hibernate.ejb.HibernatePersistence</provider>
-    <jta-data-source>movieDatabase</jta-data-source>
-    <non-jta-data-source>movieDatabaseUnmanaged</non-jta-data-source>
-    <properties>
-      <property name="hibernate.hbm2ddl.auto" value="create-drop"/>
-      <property name="hibernate.max_fetch_depth" value="3"/>
-    </properties>
-  </persistence-unit>
-</persistence></p>
-
-<pre><code>You can override and add persistence unit properties in your test case. 
+<pre><code>&lt;persistence&gt;
+  &lt;persistence-unit name="movie-unit"&gt;
+    &lt;provider&gt;org.hibernate.ejb.HibernatePersistence&lt;/provider&gt;
+    &lt;jta-data-source&gt;movieDatabase&lt;/jta-data-source&gt;
+    &lt;non-jta-data-source&gt;movieDatabaseUnmanaged&lt;/non-jta-data-source&gt;
+    &lt;properties&gt;
+      &lt;property name="hibernate.hbm2ddl.auto" value="create-drop"/&gt;
+      &lt;property name="hibernate.max_fetch_depth" value="3"/&gt;
+    &lt;/properties&gt;
+  &lt;/persistence-unit&gt;
+&lt;/persistence&gt;
 </code></pre>
 
-<p>There are currently no facilities for removing them (if you have a need for
+<p>You can override and add persistence unit properties in your test case.
+There are currently no facilities for removing them (if you have a need for
 that let us know -- it hasn't really come up so far).</p>
 
-<p>Properties p = new Properties();
-p.put(Context.INITIAL_CONTEXT_FACTORY,"org.apache.openejb.client.LocalInitialContextFactory");</p>
+<pre><code>Properties p = new Properties();
+p.put(Context.INITIAL_CONTEXT_FACTORY,"org.apache.openejb.client.LocalInitialContextFactory");
 
-<p>p.put("movie-unit.hibernate.hbm2ddl.auto", "update");
-p.put("movie-unit.hibernate.dialect", "org.hibernate.dialect.HSQLDialect");</p>
+p.put("movie-unit.hibernate.hbm2ddl.auto", "update");
+p.put("movie-unit.hibernate.dialect", "org.hibernate.dialect.HSQLDialect");
 
-<p>context = new InitialContext(p);</p>
+context = new InitialContext(p);
+</code></pre>
 
-<pre><code>The overriding order is as follows: 1 = highest, 4 = lowest.
+<p>The overriding order is as follows: 1 = highest, 4 = lowest.</p>
 
-# InitialContext properties
+<pre><code># InitialContext properties
 # jndi.properties from the classpath
 # System properties
 # persistence.xml properties
-
-By default there are no overrides in 1-3, so #4 is the only source of
 </code></pre>
 
-<p>information.  </p>
+<p>By default there are no overrides in 1-3, so #4 is the only source of
+information.  </p>
 
-<pre><code>In the above example there would be exactly three properties for the
-</code></pre>
+<p>In the above example there would be exactly three properties for the "movie-unit" persistence unit:</p>
 
-<p>"movie-unit" persistence unit:
-    - hibernate.hbm2ddl.auto = update
-    - hibernate.max_fetch_depth = 3
-    - hibernate.dialect = org.hibernate.dialect.HSQLDialect</p>
+<ul>
+<li>hibernate.hbm2ddl.auto = update</li>
+<li>hibernate.max_fetch_depth = 3</li>
+<li>hibernate.dialect = org.hibernate.dialect.HSQLDialect</li>
+</ul>
 
-<pre><code>These properties would be passed by OpenEJB directly to the persistence
-</code></pre>
-
-<p>provider (in this case Hibernate).  With one exception OpenEJB does not
+<p>These properties would be passed by OpenEJB directly to the persistence
+provider (in this case Hibernate).  With one exception OpenEJB does not
 understand or modify these properties.  Details on that one exception
 below.</p>
 
 <pre><code>h3.  No need to specify a "transaction lookup" property
-
-All vendors have such a property for getting a reference to the container's
 </code></pre>
 
-<p>TransactionManager and nothing works if this is not set correctly to the
+<p>All vendors have such a property for getting a reference to the container's
+TransactionManager and nothing works if this is not set correctly to the
 OpenEJB specific class.  To make the lives of users easier, OpenEJB will
 take the liberty of setting it for you.</p>
 

Modified: websites/staging/openejb/trunk/content/local-client-injection.html
==============================================================================
--- websites/staging/openejb/trunk/content/local-client-injection.html (original)
+++ websites/staging/openejb/trunk/content/local-client-injection.html Sun Jul 10 23:52:59 2011
@@ -239,7 +239,7 @@ deployed.
 annotations will be treated specially and always loaded by the parent
 classloader</p>
 
-<p>{quote}openejb.tempclassloader.skip=annotations{quote}</p>
+<p><code>openejb.tempclassloader.skip=annotations</code></p>
 
             </DIV>
           </P>