svn commit: r897492 - in /websites/staging/isis/trunk: cgi-bin/ content/ content/reference/services/background-service.html

[bu...@apache.org]

Author: buildbot
Date: Tue Feb 11 20:43:26 2014
New Revision: 897492

Log:
Staging update by buildbot for isis

Modified:
    websites/staging/isis/trunk/cgi-bin/   (props changed)
    websites/staging/isis/trunk/content/   (props changed)
    websites/staging/isis/trunk/content/reference/services/background-service.html

Propchange: websites/staging/isis/trunk/cgi-bin/
------------------------------------------------------------------------------
--- cms:source-revision (original)
+++ cms:source-revision Tue Feb 11 20:43:26 2014
@@ -1 +1 @@
-1567370
+1567372

Propchange: websites/staging/isis/trunk/content/
------------------------------------------------------------------------------
--- cms:source-revision (original)
+++ cms:source-revision Tue Feb 11 20:43:26 2014
@@ -1 +1 @@
-1567370
+1567372

Modified: websites/staging/isis/trunk/content/reference/services/background-service.html
==============================================================================
--- websites/staging/isis/trunk/content/reference/services/background-service.html (original)
+++ websites/staging/isis/trunk/content/reference/services/background-service.html Tue Feb 11 20:43:26 2014
@@ -286,7 +286,7 @@
 
 <p>The <code>BackgroundService</code> is responsible for capturing a memento representing the action invocation, and persisting it.  The default <code>BackgroundServiceDefault</code> implementation (provided by isis-core) uses (a private copy of) <a href="./memento-service.html">MementoService</a>, and then delegates the persistence of the memento to the companion <code>BackgroundCommandService</code> (discussed further <a href="#BackgroundCommandService">below</a>).</p>
 
-<p>The JDO objectstore provides an implementation of <code>BackgroundCommandService</code> (<a href="../../components/objectstores/jdo/background-command-service-jdo.html">BackgroundCommandServiceJdo</a>) that persists to an RBMS entities.  You are welcome to write other implementations to other data stores (eg NoSQL) if required.</p>
+<p>The JDO objectstore provides an implementation of <code>BackgroundCommandService</code> (<a href="../../components/objectstores/jdo/services/background-command-service-jdo.html">BackgroundCommandServiceJdo</a>) that persists to an RBMS entities.  You are welcome to write other implementations to other data stores (eg NoSQL) if required.</p>
 
 <p>The persisting of commands is only half the story; there needs to be a separate process  to read the commands and execute them.  The <code>BackgroundCommandExecution</code> class (also discussed <a href="#BackgroundCommandExecution">below</a> provides the mechanism to do this.</p>
 
@@ -393,7 +393,7 @@
 
 <h3>Implementation</h3>
 
-<p>The JDO object store provides the <a href="../../components/objectstores/jdo/background-command-service-jdo.html">BackgroundCommandServiceJdo</a> implementation that persists <code>Command</code>s to an RDBMS.</p>
+<p>The JDO object store provides the <a href="../../components/objectstores/jdo/services/background-command-service-jdo.html">BackgroundCommandServiceJdo</a> implementation that persists <code>Command</code>s to an RDBMS.</p>
 
 <h3>Usage</h3>
 
@@ -405,7 +405,7 @@
 
 <p>The core framework provides default implementations of <code>CommandContext</code> and also <code>BackgroundService</code>, and there is very little reason to use any other implementation.</p>
 
-<p>The implementations of <code>CommandService</code> and <code>BackgroundCommandService</code> also go together; typically both parent <code>Command</code>s and child background <code>Command</code>s will be persisted in the same way.  The JDO objectstore provides implementations of both (<a href="../../components/objectstores/jdo/command-service-jdo.html">CommandServiceJdo</a> and <a href="../../components/objectstores/jdo/background-command-service-jdo.html">BackgroundCommandServiceJdo</a>).</p>
+<p>The implementations of <code>CommandService</code> and <code>BackgroundCommandService</code> also go together; typically both parent <code>Command</code>s and child background <code>Command</code>s will be persisted in the same way.  The JDO objectstore provides implementations of both (<a href="../../components/objectstores/jdo/services/command-service-jdo.html">CommandServiceJdo</a> and <a href="../../components/objectstores/jdo/services/background-command-service-jdo.html">BackgroundCommandServiceJdo</a>).</p>
 
 <h2>BackgroundCommandExecution</h2>