svn commit: r846861 - in /websites/staging/rave/trunk/content: ./ documentation/mongo-db.html

[bu...@apache.org]

Author: buildbot
Date: Wed Jan 16 15:48:20 2013
New Revision: 846861

Log:
Staging update by buildbot for rave

Modified:
    websites/staging/rave/trunk/content/   (props changed)
    websites/staging/rave/trunk/content/documentation/mongo-db.html

Propchange: websites/staging/rave/trunk/content/
------------------------------------------------------------------------------
--- cms:source-revision (original)
+++ cms:source-revision Wed Jan 16 15:48:20 2013
@@ -1 +1 @@
-1433927
+1433996

Modified: websites/staging/rave/trunk/content/documentation/mongo-db.html
==============================================================================
--- websites/staging/rave/trunk/content/documentation/mongo-db.html (original)
+++ websites/staging/rave/trunk/content/documentation/mongo-db.html Wed Jan 16 15:48:20 2013
@@ -88,7 +88,7 @@
         <article class="span12">
           <p>As of 0.19, Rave has a <a href="http://www.mongodb.org">MongoDB</a> module that provides implementations for all of Rave's repository interfaces; thus providing support for MongoDB.<br />
 </p>
-<h1 id="using-the-mongodb-for-persistence">Using the MongoDB for Persistence</h1>
+<h1 id="using-mongodb-for-persistence">Using MongoDB for Persistence</h1>
 <p>JPA remains the primary supported data access method in the rave-portal &amp; rave-portal-resources projects; but can be easily replaced with MongoDB using the following techniques:</p>
 <h2 id="build-from-source">Build from source</h2>
 <p>To build a MongoDB version of the demo binaries follow these steps:</p>
@@ -98,8 +98,8 @@
 </ol>
 <p>The rave-portal, rave-portal-resources &amp; rave-shindig wars created by this process contain everything needed to run Rave with MongoDB persistence.  See <a href="#configure">configuring MongoDB</a> for information on how to set the database properties.</p>
 <h2 id="custom-rave-extension">Custom Rave Extension</h2>
-<p>In a custom build that depends on rave-jpa directly, the only thing that needs to be done is to replace the rave-jpa dependency with rave-mongo.</p>
-<p>If the custom application depends on JPA indirectly, via a dependency on rave-portal-dependencies add an exclusion of rave-jpa to rave-portal-dependencies as follows:</p>
+<p>In a custom build that depends on rave-jpa directly, the only thing that needs to be done is to replace the rave-jpa dependency with rave-mongodb.</p>
+<p>If the custom application depends on JPA indirectly, via a dependency on rave-portal-dependencies, add an exclusion of rave-jpa to rave-portal-dependencies as follows:</p>
 <div class="codehilite"><pre> <span class="nt">&lt;dependency&gt;</span>
     <span class="nt">&lt;groupId&gt;</span>org.apache.rave<span class="nt">&lt;/groupId&gt;</span>
     <span class="nt">&lt;artifactId&gt;</span>rave-portal-dependencies<span class="nt">&lt;/artifactId&gt;</span>
@@ -126,7 +126,7 @@
 <li>Remove rave-jpa.jar from webapps/portal/WEB-INF/lib &amp; webapps/ROOT/WEB-INF/lib</li>
 <li>Configure the properties files located in webapps/portal/WEB-INF/classes &amp; webapps/ROOT/WEB-INF/classes per <a href="#configure">configuring MongoDB</a> </li>
 </ol>
-<p><a name="configuring">&nbsp;</a></p>
+<p><a name="configure">&nbsp;</a></p>
 <h2 id="configuring-mongodb">Configuring MongoDB</h2>
 <p>Both portal.properties &amp; rave.shindig.properties have entries for connecting to MongoDB. </p>
 <div class="codehilite"><pre><span class="n">mongo</span><span class="o">.</span><span class="n">host</span><span class="o">=</span><span class="n">localhost</span>