You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@isis.apache.org by bu...@apache.org on 2014/02/11 01:26:40 UTC
svn commit: r897313 - in /websites/staging/isis/trunk: cgi-bin/ content/
content/reference/services/command-context.html
Author: buildbot
Date: Tue Feb 11 00:26:39 2014
New Revision: 897313
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/command-context.html
Propchange: websites/staging/isis/trunk/cgi-bin/
------------------------------------------------------------------------------
--- cms:source-revision (original)
+++ cms:source-revision Tue Feb 11 00:26:39 2014
@@ -1 +1 @@
-1566892
+1566893
Propchange: websites/staging/isis/trunk/content/
------------------------------------------------------------------------------
--- cms:source-revision (original)
+++ cms:source-revision Tue Feb 11 00:26:39 2014
@@ -1 +1 @@
-1566892
+1566893
Modified: websites/staging/isis/trunk/content/reference/services/command-context.html
==============================================================================
--- websites/staging/isis/trunk/content/reference/services/command-context.html (original)
+++ websites/staging/isis/trunk/content/reference/services/command-context.html Tue Feb 11 00:26:39 2014
@@ -277,7 +277,7 @@
</h1>
</div>
-<p>The <code>CommandContext</code> service is a <a href="../../applib-guide/domain-services/how-to-09-020-How-to-write-a-typical-domain-service.html">request-scoped</a> service that reifies the invocation of an action on a domain object into an object itself. This reified information is encapsulated within the <code>Command</code> object.</p>
+<p>The <code>CommandContext</code> service is a <a href="../../more-advanced-topics/how-to-09-020-How-to-write-a-typical-domain-service.html">request-scoped</a> service that reifies the invocation of an action on a domain object into an object itself. This reified information is encapsulated within the <code>Command</code> object.</p>
<p>By default, the <code>Command</code> is held in-memory only; once the action invocation has completed, the <code>Command</code> object is gone. The optional
supporting <code>CommandService</code> enables the implementation of <code>Command</code> to be pluggable, however, enabling the <code>Command</code> to be persisted.</p>
@@ -291,7 +291,7 @@
<li>if <a href="./publishing-service.html">publishing</a> is configured, they provide better traceability as the <code>Command</code> is also correlated with any published events, again through the unique <code>transactionId</code> GUID</li>
</ul>
-<p>Assuming that the <code>CommandService</code> supports persistent <code>Command</code>s, the associated <a href="../../applib-guide/reference/recognized-annotations/Command.html">@Command</a> annotation also allows action invocations to be performed in the background. In this case the act of invoking the action on an object instead returns the <code>Command</code> to the user.</p>
+<p>Assuming that the <code>CommandService</code> supports persistent <code>Command</code>s, the associated <a href="../recognized-annotations/Command.html">@Command</a> annotation also allows action invocations to be performed in the background. In this case the act of invoking the action on an object instead returns the <code>Command</code> to the user.</p>
<h3>API</h3>
@@ -401,7 +401,7 @@ public class CommandContext {
<h3>Registering the Services</h3>
-<p>Register like any other service in <code>isis.properties</code>. For example, if using the core <code>CommandContext</code> service along with the <a href="../../components/objectstores/jdo/command-service.html">JDO implementation</a> of the <code>CommandService</code>, then it would be:</p>
+<p>Register like any other service in <code>isis.properties</code>. For example, if using the core <code>CommandContext</code> service along with the <a href="../../components/objectstores/jdo/command-service-jdo.html">JDO implementation</a> of the <code>CommandService</code>, then it would be:</p>
<pre><code>isis.services=...,\
org.apache.isis.applib.services.command.CommandContext,\