You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@isis.apache.org by da...@apache.org on 2017/03/08 05:35:38 UTC
[09/15] isis-site git commit: ISIS-1594: fixes anchors for extension
point's conventions
http://git-wip-us.apache.org/repos/asf/isis-site/blob/dd1ff6a4/content/guides/rgsvc.html
----------------------------------------------------------------------
diff --git a/content/guides/rgsvc.html b/content/guides/rgsvc.html
index 5ab2ef1..98d970d 100644
--- a/content/guides/rgsvc.html
+++ b/content/guides/rgsvc.html
@@ -514,7 +514,7 @@ table.CodeRay td.code>pre{padding:0}
<button type="button" class="button secondary" onclick="window.location.href="https://github.com/apache/isis/edit/master/adocs/documentation/src/main/asciidoc/guides/_rgsvc_intro.adoc"" style="float: right; font-size: small; padding: 6px; margin-top: -55px; "><i class="fa fa-pencil-square-o"></i> Edit</button>
<div class="sectionbody">
<div class="sect2">
- <h3 id="_rgsvc_intro_types-of-domain-services">2.1. Types of Domain Service</h3>
+ <h3 id="__rgsvc_intro_types-of-domain-services">2.1. Types of Domain Service</h3>
<div class="paragraph">
<p>The domain services also group into various broad categories. Many support functionality of the various layers of the system (presentation layer, application layer, core domain, persistence layer); others exist to allow the domain objects to integrate with other bounded contexts, or provide various metadata (eg for development-time tooling). The diagram below shows these categories:</p>
</div>
@@ -534,7 +534,7 @@ table.CodeRay td.code>pre{padding:0}
</div>
</div>
<div class="sect2">
- <h3 id="_rgsvc_intro_public-api">2.2. Public API vs Internal Services</h3>
+ <h3 id="__rgsvc_intro_public-api">2.2. Public API vs Internal Services</h3>
<div class="paragraph">
<p>The vast majority of Apache Isis' domain services are defined in Apache Isis' applib (<code>o.a.i.core:isis-core-applib</code> module) as stable, public classes. Importantly, this also minimizes the coupling between your code and Apache Isis, allowing you to easily mock out these services in your unit tests.</p>
</div>
@@ -543,7 +543,7 @@ table.CodeRay td.code>pre{padding:0}
</div>
</div>
<div class="sect2">
- <h3 id="_rgsvc_intro_using-the-services">2.3. Using the services</h3>
+ <h3 id="__rgsvc_intro_using-the-services">2.3. Using the services</h3>
<div class="paragraph">
<p>Apache Isis includes an extensive number of domain services for your domain objects to use; simply define the service as an annotated field and Apache Isis will inject the service into your object.</p>
</div>
@@ -589,7 +589,7 @@ table.CodeRay td.code>pre{padding:0}
</div>
</div>
<div class="sect2">
- <h3 id="_rgsvc_intro_overriding-the-services">2.4. Overriding the services</h3>
+ <h3 id="__rgsvc_intro_overriding-the-services">2.4. Overriding the services</h3>
<div class="paragraph">
<p>The framework provides default implementations for many of the domain services. This is convenient, but sometimes you will want to replace the default implementation with your own service implementation.</p>
</div>
@@ -687,7 +687,7 @@ table.CodeRay td.code>pre{padding:0}
</div>
</div>
<div class="sect2">
- <h3 id="_rgsvc_intro_commands-and-events">2.5. Command and Events</h3>
+ <h3 id="__rgsvc_intro_commands-and-events">2.5. Command and Events</h3>
<div class="paragraph">
<p>A good number of the domain services manage the execution of action invocations/property edits, along with the state of domain objects that are modified as a result of these. These services capture information which can then be used for various purposes, most notably for auditing or for publishing events, or for deferring execution such that the execution be performed in the background at some later date.</p>
</div>
@@ -1165,7 +1165,7 @@ table.CodeRay td.code>pre{padding:0}
<p>Assuming that the <code>configuration-and-annotation</code> services installer is configured (implicit if using the <code>AppManifest</code> to <a href="rgcms.html#_rgcms_classes_AppManifest-bootstrapping">bootstrap the app</a>) then Apache Isis' default implementation of <code>EmailNotificationService</code> service is automatically registered and injected (it is annotated with <code>@DomainService</code>) so no further configuration is required.</p>
</div>
<div class="paragraph">
- <p>To use an alternative implementation, use <a href="rgant.html#_rgant-DomainServiceLayout_menuOrder"><code>@DomainServiceLayout#menuOrder()</code></a> (as explained in the <a href="#_rgsvc_intro_overriding-the-services">introduction</a> to this guide).</p>
+ <p>To use an alternative implementation, use <a href="rgant.html#_rgant-DomainServiceLayout_menuOrder"><code>@DomainServiceLayout#menuOrder()</code></a> (as explained in the <a href="#__rgsvc_intro_overriding-the-services">introduction</a> to this guide).</p>
</div>
</div>
<div class="sect3">
@@ -1564,7 +1564,7 @@ table.CodeRay td.code>pre{padding:0}
<p>Assuming that the <code>configuration-and-annotation</code> services installer is configured (implicit if using the <code>AppManifest</code> to <a href="rgcms.html#_rgcms_classes_AppManifest-bootstrapping">bootstrap the app</a>), then the Bootstrap3 default implementation of <code>GridSystemService</code> is automatically registered and injected, and no further configuration is required.</p>
</div>
<div class="paragraph">
- <p>To use an alternative implementation, use <a href="rgant.html#_rgant-DomainServiceLayout_menuOrder"><code>@DomainServiceLayout#menuOrder()</code></a> (as explained in the <a href="#_rgsvc_intro_overriding-the-services">introduction</a> to this guide).</p>
+ <p>To use an alternative implementation, use <a href="rgant.html#_rgant-DomainServiceLayout_menuOrder"><code>@DomainServiceLayout#menuOrder()</code></a> (as explained in the <a href="#__rgsvc_intro_overriding-the-services">introduction</a> to this guide).</p>
</div>
</div>
<div class="sect3">
@@ -1603,7 +1603,7 @@ table.CodeRay td.code>pre{padding:0}
</tr>
<tr>
<td><i class="conum" data-value="2"></i><b>2</b></td>
- <td>support metamodel invalidation/rebuilding of spec, eg as called by this <a href="rgcms.html#_rgcms_classes_mixins_Object_rebuildMetamodel">Object mixin</a> action.</td>
+ <td>support metamodel invalidation/rebuilding of spec, eg as called by this <a href="rgcms.html#__rgcms_classes_mixins_Object_rebuildMetamodel">Object mixin</a> action.</td>
</tr>
<tr>
<td><i class="conum" data-value="3"></i><b>3</b></td>
@@ -1611,7 +1611,7 @@ table.CodeRay td.code>pre{padding:0}
</tr>
<tr>
<td><i class="conum" data-value="4"></i><b>4</b></td>
- <td>returns a new instance of a <a href="rgcms.html#_rgcms_classes_layout_component"><code>Grid</code></a> for the specified domain class, eg as loaded from a <code>layout.xml</code> file. If none exists, will return null (and the calling <a href="#_rgsvc_spi_GridService"><code>GridService</code></a> will use <a href="#_rgsvc_spi_GridSystemService"><code>GridSystemService</code></a> to obtain a default grid for the domain class).</td>
+ <td>returns a new instance of a <a href="rgcms.html#__rgcms_classes_layout_component"><code>Grid</code></a> for the specified domain class, eg as loaded from a <code>layout.xml</code> file. If none exists, will return null (and the calling <a href="#_rgsvc_spi_GridService"><code>GridService</code></a> will use <a href="#_rgsvc_spi_GridSystemService"><code>GridSystemService</code></a> to obtain a default grid for the domain class).</td>
</tr>
</tbody>
</table>
@@ -1632,7 +1632,7 @@ table.CodeRay td.code>pre{padding:0}
<p>Assuming that the <code>configuration-and-annotation</code> services installer is configured (implicit if using the <code>AppManifest</code> to <a href="rgcms.html#_rgcms_classes_AppManifest-bootstrapping">bootstrap the app</a>), then the default implementation of <code>GridLoaderService</code> is automatically registered and injected, and no further configuration is required.</p>
</div>
<div class="paragraph">
- <p>To use an alternative implementation, use <a href="rgant.html#_rgant-DomainServiceLayout_menuOrder"><code>@DomainServiceLayout#menuOrder()</code></a> (as explained in the <a href="#_rgsvc_intro_overriding-the-services">introduction</a> to this guide).</p>
+ <p>To use an alternative implementation, use <a href="rgant.html#_rgant-DomainServiceLayout_menuOrder"><code>@DomainServiceLayout#menuOrder()</code></a> (as explained in the <a href="#__rgsvc_intro_overriding-the-services">introduction</a> to this guide).</p>
</div>
</div>
<div class="sect3">
@@ -1684,7 +1684,7 @@ table.CodeRay td.code>pre{padding:0}
</tr>
<tr>
<td><i class="conum" data-value="2"></i><b>2</b></td>
- <td>support metamodel invalidation/rebuilding of spec, eg as called by this <a href="rgcms.html#_rgcms_classes_mixins_Object_rebuildMetamodel">Object mixin</a> action.</td>
+ <td>support metamodel invalidation/rebuilding of spec, eg as called by this <a href="rgcms.html#__rgcms_classes_mixins_Object_rebuildMetamodel">Object mixin</a> action.</td>
</tr>
<tr>
<td><i class="conum" data-value="3"></i><b>3</b></td>
@@ -1692,7 +1692,7 @@ table.CodeRay td.code>pre{padding:0}
</tr>
<tr>
<td><i class="conum" data-value="4"></i><b>4</b></td>
- <td>returns a new instance of a <a href="rgcms.html#_rgcms_classes_layout_component"><code>Grid</code></a> for the specified domain class, eg as loaded from a <code>layout.xml</code> file. If none exists, will return null (and the calling <a href="#_rgsvc_spi_GridService"><code>GridService</code></a> will use <a href="#_rgsvc_spi_GridSystemService"><code>GridSystemService</code></a> to obtain a default grid for the domain class).</td>
+ <td>returns a new instance of a <a href="rgcms.html#__rgcms_classes_layout_component"><code>Grid</code></a> for the specified domain class, eg as loaded from a <code>layout.xml</code> file. If none exists, will return null (and the calling <a href="#_rgsvc_spi_GridService"><code>GridService</code></a> will use <a href="#_rgsvc_spi_GridSystemService"><code>GridSystemService</code></a> to obtain a default grid for the domain class).</td>
</tr>
<tr>
<td><i class="conum" data-value="5"></i><b>5</b></td>
@@ -1729,7 +1729,7 @@ table.CodeRay td.code>pre{padding:0}
<p>Assuming that the <code>configuration-and-annotation</code> services installer is configured (implicit if using the <code>AppManifest</code> to <a href="rgcms.html#_rgcms_classes_AppManifest-bootstrapping">bootstrap the app</a>), then the default implementation of <code>GridLoaderService</code> is automatically registered and injected, and no further configuration is required.</p>
</div>
<div class="paragraph">
- <p>To use an alternative implementation, use <a href="rgant.html#_rgant-DomainServiceLayout_menuOrder"><code>@DomainServiceLayout#menuOrder()</code></a> (as explained in the <a href="#_rgsvc_intro_overriding-the-services">introduction</a> to this guide). That said, there should be little reason to use a different implementation; if behaviour does need to be changed, it would also be possible to replace the implementation of either the <code>GridLoaderService</code> or the <code>GridSystemService</code>.</p>
+ <p>To use an alternative implementation, use <a href="rgant.html#_rgant-DomainServiceLayout_menuOrder"><code>@DomainServiceLayout#menuOrder()</code></a> (as explained in the <a href="#__rgsvc_intro_overriding-the-services">introduction</a> to this guide). That said, there should be little reason to use a different implementation; if behaviour does need to be changed, it would also be possible to replace the implementation of either the <code>GridLoaderService</code> or the <code>GridSystemService</code>.</p>
</div>
</div>
<div class="sect3">
@@ -1805,13 +1805,13 @@ table.CodeRay td.code>pre{padding:0}
<p>Assuming that the <code>configuration-and-annotation</code> services installer is configured (implicit if using the <code>AppManifest</code> to <a href="rgcms.html#_rgcms_classes_AppManifest-bootstrapping">bootstrap the app</a>) then Apache Isis' core implementation of <code>HintStore</code> service is automatically registered and injected (it is annotated with <code>@DomainService</code>) so no further configuration is required.</p>
</div>
<div class="paragraph">
- <p>To use an alternative implementation, use <a href="rgant.html#_rgant-DomainServiceLayout_menuOrder"><code>@DomainServiceLayout#menuOrder()</code></a> (as explained in the <a href="#_rgsvc_intro_overriding-the-services">introduction</a> to this guide).</p>
+ <p>To use an alternative implementation, use <a href="rgant.html#_rgant-DomainServiceLayout_menuOrder"><code>@DomainServiceLayout#menuOrder()</code></a> (as explained in the <a href="#__rgsvc_intro_overriding-the-services">introduction</a> to this guide).</p>
</div>
</div>
<div class="sect3">
<h4 id="_related_services_6">3.8.4. Related Services</h4>
<div class="paragraph">
- <p>The <a href="#ugvw.adoc">Wicket viewer</a> exposes the <a href="rgcms.html#_rgcms_classes_mixins_Object_clearHints">"clear hints"</a> mixin action that is for use by end-users of the application to clear any UI hints that have accumulated for a domain object.</p>
+ <p>The <a href="#ugvw.adoc">Wicket viewer</a> exposes the <a href="rgcms.html#__rgcms_classes_mixins_Object_clearHints">"clear hints"</a> mixin action that is for use by end-users of the application to clear any UI hints that have accumulated for a domain object.</p>
</div>
</div>
</div>
@@ -1878,7 +1878,7 @@ table.CodeRay td.code>pre{padding:0}
<p>Assuming that the <code>configuration-and-annotation</code> services installer is configured (implicit if using the <code>AppManifest</code> to <a href="rgcms.html#_rgcms_classes_AppManifest-bootstrapping">bootstrap the app</a>), <em>and</em> that the <a href="ugvw.html">Wicket viewer</a> is being used, then an implementation of <code>LocaleProvider</code> is automatically registered and injected (it is annotated with <code>@DomainService</code>) so no further configuration is required.</p>
</div>
<div class="paragraph">
- <p>To use an alternative implementation, use <a href="rgant.html#_rgant-DomainServiceLayout_menuOrder"><code>@DomainServiceLayout#menuOrder()</code></a> (as explained in the <a href="#_rgsvc_intro_overriding-the-services">introduction</a> to this guide).</p>
+ <p>To use an alternative implementation, use <a href="rgant.html#_rgant-DomainServiceLayout_menuOrder"><code>@DomainServiceLayout#menuOrder()</code></a> (as explained in the <a href="#__rgsvc_intro_overriding-the-services">introduction</a> to this guide).</p>
</div>
</div>
<div class="sect3">
@@ -1960,7 +1960,7 @@ table.CodeRay td.code>pre{padding:0}
<p>The framework provides a default implementation - <code>RoutingServiceDefault</code> - which will always return the original object provided, or the home page if a <code>null</code> or <code>void</code> was provided. It uses the <a href="#_rgsvc_api_HomePageProviderService"><code>HomePageProviderService</code></a>.</p>
</div>
<div class="paragraph">
- <p>There can be multiple implementations of <code>RoutingService</code> registered. These are checked in turn (chain of responsibility pattern), ordered according to <a href="rgant.html#_rgant-DomainServiceLayout_menuOrder"><code>@DomainServiceLayout#menuOrder()</code></a> (as explained in the <a href="#_rgsvc_intro_overriding-the-services">introduction</a> to this guide). The route from the first service that returns <code>true</code> from its <code>canRoute(\u2026\u200b)</code> method will be used.</p>
+ <p>There can be multiple implementations of <code>RoutingService</code> registered. These are checked in turn (chain of responsibility pattern), ordered according to <a href="rgant.html#_rgant-DomainServiceLayout_menuOrder"><code>@DomainServiceLayout#menuOrder()</code></a> (as explained in the <a href="#__rgsvc_intro_overriding-the-services">introduction</a> to this guide). The route from the first service that returns <code>true</code> from its <code>canRoute(\u2026\u200b)</code> method will be used.</p>
</div>
</div>
<div class="sect3">
@@ -2116,11 +2116,11 @@ table.CodeRay td.code>pre{padding:0}
<p>If the menu items are not required then these can be suppressed either using security or by implementing a <a href="ugbtb.html#_ugbtb_decoupling_vetoing-visibility">vetoing subscriber</a>.</p>
</div>
<div class="paragraph">
- <p>To use an alternative implementation, use <a href="rgant.html#_rgant-DomainServiceLayout_menuOrder"><code>@DomainServiceLayout#menuOrder()</code></a> (as explained in the <a href="#_rgsvc_intro_overriding-the-services">introduction</a> to this guide).</p>
+ <p>To use an alternative implementation, use <a href="rgant.html#_rgant-DomainServiceLayout_menuOrder"><code>@DomainServiceLayout#menuOrder()</code></a> (as explained in the <a href="#__rgsvc_intro_overriding-the-services">introduction</a> to this guide).</p>
</div>
</div>
<div class="sect3">
- <h4 id="_rgsvc_api_LayoutService_related-mixins-and-menus">3.12.4. Related Menus</h4>
+ <h4 id="__rgsvc_api_LayoutService_related-mixins-and-menus">3.12.4. Related Menus</h4>
<div class="paragraph">
<p>The <code>TranslationServicePoMenu</code> menu exposes the <code>TranslationServicePo</code> service\u2019s <code>toPot()</code> method so that all translations can be downloaded as a single file.</p>
</div>
@@ -2192,7 +2192,7 @@ table.CodeRay td.code>pre{padding:0}
<p>Assuming that the <code>configuration-and-annotation</code> services installer is configured (implicit if using the <code>AppManifest</code> to <a href="rgcms.html#<em>rgcms_classes_AppManifest-bootstrapping">bootstrap the app</a>), _and that the <a href="ugvw.html">Wicket viewer</a> is being used, then an implementation of <code>TranslationsResolver</code> is automatically registered and injected (it is annotated with <code>@DomainService</code>) so no further configuration is required.</p>
</div>
<div class="paragraph">
- <p>To use an alternative implementation, use <a href="rgant.html#_rgant-DomainServiceLayout_menuOrder"><code>@DomainServiceLayout#menuOrder()</code></a> (as explained in the <a href="#_rgsvc_intro_overriding-the-services">introduction</a> to this guide).</p>
+ <p>To use an alternative implementation, use <a href="rgant.html#_rgant-DomainServiceLayout_menuOrder"><code>@DomainServiceLayout#menuOrder()</code></a> (as explained in the <a href="#__rgsvc_intro_overriding-the-services">introduction</a> to this guide).</p>
</div>
</div>
<div class="sect3">
@@ -2258,7 +2258,7 @@ table.CodeRay td.code>pre{padding:0}
<p>The framework provides a default implementation (<code>UrlEncodingServiceUsingBaseEncoding</code>) that simply converts the string using base-64 encoding and UTF-8 character set. As already noted, be aware that the maximum length of a URL should not exceed 2083 characters. For large view models, there\u2019s the possibility that this limit could be exceeded; in such cases register an alternative implementation of this service.</p>
</div>
<div class="paragraph">
- <p>To use an alternative implementation, use <a href="rgant.html#_rgant-DomainServiceLayout_menuOrder"><code>@DomainServiceLayout#menuOrder()</code></a> (as explained in the <a href="#_rgsvc_intro_overriding-the-services">introduction</a> to this guide).</p>
+ <p>To use an alternative implementation, use <a href="rgant.html#_rgant-DomainServiceLayout_menuOrder"><code>@DomainServiceLayout#menuOrder()</code></a> (as explained in the <a href="#__rgsvc_intro_overriding-the-services">introduction</a> to this guide).</p>
</div>
</div>
</div>
@@ -2585,7 +2585,7 @@ table.CodeRay td.code>pre{padding:0}
<p>Assuming that the <code>configuration-and-annotation</code> services installer is configured (implicit if using the <code>AppManifest</code> to <a href="rgcms.html#_rgcms_classes_AppManifest-bootstrapping">bootstrap the app</a>) then Apache Isis' default implementation of <code>AcceptHeaderService</code> class is automatically registered (it is annotated with <code>@DomainService</code>) so no further configuration is required.</p>
</div>
<div class="paragraph">
- <p>To use an alternative implementation, use <a href="rgant.html#_rgant-DomainServiceLayout_menuOrder"><code>@DomainServiceLayout#menuOrder()</code></a> (as explained in the <a href="#_rgsvc_intro_overriding-the-services">introduction</a> to this guide).</p>
+ <p>To use an alternative implementation, use <a href="rgant.html#_rgant-DomainServiceLayout_menuOrder"><code>@DomainServiceLayout#menuOrder()</code></a> (as explained in the <a href="#__rgsvc_intro_overriding-the-services">introduction</a> to this guide).</p>
</div>
</div>
</div>
@@ -2687,7 +2687,7 @@ table.CodeRay td.code>pre{padding:0}
<p>Assuming that the <code>configuration-and-annotation</code> services installer is configured (implicit if using the <code>AppManifest</code> to <a href="rgcms.html#_rgcms_classes_AppManifest-bootstrapping">bootstrap the app</a>) then Apache Isis' default implementation of <code>ActionInvocationContext</code> class is automatically registered (it is annotated with <code>@DomainService</code>) so no further configuration is required.</p>
</div>
<div class="paragraph">
- <p>To use an alternative implementation, use <a href="rgant.html#_rgant-DomainServiceLayout_menuOrder"><code>@DomainServiceLayout#menuOrder()</code></a> (as explained in the <a href="#_rgsvc_intro_overriding-the-services">introduction</a> to this guide).</p>
+ <p>To use an alternative implementation, use <a href="rgant.html#_rgant-DomainServiceLayout_menuOrder"><code>@DomainServiceLayout#menuOrder()</code></a> (as explained in the <a href="#__rgsvc_intro_overriding-the-services">introduction</a> to this guide).</p>
</div>
</div>
<div class="sect3">
@@ -2853,7 +2853,7 @@ CommandContext commandContext; <i class="conum" data-value="1"></i><b>(1)</b></
<p>Assuming that the <code>configuration-and-annotation</code> services installer is configured (implicit if using the <code>AppManifest</code> to <a href="rgcms.html#_rgcms_classes_AppManifest-bootstrapping">bootstrap the app</a>) then Apache Isis' core implementation of <code>BackgroundService</code> is automatically registered (it is annotated with <code>@DomainService</code>) so no further configuration is required.</p>
</div>
<div class="paragraph">
- <p>To use an alternative implementation, use <a href="rgant.html#_rgant-DomainServiceLayout_menuOrder"><code>@DomainServiceLayout#menuOrder()</code></a> (as explained in the <a href="#_rgsvc_intro_overriding-the-services">introduction</a> to this guide).</p>
+ <p>To use an alternative implementation, use <a href="rgant.html#_rgant-DomainServiceLayout_menuOrder"><code>@DomainServiceLayout#menuOrder()</code></a> (as explained in the <a href="#__rgsvc_intro_overriding-the-services">introduction</a> to this guide).</p>
</div>
</div>
<div class="sect3">
@@ -3077,7 +3077,7 @@ org.quartz.plugin.jobInitializer.failOnFileNotFound = true</code></pre>
<p>As of <code>1.13.0</code>, these other uses cases are now more fully supported through the <a href="#_rgsvc_api_InteractionContext"><code>InteractionContext</code></a> service and persistent implementations of the <code>Interaction</code> object, eg as provided by the (non-ASF) <a href="http://github.com/isisaddons/isis-module-publishmq">Isis addons' publishmq</a> module.</p>
</div>
<div class="sect3">
- <h4 id="_rgsvc_api_CommandContext_screencast">4.4.1. Screencast</h4>
+ <h4 id="__rgsvc_api_CommandContext_screencast">4.4.1. Screencast</h4>
<div class="paragraph">
<p>The <a href="https://www.youtube.com/watch?v=tqXUZkPB3EI">screencast</a> provides a run-through of the command (profiling) service, auditing service, publishing service. It also shows how commands can be run in the background either explicitly by scheduling through the background service or implicitly by way of a framework annotation.</p>
</div>
@@ -3335,7 +3335,7 @@ org.quartz.plugin.jobInitializer.failOnFileNotFound = true</code></pre>
<p>Assuming that the <code>configuration-and-annotation</code> services installer is configured (implicit if using the <code>AppManifest</code> to <a href="rgcms.html#_rgcms_classes_AppManifest-bootstrapping">bootstrap the app</a>) then Apache Isis' core implementation of <code>CommandContext</code> service is automatically registered and injected (it is annotated with <code>@DomainService</code>) so no further configuration is required.</p>
</div>
<div class="paragraph">
- <p>To use an alternative implementation, use <a href="rgant.html#_rgant-DomainServiceLayout_menuOrder"><code>@DomainServiceLayout#menuOrder()</code></a> (as explained in the <a href="#_rgsvc_intro_overriding-the-services">introduction</a> to this guide).</p>
+ <p>To use an alternative implementation, use <a href="rgant.html#_rgant-DomainServiceLayout_menuOrder"><code>@DomainServiceLayout#menuOrder()</code></a> (as explained in the <a href="#__rgsvc_intro_overriding-the-services">introduction</a> to this guide).</p>
</div>
</div>
<div class="sect3">
@@ -3605,7 +3605,7 @@ org.quartz.plugin.jobInitializer.failOnFileNotFound = true</code></pre>
<td class="icon"> <i class="fa icon-note" title="Note"></i> </td>
<td class="content">
<div class="paragraph">
- <p>Unlike the similar <a href="#_rgsvc_api_CommandContext"><code>CommandContext</code></a> (discussed <a href="#_rgsvc_api_InteractionContext_Related-Classes">below</a>) there is no domain service to different implementations of <code>Interaction</code> to be used. If this were to be needed, then a custom implementation of <a href="#_rgsvc_api_FactoryService"><code>FactoryService</code></a> could always used).</p>
+ <p>Unlike the similar <a href="#_rgsvc_api_CommandContext"><code>CommandContext</code></a> (discussed <a href="#__rgsvc_api_InteractionContext_Related-Classes">below</a>) there is no domain service to different implementations of <code>Interaction</code> to be used. If this were to be needed, then a custom implementation of <a href="#_rgsvc_api_FactoryService"><code>FactoryService</code></a> could always used).</p>
</div> </td>
</tr>
</tbody>
@@ -3613,7 +3613,7 @@ org.quartz.plugin.jobInitializer.failOnFileNotFound = true</code></pre>
</div>
</div>
<div class="sect3">
- <h4 id="_rgsvc_api_InteractionContext_Related-Classes">4.5.4. Related Classes</h4>
+ <h4 id="__rgsvc_api_InteractionContext_Related-Classes">4.5.4. Related Classes</h4>
<div class="paragraph">
<p>This service is very similar in nature to <a href="#_rgsvc_api_CommandContext"><code>CommandContext</code></a>, in that the <code>Interaction</code> object accessed through it is very similar to the <code>Command</code> object obtained from the <code>CommandContext</code>. The principle distinction is that while <code>Command</code> represents the <em>intention</em> to invoke an action or edit a property, the <code>Interaction</code> (and contained <code>Execution</code>s) represents the actual execution.</p>
</div>
@@ -3718,7 +3718,7 @@ org.quartz.plugin.jobInitializer.failOnFileNotFound = true</code></pre>
<p>Assuming that the <code>configuration-and-annotation</code> services installer is configured (implicit if using the <code>AppManifest</code> to <a href="rgcms.html#_rgcms_classes_AppManifest-bootstrapping">bootstrap the app</a>) then Apache Isis' core implementation of <code>MessageService</code> service is automatically registered and injected (it is annotated with <code>@DomainService</code>) so no further configuration is required.</p>
</div>
<div class="paragraph">
- <p>To use an alternative implementation, use <a href="rgant.html#_rgant-DomainServiceLayout_menuOrder"><code>@DomainServiceLayout#menuOrder()</code></a> (as explained in the <a href="#_rgsvc_intro_overriding-the-services">introduction</a> to this guide).</p>
+ <p>To use an alternative implementation, use <a href="rgant.html#_rgant-DomainServiceLayout_menuOrder"><code>@DomainServiceLayout#menuOrder()</code></a> (as explained in the <a href="#__rgsvc_intro_overriding-the-services">introduction</a> to this guide).</p>
</div>
</div>
</div>
@@ -3771,7 +3771,7 @@ org.quartz.plugin.jobInitializer.failOnFileNotFound = true</code></pre>
<p>Assuming that the <code>configuration-and-annotation</code> services installer is configured (implicit if using the <code>AppManifest</code> to <a href="rgcms.html#_rgcms_classes_AppManifest-bootstrapping">bootstrap the app</a>) then Apache Isis' core implementation of <code>SessionManagementService</code> service is automatically registered and injected (it is annotated with <code>@DomainService</code>) so no further configuration is required.</p>
</div>
<div class="paragraph">
- <p>To use an alternative implementation, use <a href="rgant.html#_rgant-DomainServiceLayout_menuOrder"><code>@DomainServiceLayout#menuOrder()</code></a> (as explained in the <a href="#_rgsvc_intro_overriding-the-services">introduction</a> to this guide).</p>
+ <p>To use an alternative implementation, use <a href="rgant.html#_rgant-DomainServiceLayout_menuOrder"><code>@DomainServiceLayout#menuOrder()</code></a> (as explained in the <a href="#__rgsvc_intro_overriding-the-services">introduction</a> to this guide).</p>
</div>
</div>
</div>
@@ -3858,7 +3858,7 @@ org.quartz.plugin.jobInitializer.failOnFileNotFound = true</code></pre>
<p>Assuming that the <code>configuration-and-annotation</code> services installer is configured (implicit if using the <code>AppManifest</code> to <a href="rgcms.html#_rgcms_classes_AppManifest-bootstrapping">bootstrap the app</a>) then Apache Isis' core implementation of <code>TitleService</code> service is automatically registered and injected (it is annotated with <code>@DomainService</code>) so no further configuration is required.</p>
</div>
<div class="paragraph">
- <p>To use an alternative implementation, use <a href="rgant.html#_rgant-DomainServiceLayout_menuOrder"><code>@DomainServiceLayout#menuOrder()</code></a> (as explained in the <a href="#_rgsvc_intro_overriding-the-services">introduction</a> to this guide).</p>
+ <p>To use an alternative implementation, use <a href="rgant.html#_rgant-DomainServiceLayout_menuOrder"><code>@DomainServiceLayout#menuOrder()</code></a> (as explained in the <a href="#__rgsvc_intro_overriding-the-services">introduction</a> to this guide).</p>
</div>
</div>
</div>
@@ -3991,7 +3991,7 @@ org.quartz.plugin.jobInitializer.failOnFileNotFound = true</code></pre>
<p>Assuming that the <code>configuration-and-annotation</code> services installer is configured (implicit if using the <code>AppManifest</code> to <a href="rgcms.html#_rgcms_classes_AppManifest-bootstrapping">bootstrap the app</a>) then Apache Isis' core implementation of <code>TransactionService</code> service is automatically registered and injected (it is annotated with <code>@DomainService</code>) so no further configuration is required.</p>
</div>
<div class="paragraph">
- <p>To use an alternative implementation, use <a href="rgant.html#_rgant-DomainServiceLayout_menuOrder"><code>@DomainServiceLayout#menuOrder()</code></a> (as explained in the <a href="#_rgsvc_intro_overriding-the-services">introduction</a> to this guide).</p>
+ <p>To use an alternative implementation, use <a href="rgant.html#_rgant-DomainServiceLayout_menuOrder"><code>@DomainServiceLayout#menuOrder()</code></a> (as explained in the <a href="#__rgsvc_intro_overriding-the-services">introduction</a> to this guide).</p>
</div>
</div>
</div>
@@ -4233,7 +4233,7 @@ org.quartz.plugin.jobInitializer.failOnFileNotFound = true</code></pre>
<p>Assuming that the <code>configuration-and-annotation</code> services installer is configured (implicit if using the <code>AppManifest</code> to <a href="rgcms.html#_rgcms_classes_AppManifest-bootstrapping">bootstrap the app</a>) then Apache Isis' core implementation of <code>WrapperFactory</code> service is automatically registered and injected (it is annotated with <code>@DomainService</code>) so no further configuration is required.</p>
</div>
<div class="paragraph">
- <p>To use an alternative implementation, use <a href="rgant.html#_rgant-DomainServiceLayout_menuOrder"><code>@DomainServiceLayout#menuOrder()</code></a> (as explained in the <a href="#_rgsvc_intro_overriding-the-services">introduction</a> to this guide).</p>
+ <p>To use an alternative implementation, use <a href="rgant.html#_rgant-DomainServiceLayout_menuOrder"><code>@DomainServiceLayout#menuOrder()</code></a> (as explained in the <a href="#__rgsvc_intro_overriding-the-services">introduction</a> to this guide).</p>
</div>
</div>
</div>
@@ -5053,7 +5053,7 @@ org.quartz.plugin.jobInitializer.failOnFileNotFound = true</code></pre>
<p>Assuming that the <code>configuration-and-annotation</code> services installer is configured (implicit if using the <code>AppManifest</code> to <a href="rgcms.html#_rgcms_classes_AppManifest-bootstrapping">bootstrap the app</a>) then Apache Isis' core implementation of <code>ConfigurationService</code> service is automatically registered and injected (it is annotated with <code>@DomainService</code>) so no further configuration is required.</p>
</div>
<div class="paragraph">
- <p>To use an alternative implementation, use <a href="rgant.html#_rgant-DomainServiceLayout_menuOrder"><code>@DomainServiceLayout#menuOrder()</code></a> (as explained in the <a href="#_rgsvc_intro_overriding-the-services">introduction</a> to this guide).</p>
+ <p>To use an alternative implementation, use <a href="rgant.html#_rgant-DomainServiceLayout_menuOrder"><code>@DomainServiceLayout#menuOrder()</code></a> (as explained in the <a href="#__rgsvc_intro_overriding-the-services">introduction</a> to this guide).</p>
</div>
</div>
<div class="sect3">
@@ -5744,7 +5744,7 @@ container.persist(cust);</code></pre>
<p>Two implementations are available, using either <a href="https://code.google.com/p/guava-libraries/">Guava</a>'s <a href="https://code.google.com/p/guava-libraries/wiki/EventBusExplained"><code>EventBus</code></a>, or alternatively using the <a href="http://www.axonframework.org/">AxonFramework</a>'s <a href="http://www.axonframework.org/docs/2.4/single.html#d5e1489">SimpleEventBus</a>. It is also possible to plug in a custom implementation.</p>
</div>
<div class="sect3">
- <h4 id="_rgsvc_api_EventBusService_api-and-implementation">6.4.1. API & Implementation</h4>
+ <h4 id="__rgsvc_api_EventBusService_api-and-implementation">6.4.1. API & Implementation</h4>
<div class="paragraph">
<p>The API defined by <code>EventBusService</code> is:</p>
</div>
@@ -5785,7 +5785,7 @@ container.persist(cust);</code></pre>
<div class="sect3">
<h4 id="_registering_subscribers">6.4.2. Registering Subscribers</h4>
<div class="paragraph">
- <p>The <code>register()</code> method should be called in the <a href="rgant.html#_rgant-PostConstruct"><code>@PostConstruct</code></a> lifecycle method. It is valid and probably the least confusing to readers to also "unregister" in the <a href="rgant.html#_rgant-PreDestroy"><code>@PreDestroy</code></a> lifecycle method (though as noted <a href="#_rgsvc_api_EventBusService_api-and-implementation">above</a>, unregistering is actually a no-op).</p>
+ <p>The <code>register()</code> method should be called in the <a href="rgant.html#_rgant-PostConstruct"><code>@PostConstruct</code></a> lifecycle method. It is valid and probably the least confusing to readers to also "unregister" in the <a href="rgant.html#_rgant-PreDestroy"><code>@PreDestroy</code></a> lifecycle method (though as noted <a href="#__rgsvc_api_EventBusService_api-and-implementation">above</a>, unregistering is actually a no-op).</p>
</div>
<div class="paragraph">
<p>For example:</p>
@@ -5913,7 +5913,7 @@ container.persist(cust);</code></pre>
<tbody>
<tr>
<td><i class="conum" data-value="1"></i><b>1</b></td>
- <td><code>LibraryMemberLeaveEvent</code> is a subclass of <code>o.a.i.applib.eventbus.ActionDomainEvent</code>. The topic of subclassing is discussed in more detail <a href="#_rgsvc_api_EventBusService_event-hierarchy">below</a>.</td>
+ <td><code>LibraryMemberLeaveEvent</code> is a subclass of <code>o.a.i.applib.eventbus.ActionDomainEvent</code>. The topic of subclassing is discussed in more detail <a href="#__rgsvc_api_EventBusService_event-hierarchy">below</a>.</td>
</tr>
</tbody>
</table>
@@ -5942,7 +5942,7 @@ container.persist(cust);</code></pre>
</div>
</div>
<div class="sect3">
- <h4 id="_rgsvc_api_EventBusService_event-hierarchy">6.4.4. Event hierarchy</h4>
+ <h4 id="__rgsvc_api_EventBusService_event-hierarchy">6.4.4. Event hierarchy</h4>
<div class="paragraph">
<p>By creating domain event subtypes we can be more semantically precise and in turn providesmore flexibility for subscribers: they can choose whether to be broadly applicable (by subscribing to a superclass) or to be tightly focussed (by subscribing to a subclass).</p>
</div>
@@ -6125,7 +6125,7 @@ public <span class="directive">static</span> <span class="type">class</span> <sp
<div class="sect3">
<h4 id="_implementation_spi">6.4.7. Implementation SPI</h4>
<div class="paragraph">
- <p>The implementation of <code>EventBusService</code> provided by Apache Isis will by default use <a href="https://code.google.com/p/guava-libraries/">Guava</a>'s <a href="https://code.google.com/p/guava-libraries/wiki/EventBusExplained"><code>EventBus</code></a> as the underlying in-memory event bus. Alternatively the <a href="http://www.axonframework.org/">AxonFramework</a>'s <a href="http://www.axonframework.org/docs/2.4/single.html#d5e1489">SimpleEventBus</a> can be used. Which is used is specified through configuration property (described <a href="#_rgsvc_api_EventBusService_Configuration">below</a>).</p>
+ <p>The implementation of <code>EventBusService</code> provided by Apache Isis will by default use <a href="https://code.google.com/p/guava-libraries/">Guava</a>'s <a href="https://code.google.com/p/guava-libraries/wiki/EventBusExplained"><code>EventBus</code></a> as the underlying in-memory event bus. Alternatively the <a href="http://www.axonframework.org/">AxonFramework</a>'s <a href="http://www.axonframework.org/docs/2.4/single.html#d5e1489">SimpleEventBus</a> can be used. Which is used is specified through configuration property (described <a href="#__rgsvc_api_EventBusService_Configuration">below</a>).</p>
</div>
<div class="admonitionblock note">
<table>
@@ -6166,7 +6166,7 @@ public <span class="directive">static</span> <span class="type">class</span> <sp
</div>
</div>
<div class="sect3">
- <h4 id="_rgsvc_api_EventBusService_Configuration">6.4.8. Configuration</h4>
+ <h4 id="__rgsvc_api_EventBusService_Configuration">6.4.8. Configuration</h4>
<div class="paragraph">
<p>The implementation of <code>EventBusService</code> provided by Apache Isis will by default use <a href="https://code.google.com/p/guava-libraries/">Guava</a>'s <a href="https://code.google.com/p/guava-libraries/wiki/EventBusExplained"><code>EventBus</code></a> as the underlying in-memory event bus. Alternatively the <a href="http://www.axonframework.org/">AxonFramework</a>'s <a href="http://www.axonframework.org/docs/2.4/single.html#d5e1489">SimpleEventBus</a> can be used.</p>
</div>
@@ -6212,7 +6212,7 @@ public <span class="directive">static</span> <span class="type">class</span> <sp
<p>Assuming that the <code>configuration-and-annotation</code> services installer is configured (implicit if using the <code>AppManifest</code> to <a href="rgcms.html#_rgcms_classes_AppManifest-bootstrapping">bootstrap the app</a>) then Apache Isis' core implementation of <code>EventBusService</code> service is automatically registered and injected (it is annotated with <code>@DomainService</code>) so no further configuration is required.</p>
</div>
<div class="paragraph">
- <p>To use an alternative implementation, use <a href="rgant.html#_rgant-DomainServiceLayout_menuOrder"><code>@DomainServiceLayout#menuOrder()</code></a> (as explained in the <a href="#_rgsvc_intro_overriding-the-services">introduction</a> to this guide).</p>
+ <p>To use an alternative implementation, use <a href="rgant.html#_rgant-DomainServiceLayout_menuOrder"><code>@DomainServiceLayout#menuOrder()</code></a> (as explained in the <a href="#__rgsvc_intro_overriding-the-services">introduction</a> to this guide).</p>
</div>
</div>
<div class="sect3">
@@ -6309,7 +6309,7 @@ repositoryService.persist(cust);</code></pre>
<p>Assuming that the <code>configuration-and-annotation</code> services installer is configured (implicit if using the <code>AppManifest</code> to <a href="rgcms.html#_rgcms_classes_AppManifest-bootstrapping">bootstrap the app</a>) then Apache Isis' core implementation of <code>FactoryService</code> service is automatically registered and injected (it is annotated with <code>@DomainService</code>) so no further configuration is required.</p>
</div>
<div class="paragraph">
- <p>To use an alternative implementation, use <a href="rgant.html#_rgant-DomainServiceLayout_menuOrder"><code>@DomainServiceLayout#menuOrder()</code></a> (as explained in the <a href="#_rgsvc_intro_overriding-the-services">introduction</a> to this guide).</p>
+ <p>To use an alternative implementation, use <a href="rgant.html#_rgant-DomainServiceLayout_menuOrder"><code>@DomainServiceLayout#menuOrder()</code></a> (as explained in the <a href="#__rgsvc_intro_overriding-the-services">introduction</a> to this guide).</p>
</div>
</div>
<div class="sect3">
@@ -6449,7 +6449,7 @@ Scratchpad scratchpad;</code></pre>
<p>Assuming that the <code>configuration-and-annotation</code> services installer is configured (implicit if using the <code>AppManifest</code> to <a href="rgcms.html#_rgcms_classes_AppManifest-bootstrapping">bootstrap the app</a>) then Apache Isis' core implementation of <code>Scratchpad</code> service is automatically registered and injected (it is annotated with <code>@DomainService</code>) so no further configuration is required.</p>
</div>
<div class="paragraph">
- <p>To use an alternative implementation, use <a href="rgant.html#_rgant-DomainServiceLayout_menuOrder"><code>@DomainServiceLayout#menuOrder()</code></a> (as explained in the <a href="#_rgsvc_intro_overriding-the-services">introduction</a> to this guide).</p>
+ <p>To use an alternative implementation, use <a href="rgant.html#_rgant-DomainServiceLayout_menuOrder"><code>@DomainServiceLayout#menuOrder()</code></a> (as explained in the <a href="#__rgsvc_intro_overriding-the-services">introduction</a> to this guide).</p>
</div>
</div>
<div class="sect3">
@@ -6542,7 +6542,7 @@ Scratchpad scratchpad;</code></pre>
<p>Assuming that the <code>configuration-and-annotation</code> services installer is configured (implicit if using the <code>AppManifest</code> to <a href="rgcms.html#_rgcms_classes_AppManifest-bootstrapping">bootstrap the app</a>) then Apache Isis' core implementation of <code>UserService</code> service is automatically registered and injected (it is annotated with <code>@DomainService</code>) so no further configuration is required.</p>
</div>
<div class="paragraph">
- <p>To use an alternative implementation, use <a href="rgant.html#_rgant-DomainServiceLayout_menuOrder"><code>@DomainServiceLayout#menuOrder()</code></a> (as explained in the <a href="#_rgsvc_intro_overriding-the-services">introduction</a> to this guide).</p>
+ <p>To use an alternative implementation, use <a href="rgant.html#_rgant-DomainServiceLayout_menuOrder"><code>@DomainServiceLayout#menuOrder()</code></a> (as explained in the <a href="#__rgsvc_intro_overriding-the-services">introduction</a> to this guide).</p>
</div>
</div>
</div>
@@ -6809,7 +6809,7 @@ Scratchpad scratchpad;</code></pre>
<p>Assuming that the <code>configuration-and-annotation</code> services installer is configured (implicit if using the <code>AppManifest</code> to <a href="rgcms.html#_rgcms_classes_AppManifest-bootstrapping">bootstrap the app</a>) then Apache Isis' core implementation of <code>BookmarkService</code> is automatically registered (it is annotated with <code>@DomainService</code>) so no further configuration is required.</p>
</div>
<div class="paragraph">
- <p>To use an alternative implementation, use <a href="rgant.html#_rgant-DomainServiceLayout_menuOrder"><code>@DomainServiceLayout#menuOrder()</code></a> (as explained in the <a href="#_rgsvc_intro_overriding-the-services">introduction</a> to this guide).</p>
+ <p>To use an alternative implementation, use <a href="rgant.html#_rgant-DomainServiceLayout_menuOrder"><code>@DomainServiceLayout#menuOrder()</code></a> (as explained in the <a href="#__rgsvc_intro_overriding-the-services">introduction</a> to this guide).</p>
</div>
</div>
</div>
@@ -6870,7 +6870,7 @@ Scratchpad scratchpad;</code></pre>
<p>Assuming that the <code>configuration-and-annotation</code> services installer is configured (implicit if using the <code>AppManifest</code> to <a href="rgcms.html#<em>rgcms_classes_AppManifest-bootstrapping">bootstrap the app</a>), _and that the <a href="ugvw.html">Wicket viewer</a> is being used, then an implementation of <code>DeepLinkService</code> is automatically registered and injected (it is annotated with <code>@DomainService</code>) so no further configuration is required.</p>
</div>
<div class="paragraph">
- <p>To use an alternative implementation, use <a href="rgant.html#_rgant-DomainServiceLayout_menuOrder"><code>@DomainServiceLayout#menuOrder()</code></a> (as explained in the <a href="#_rgsvc_intro_overriding-the-services">introduction</a> to this guide).</p>
+ <p>To use an alternative implementation, use <a href="rgant.html#_rgant-DomainServiceLayout_menuOrder"><code>@DomainServiceLayout#menuOrder()</code></a> (as explained in the <a href="#__rgsvc_intro_overriding-the-services">introduction</a> to this guide).</p>
</div>
</div>
</div>
@@ -7016,7 +7016,7 @@ Scratchpad scratchpad;</code></pre>
<p>Assuming that the <code>configuration-and-annotation</code> services installer is configured (implicit if using the <code>AppManifest</code> to <a href="rgcms.html#_rgcms_classes_AppManifest-bootstrapping">bootstrap the app</a>) then Apache Isis' core implementation of <code>EmailService</code> service is automatically registered and injected (it is annotated with <code>@DomainService</code>) so no further configuration is required.</p>
</div>
<div class="paragraph">
- <p>To use an alternative implementation, use <a href="rgant.html#_rgant-DomainServiceLayout_menuOrder"><code>@DomainServiceLayout#menuOrder()</code></a> (as explained in the <a href="#_rgsvc_intro_overriding-the-services">introduction</a> to this guide).</p>
+ <p>To use an alternative implementation, use <a href="rgant.html#_rgant-DomainServiceLayout_menuOrder"><code>@DomainServiceLayout#menuOrder()</code></a> (as explained in the <a href="#__rgsvc_intro_overriding-the-services">introduction</a> to this guide).</p>
</div>
</div>
<div class="sect3">
@@ -7119,7 +7119,7 @@ Scratchpad scratchpad;</code></pre>
<p>Assuming that the <code>configuration-and-annotation</code> services installer is configured (implicit if using the <code>AppManifest</code> to <a href="rgcms.html#<em>rgcms_classes_AppManifest-bootstrapping">bootstrap the app</a>), _and that the <a href="ugvw.html">Wicket viewer</a> is being used, then an implementation of <code>GuiceBeanProvider</code> is automatically registered and injected (it is annotated with <code>@DomainService</code>) so no further configuration is required.</p>
</div>
<div class="paragraph">
- <p>To use an alternative implementation, use <a href="rgant.html#_rgant-DomainServiceLayout_menuOrder"><code>@DomainServiceLayout#menuOrder()</code></a> (as explained in the <a href="#_rgsvc_intro_overriding-the-services">introduction</a> to this guide).</p>
+ <p>To use an alternative implementation, use <a href="rgant.html#_rgant-DomainServiceLayout_menuOrder"><code>@DomainServiceLayout#menuOrder()</code></a> (as explained in the <a href="#__rgsvc_intro_overriding-the-services">introduction</a> to this guide).</p>
</div>
</div>
</div>
@@ -7129,7 +7129,7 @@ Scratchpad scratchpad;</code></pre>
<p>The <code>JaxbService</code> allows instances of JAXB-annotated classes to be marshalled to XML and unmarshalled from XML back into domain objects.</p>
</div>
<div class="sect3">
- <h4 id="_rgsvc_api_JaxbService_api-and-implementation">7.5.1. API & Implementation</h4>
+ <h4 id="__rgsvc_api_JaxbService_api-and-implementation">7.5.1. API & Implementation</h4>
<div class="paragraph">
<p>The API defined by <code>JaxbService</code> is:</p>
</div>
@@ -7189,7 +7189,7 @@ Scratchpad scratchpad;</code></pre>
<p>Assuming that the <code>configuration-and-annotation</code> services installer is configured (implicit if using the <code>AppManifest</code> to <a href="rgcms.html#_rgcms_classes_AppManifest-bootstrapping">bootstrap the app</a>) then Apache Isis' core implementation of <code>JaxbService</code> service is automatically registered and injected (it is annotated with <code>@DomainService</code>) so no further configuration is required.</p>
</div>
<div class="paragraph">
- <p>To use an alternative implementation, use <a href="rgant.html#_rgant-DomainServiceLayout_menuOrder"><code>@DomainServiceLayout#menuOrder()</code></a> (as explained in the <a href="#_rgsvc_intro_overriding-the-services">introduction</a> to this guide).</p>
+ <p>To use an alternative implementation, use <a href="rgant.html#_rgant-DomainServiceLayout_menuOrder"><code>@DomainServiceLayout#menuOrder()</code></a> (as explained in the <a href="#__rgsvc_intro_overriding-the-services">introduction</a> to this guide).</p>
</div>
</div>
</div>
@@ -7354,7 +7354,7 @@ Scratchpad scratchpad;</code></pre>
<p>Assuming that the <code>configuration-and-annotation</code> services installer is configured (implicit if using the <code>AppManifest</code> to <a href="rgcms.html#_rgcms_classes_AppManifest-bootstrapping">bootstrap the app</a>) then Apache Isis' core implementation of <code>MementoService</code> service is automatically registered and injected (it is annotated with <code>@DomainService</code>) so no further configuration is required.</p>
</div>
<div class="paragraph">
- <p>To use an alternative implementation, use <a href="rgant.html#_rgant-DomainServiceLayout_menuOrder"><code>@DomainServiceLayout#menuOrder()</code></a> (as explained in the <a href="#_rgsvc_intro_overriding-the-services">introduction</a> to this guide).</p>
+ <p>To use an alternative implementation, use <a href="rgant.html#_rgant-DomainServiceLayout_menuOrder"><code>@DomainServiceLayout#menuOrder()</code></a> (as explained in the <a href="#__rgsvc_intro_overriding-the-services">introduction</a> to this guide).</p>
</div>
</div>
</div>
@@ -7585,7 +7585,7 @@ Element customerXsd = snapshot.getXsdElement();</code></pre>
<p>Assuming that the <code>configuration-and-annotation</code> services installer is configured (implicit if using the <code>AppManifest</code> to <a href="rgcms.html#_rgcms_classes_AppManifest-bootstrapping">bootstrap the app</a>) then Apache Isis' core implementation of <code>XmlSnapshotService</code> service is automatically registered and injected (it is annotated with <code>@DomainService</code>) so no further configuration is required.</p>
</div>
<div class="paragraph">
- <p>To use an alternative implementation, use <a href="rgant.html#_rgant-DomainServiceLayout_menuOrder"><code>@DomainServiceLayout#menuOrder()</code></a> (as explained in the <a href="#_rgsvc_intro_overriding-the-services">introduction</a> to this guide).</p>
+ <p>To use an alternative implementation, use <a href="rgant.html#_rgant-DomainServiceLayout_menuOrder"><code>@DomainServiceLayout#menuOrder()</code></a> (as explained in the <a href="#__rgsvc_intro_overriding-the-services">introduction</a> to this guide).</p>
</div>
</div>
<div class="sect3">
@@ -7756,7 +7756,7 @@ Element customerXsd = snapshot.getXsdElement();</code></pre>
<p>Assuming that the <code>configuration-and-annotation</code> services installer is configured (implicit if using the <code>AppManifest</code> to <a href="rgcms.html#_rgcms_classes_AppManifest-bootstrapping">bootstrap the app</a>) then Apache Isis' core implementation of <code>ApplicationFeatureRepository</code> service is automatically registered and injected (it is annotated with <code>@DomainService</code>) so no further configuration is required.</p>
</div>
<div class="paragraph">
- <p>To use an alternative implementation, use <a href="rgant.html#_rgant-DomainServiceLayout_menuOrder"><code>@DomainServiceLayout#menuOrder()</code></a> (as explained in the <a href="#_rgsvc_intro_overriding-the-services">introduction</a> to this guide).</p>
+ <p>To use an alternative implementation, use <a href="rgant.html#_rgant-DomainServiceLayout_menuOrder"><code>@DomainServiceLayout#menuOrder()</code></a> (as explained in the <a href="#__rgsvc_intro_overriding-the-services">introduction</a> to this guide).</p>
</div>
</div>
<div class="sect3">
@@ -7769,10 +7769,10 @@ Element customerXsd = snapshot.getXsdElement();</code></pre>
<div class="sect2">
<h3 id="_rgsvc_api_LayoutService">8.2. <code>LayoutService</code></h3>
<div class="paragraph">
- <p>The <code>LayoutService</code> provides the ability to obtain the XML layout for a single domain object or for all domain objects. This functionality is surfaced through the user interface through a related <a href="#_rgsvc_api_LayoutService_related-mixins-and-menus">mixin and menu action</a>.</p>
+ <p>The <code>LayoutService</code> provides the ability to obtain the XML layout for a single domain object or for all domain objects. This functionality is surfaced through the user interface through a related <a href="#__rgsvc_api_LayoutService_related-mixins-and-menus">mixin and menu action</a>.</p>
</div>
<div class="sect3">
- <h4 id="_rgsvc_api_LayoutService_api-and-implementation">8.2.1. API & Implementation</h4>
+ <h4 id="__rgsvc_api_LayoutService_api-and-implementation">8.2.1. API & Implementation</h4>
<div class="paragraph">
<p>The API defined by <code>LayoutService</code> is:</p>
</div>
@@ -7865,7 +7865,7 @@ Element customerXsd = snapshot.getXsdElement();</code></pre>
</div>
</div>
<div class="sect3">
- <h4 id="_rgsvc_api_LayoutService_related-mixins-and-menus">8.2.2. Related Mixins and Menus</h4>
+ <h4 id="__rgsvc_api_LayoutService_related-mixins-and-menus">8.2.2. Related Mixins and Menus</h4>
<div class="paragraph">
<p>The service\u2019s functionality is exposed in the UI through a mixin (per object) and a menu action (for all objects):</p>
</div>
@@ -7880,7 +7880,7 @@ Element customerXsd = snapshot.getXsdElement();</code></pre>
</div>
</div>
<div class="sect3">
- <h4 id="_rgsvc_api_LayoutService_related-domain-services">8.2.3. Related Domain Services</h4>
+ <h4 id="__rgsvc_api_LayoutService_related-domain-services">8.2.3. Related Domain Services</h4>
<div class="paragraph">
<p>The <a href="#_rgsvc_spi_GridService"><code>GridService</code></a> is responsible for loading and normalizing layout XML for a domain class. It in turn uses the <a href="#_rgsvc_spi_GridLoaderService"><code>GridLoaderService</code></a> and <a href="#_rgsvc_spi_GridSystemService"><code>GridSystemService</code></a> services.</p>
</div>
@@ -7962,7 +7962,7 @@ Element customerXsd = snapshot.getXsdElement();</code></pre>
<p>Assuming that the <code>configuration-and-annotation</code> services installer is configured (implicit if using the <code>AppManifest</code> to <a href="rgcms.html#_rgcms_classes_AppManifest-bootstrapping">bootstrap the app</a>) then Apache Isis' core implementation of <code>MetamodelService</code> service is automatically registered and injected (it is annotated with <code>@DomainService</code>) so no further configuration is required.</p>
</div>
<div class="paragraph">
- <p>To use an alternative implementation, use <a href="rgant.html#_rgant-DomainServiceLayout_menuOrder"><code>@DomainServiceLayout#menuOrder()</code></a> (as explained in the <a href="#_rgsvc_intro_overriding-the-services">introduction</a> to this guide).</p>
+ <p>To use an alternative implementation, use <a href="rgant.html#_rgant-DomainServiceLayout_menuOrder"><code>@DomainServiceLayout#menuOrder()</code></a> (as explained in the <a href="#__rgsvc_intro_overriding-the-services">introduction</a> to this guide).</p>
</div>
</div>
<div class="sect3">
@@ -8063,7 +8063,7 @@ repositoryService.persist(cust);</code></pre>
<p>Assuming that the <code>configuration-and-annotation</code> services installer is configured (implicit if using the <code>AppManifest</code> to <a href="rgcms.html#_rgcms_classes_AppManifest-bootstrapping">bootstrap the app</a>) then Apache Isis' core implementation of <code>ServiceRegistry</code> service is automatically registered and injected (it is annotated with <code>@DomainService</code>) so no further configuration is required.</p>
</div>
<div class="paragraph">
- <p>To use an alternative implementation, use <a href="rgant.html#_rgant-DomainServiceLayout_menuOrder"><code>@DomainServiceLayout#menuOrder()</code></a> (as explained in the <a href="#_rgsvc_intro_overriding-the-services">introduction</a> to this guide).</p>
+ <p>To use an alternative implementation, use <a href="rgant.html#_rgant-DomainServiceLayout_menuOrder"><code>@DomainServiceLayout#menuOrder()</code></a> (as explained in the <a href="#__rgsvc_intro_overriding-the-services">introduction</a> to this guide).</p>
</div>
</div>
</div>
@@ -8089,7 +8089,7 @@ repositoryService.persist(cust);</code></pre>
</table>
</div>
<div class="sect3">
- <h4 id="_rgsvc_api_SwaggerService_api-and-implementation">8.5.1. API & Implementation</h4>
+ <h4 id="__rgsvc_api_SwaggerService_api-and-implementation">8.5.1. API & Implementation</h4>
<div class="paragraph">
<p>The API defined by <code>SwaggerService</code> is:</p>
</div>
@@ -8470,7 +8470,7 @@ repositoryService.persist(cust);</code></pre>
<td class="icon"> <i class="fa icon-important" title="Important"></i> </td>
<td class="content">
<div class="paragraph">
- <p>Note however that this the "effective user" does not propagate through to the <a href="ugsec.html">Shiro security mechanism</a>, which will continue to be evaluated according to the permissions of the current user. See the <a href="#_rgsvc_api_SudoService_ACCESS-ALL-ROLE"><code>ACCESS-ALL-ROLE</code></a> below for details of how to circumvent this.</p>
+ <p>Note however that this the "effective user" does not propagate through to the <a href="ugsec.html">Shiro security mechanism</a>, which will continue to be evaluated according to the permissions of the current user. See the <a href="#__rgsvc_api_SudoService_ACCESS-ALL-ROLE"><code>ACCESS-ALL-ROLE</code></a> below for details of how to circumvent this.</p>
</div> </td>
</tr>
</tbody>
@@ -8504,7 +8504,7 @@ repositoryService.persist(cust);</code></pre>
</div>
</div>
<div class="sect4">
- <h5 id="_rgsvc_api_SudoService_ACCESS-ALL-ROLE">ACCESS_ALL_ROLE</h5>
+ <h5 id="__rgsvc_api_SudoService_ACCESS-ALL-ROLE">ACCESS_ALL_ROLE</h5>
<div class="paragraph">
<p>When <code>sudo(\u2026\u200b)</code> is called the "effective user" is reported by both <a href="#_rgsvc_api_UserService"><code>UserService</code></a> and by <a href="rgfis.html#_rgfis_spi_AuthenticationSessionProvider"><code>AuthenticationSessionProvider</code></a>, but does not propagate through to the <a href="ugsec.html">Shiro security mechanism</a>. These continue to be evaluated according to the permissions of the current user.</p>
</div>
@@ -8584,7 +8584,7 @@ repositoryService.persist(cust);</code></pre>
<p>Assuming that the <code>configuration-and-annotation</code> services installer is configured (implicit if using the <code>AppManifest</code> to <a href="rgcms.html#_rgcms_classes_AppManifest-bootstrapping">bootstrap the app</a>) then Apache Isis' core implementation of <code>SudoService</code> service is automatically registered and injected (it is annotated with <code>@DomainService</code>) so no further configuration is required.</p>
</div>
<div class="paragraph">
- <p>To use an alternative implementation, use <a href="rgant.html#_rgant-DomainServiceLayout_menuOrder"><code>@DomainServiceLayout#menuOrder()</code></a> (as explained in the <a href="#_rgsvc_intro_overriding-the-services">introduction</a> to this guide).</p>
+ <p>To use an alternative implementation, use <a href="rgant.html#_rgant-DomainServiceLayout_menuOrder"><code>@DomainServiceLayout#menuOrder()</code></a> (as explained in the <a href="#__rgsvc_intro_overriding-the-services">introduction</a> to this guide).</p>
</div>
</div>
</div>
@@ -8738,7 +8738,7 @@ repositoryService.persist(cust);</code></pre>
<p>The following sections discuss the functionality provided by the service, broken out into categories.</p>
</div>
<div class="sect3">
- <h4 id="_rgsvc_api_IsisJdoSupport_executing-sql">10.1.1. Executing SQL</h4>
+ <h4 id="__rgsvc_api_IsisJdoSupport_executing-sql">10.1.1. Executing SQL</h4>
<div class="paragraph">
<p>You can use the <code>IsisJdoSupportService</code> to perform arbitrary SQL SELECTs or UPDATEs:</p>
</div>
@@ -8782,7 +8782,7 @@ repositoryService.persist(cust);</code></pre>
<td class="icon"> <i class="fa icon-tip" title="Tip"></i> </td>
<td class="content">
<div class="paragraph">
- <p>As an alternative, consider using DataNucleus' <a href="http://www.datanucleus.org/products/accessplatform_4_0/jdo/jdoql_typesafe.html">type-safe JDO query API</a>, discussed <a href="#_rgsvc_api_IsisJdoSupport_type-safe-query-api">below</a>.</p>
+ <p>As an alternative, consider using DataNucleus' <a href="http://www.datanucleus.org/products/accessplatform_4_0/jdo/jdoql_typesafe.html">type-safe JDO query API</a>, discussed <a href="#__rgsvc_api_IsisJdoSupport_type-safe-query-api">below</a>.</p>
</div> </td>
</tr>
</tbody>
@@ -8790,7 +8790,7 @@ repositoryService.persist(cust);</code></pre>
</div>
</div>
<div class="sect3">
- <h4 id="_rgsvc_api_IsisJdoSupport_type-safe-jdoql-queries">10.1.2. Type-safe JDOQL Queries</h4>
+ <h4 id="__rgsvc_api_IsisJdoSupport_type-safe-jdoql-queries">10.1.2. Type-safe JDOQL Queries</h4>
<div class="paragraph">
<p>DataNucleus provides an <a href="http://www.datanucleus.org/products/accessplatform_4_0/jdo/jdoql_typesafe.html">extension to JDO</a>, so that JDOQL queries can be built up and executed using a set of type-safe classes.</p>
</div>
@@ -8882,9 +8882,9 @@ repositoryService.persist(cust);</code></pre>
</div>
</div>
<div class="sect3">
- <h4 id="_rgsvc_api_IsisJdoSupport_fixture-support">10.1.3. Fixture support</h4>
+ <h4 id="__rgsvc_api_IsisJdoSupport_fixture-support">10.1.3. Fixture support</h4>
<div class="paragraph">
- <p>When writing <a href="ugtst.html#_ugtst_integ-test-support">integration tests</a> you\u2019ll usually need to tear down some/all mutable transactional data before each test. One way to do that is to use the <code>executeUpdate(\u2026\u200b)</code> method described <a href="#_rgsvc_api_IsisJdoSupport_executing-sql">above</a>.</p>
+ <p>When writing <a href="ugtst.html#_ugtst_integ-test-support">integration tests</a> you\u2019ll usually need to tear down some/all mutable transactional data before each test. One way to do that is to use the <code>executeUpdate(\u2026\u200b)</code> method described <a href="#__rgsvc_api_IsisJdoSupport_executing-sql">above</a>.</p>
</div>
<div class="paragraph">
<p>Alternatively, the <code>deleteAll(\u2026\u200b)</code> method will let your test delete all instances of a class without resorting to SQL:</p>
@@ -8930,7 +8930,7 @@ repositoryService.persist(cust);</code></pre>
</div>
</div>
<div class="sect3">
- <h4 id="_rgsvc_api_IsisJdoSupport_reloading-entities">10.1.4. Reloading entities</h4>
+ <h4 id="__rgsvc_api_IsisJdoSupport_reloading-entities">10.1.4. Reloading entities</h4>
<div class="paragraph">
<p>An <a href="http://www.datanucleus.org/products/datanucleus/jdo/orm/relationships.html">(intentional) limitation</a> of JDO/DataNucleus is that persisting a child entity (in a 1:n bidirectional relationship) does not cause the parent\u2019s collection to be updated.</p>
</div>
@@ -9002,7 +9002,7 @@ repositoryService.persist(cust);</code></pre>
</div>
</div>
<div class="sect3">
- <h4 id="_rgsvc_api_IsisJdoSupport_jdo-persistencemanager">10.1.5. JDO <code>PersistenceManager</code></h4>
+ <h4 id="__rgsvc_api_IsisJdoSupport_jdo-persistencemanager">10.1.5. JDO <code>PersistenceManager</code></h4>
<div class="paragraph">
<p>The functionality provided by <code>IsisJdoSupport</code> focus only on the most common use cases. If you require more flexibility than this, eg for dynamically constructed queries, then you can use the service to access the underlying JDO <code>PersistenceManager</code> API:</p>
</div>
@@ -9036,7 +9036,7 @@ repositoryService.persist(cust);</code></pre>
<p>Assuming that the <code>configuration-and-annotation</code> services installer is configured (implicit if using the <code>AppManifest</code> to <a href="rgcms.html#_rgcms_classes_AppManifest-bootstrapping">bootstrap the app</a>) then Apache Isis' core implementation of <code>IsisJdoSupport</code> service is automatically registered and injected (it is annotated with <code>@DomainService</code>) so no further configuration is required.</p>
</div>
<div class="paragraph">
- <p>To use an alternative implementation, use <a href="rgant.html#_rgant-DomainServiceLayout_menuOrder"><code>@DomainServiceLayout#menuOrder()</code></a> (as explained in the <a href="#_rgsvc_intro_overriding-the-services">introduction</a> to this guide).</p>
+ <p>To use an alternative implementation, use <a href="rgant.html#_rgant-DomainServiceLayout_menuOrder"><code>@DomainServiceLayout#menuOrder()</code></a> (as explained in the <a href="#__rgsvc_intro_overriding-the-services">introduction</a> to this guide).</p>
</div>
</div>
</div>
@@ -9230,7 +9230,7 @@ repositoryService.persist(cust);</code></pre>
<p>Assuming that the <code>configuration-and-annotation</code> services installer is configured (implicit if using the <code>AppManifest</code> to <a href="rgcms.html#_rgcms_classes_AppManifest-bootstrapping">bootstrap the app</a>) then Apache Isis' core implementation of <code>QueryResultsCache</code> service is automatically registered and injected (it is annotated with <code>@DomainService</code>) so no further configuration is required.</p>
</div>
<div class="paragraph">
- <p>To use an alternative implementation, use <a href="rgant.html#_rgant-DomainServiceLayout_menuOrder"><code>@DomainServiceLayout#menuOrder()</code></a> (as explained in the <a href="#_rgsvc_intro_overriding-the-services">introduction</a> to this guide).</p>
+ <p>To use an alternative implementation, use <a href="rgant.html#_rgant-DomainServiceLayout_menuOrder"><code>@DomainServiceLayout#menuOrder()</code></a> (as explained in the <a href="#__rgsvc_intro_overriding-the-services">introduction</a> to this guide).</p>
</div>
</div>
<div class="sect3">
@@ -9618,7 +9618,7 @@ public static final String KEY_DISABLE_AUTOFLUSH = "isis.services.container.disa
<p>Assuming that the <code>configuration-and-annotation</code> services installer is configured (implicit if using the <code>AppManifest</code> to <a href="rgcms.html#_rgcms_classes_AppManifest-bootstrapping">bootstrap the app</a>) then Apache Isis' core implementation of <code>RepositoryService</code> service is automatically registered and injected (it is annotated with <code>@DomainService</code>) so no further configuration is required.</p>
</div>
<div class="paragraph">
- <p>To use an alternative implementation, use <a href="rgant.html#_rgant-DomainServiceLayout_menuOrder"><code>@DomainServiceLayout#menuOrder()</code></a> (as explained in the <a href="#_rgsvc_intro_overriding-the-services">introduction</a> to this guide).</p>
+ <p>To use an alternative implementation, use <a href="rgant.html#_rgant-DomainServiceLayout_menuOrder"><code>@DomainServiceLayout#menuOrder()</code></a> (as explained in the <a href="#__rgsvc_intro_overriding-the-services">introduction</a> to this guide).</p>
</div>
</div>
<div class="sect3">
@@ -10756,7 +10756,7 @@ log4j.additivity.org.apache.isis.applib.services.publish.PublisherServiceLogging
<p>Assuming that the <code>configuration-and-annotation</code> services installer is configured (implicit if using the <code>AppManifest</code> to <a href="rgcms.html#_rgcms_classes_AppManifest-bootstrapping">bootstrap the app</a>) then Apache Isis' core implementation of <code>ClassDiscoveryService2</code> service is automatically registered and injected (it is annotated with <code>@DomainService</code>) so no further configuration is required.</p>
</div>
<div class="paragraph">
- <p>To use an alternative implementation, use <a href="rgant.html#_rgant-DomainServiceLayout_menuOrder"><code>@DomainServiceLayout#menuOrder()</code></a> (as explained in the <a href="#_rgsvc_intro_overriding-the-services">introduction</a> to this guide).</p>
+ <p>To use an alternative implementation, use <a href="rgant.html#_rgant-DomainServiceLayout_menuOrder"><code>@DomainServiceLayout#menuOrder()</code></a> (as explained in the <a href="#__rgsvc_intro_overriding-the-services">introduction</a> to this guide).</p>
</div>
</div>
</div>
@@ -10778,11 +10778,11 @@ log4j.additivity.org.apache.isis.applib.services.publish.PublisherServiceLogging
</ul> </li>
<li><a href="#_rgsvc_intro">2. Introduction</a>
<ul class="sectlevel2">
- <li><a href="#_rgsvc_intro_types-of-domain-services">2.1. Types of Domain Service</a></li>
- <li><a href="#_rgsvc_intro_public-api">2.2. Public API vs Internal Services</a></li>
- <li><a href="#_rgsvc_intro_using-the-services">2.3. Using the services</a></li>
- <li><a href="#_rgsvc_intro_overriding-the-services">2.4. Overriding the services</a></li>
- <li><a href="#_rgsvc_intro_commands-and-events">2.5. Command and Events</a></li>
+ <li><a href="#__rgsvc_intro_types-of-domain-services">2.1. Types of Domain Service</a></li>
+ <li><a href="#__rgsvc_intro_public-api">2.2. Public API vs Internal Services</a></li>
+ <li><a href="#__rgsvc_intro_using-the-services">2.3. Using the services</a></li>
+ <li><a href="#__rgsvc_intro_overriding-the-services">2.4. Overriding the services</a></li>
+ <li><a href="#__rgsvc_intro_commands-and-events">2.5. Command and Events</a></li>
</ul> </li>
<li><a href="#_rgsvc_presentation-layer-spi">3. Presentation Layer SPI</a>
<ul class="sectlevel2">
@@ -10867,7 +10867,7 @@ log4j.additivity.org.apache.isis.applib.services.publish.PublisherServiceLogging
<li><a href="#_spi_12">3.12.1. SPI</a></li>
<li><a href="#_implementation_11">3.12.2. Implementation</a></li>
<li><a href="#_registering_the_services_9">3.12.3. Registering the Services</a></li>
- <li><a href="#_rgsvc_api_LayoutService_related-mixins-and-menus">3.12.4. Related Menus</a></li>
+ <li><a href="#__rgsvc_api_LayoutService_related-mixins-and-menus">3.12.4. Related Menus</a></li>
<li><a href="#_related_services_9">3.12.5. Related Services</a></li>
</ul> </li>
<li><a href="#_rgsvc_spi_TranslationsResolver">3.13. <code>TranslationsResolver</code></a>
@@ -10915,7 +10915,7 @@ log4j.additivity.org.apache.isis.applib.services.publish.PublisherServiceLogging
</ul> </li>
<li><a href="#_rgsvc_api_CommandContext">4.4. <code>CommandContext</code></a>
<ul class="sectlevel3">
- <li><a href="#_rgsvc_api_CommandContext_screencast">4.4.1. Screencast</a></li>
+ <li><a href="#__rgsvc_api_CommandContext_screencast">4.4.1. Screencast</a></li>
<li><a href="#_api_implementation_4">4.4.2. API & Implementation</a></li>
<li><a href="#_usage_4">4.4.3. Usage</a></li>
<li><a href="#_interacting_with_the_services">4.4.4. Interacting with the services</a></li>
@@ -10932,7 +10932,7 @@ log4j.additivity.org.apache.isis.applib.services.publish.PublisherServiceLogging
</ul> </li>
<li><a href="#_interacting_with_the_services_2">4.5.2. Interacting with the services</a></li>
<li><a href="#_registering_the_service_6">4.5.3. Registering the Service</a></li>
- <li><a href="#_rgsvc_api_InteractionContext_Related-Classes">4.5.4. Related Classes</a></li>
+ <li><a href="#__rgsvc_api_InteractionContext_Related-Classes">4.5.4. Related Classes</a></li>
</ul> </li>
<li><a href="#_rgsvc_api_MessageService">4.6. <code>MessageService</code></a>
<ul class="sectlevel3">
@@ -11030,17 +11030,17 @@ log4j.additivity.org.apache.isis.applib.services.publish.PublisherServiceLogging
</ul> </li>
<li><a href="#_rgsvc_api_EventBusService">6.4. <code>EventBusService</code></a>
<ul class="sectlevel3">
- <li><a href="#_rgsvc_api_EventBusService_api-and-implementation">6.4.1. API & Implementation</a></li>
+ <li><a href="#__rgsvc_api_EventBusService_api-and-implementation">6.4.1. API & Implementation</a></li>
<li><a href="#_registering_subscribers">6.4.2. Registering Subscribers</a></li>
<li><a href="#_annotating_members">6.4.3. Annotating Members</a></li>
- <li><a href="#_rgsvc_api_EventBusService_event-hierarchy">6.4.4. Event hierarchy</a>
+ <li><a href="#__rgsvc_api_EventBusService_event-hierarchy">6.4.4. Event hierarchy</a>
<ul class="sectlevel4">
<li><a href="#_variation_for_contributing_services">Variation (for contributing services)</a></li>
</ul> </li>
<li><a href="#_programmatic_posting">6.4.5. Programmatic posting</a></li>
<li><a href="#_using_code_wrapperfactory_code">6.4.6. Using <code>WrapperFactory</code></a></li>
<li><a href="#_implementation_spi">6.4.7. Implementation SPI</a></li>
- <li><a href="#_rgsvc_api_EventBusService_Configuration">6.4.8. Configuration</a></li>
+ <li><a href="#__rgsvc_api_EventBusService_Configuration">6.4.8. Configuration</a></li>
<li><a href="#_registering_the_services_14">6.4.9. Registering the Services</a></li>
<li><a href="#_related_services_16">6.4.10. Related Services</a></li>
</ul> </li>
@@ -11098,7 +11098,7 @@ log4j.additivity.org.apache.isis.applib.services.publish.PublisherServiceLogging
</ul> </li>
<li><a href="#_rgsvc_api_JaxbService">7.5. <code>JaxbService</code></a>
<ul class="sectlevel3">
- <li><a href="#_rgsvc_api_JaxbService_api-and-implementation">7.5.1. API & Implementation</a></li>
+ <li><a href="#__rgsvc_api_JaxbService_api-and-implementation">7.5.1. API & Implementation</a></li>
<li><a href="#_usage_within_the_framework_2">7.5.2. Usage within the framework</a></li>
<li><a href="#_registering_the_service_20">7.5.3. Registering the Service</a></li>
</ul> </li>
@@ -11129,9 +11129,9 @@ log4j.additivity.org.apache.isis.applib.services.publish.PublisherServiceLogging
</ul> </li>
<li><a href="#_rgsvc_api_LayoutService">8.2. <code>LayoutService</code></a>
<ul class="sectlevel3">
- <li><a href="#_rgsvc_api_LayoutService_api-and-implementation">8.2.1. API & Implementation</a></li>
- <li><a href="#_rgsvc_api_LayoutService_related-mixins-and-menus">8.2.2. Related Mixins and Menus</a></li>
- <li><a href="#_rgsvc_api_LayoutService_related-domain-services">8.2.3. Related Domain Services</a></li>
+ <li><a href="#__rgsvc_api_LayoutService_api-and-implementation">8.2.1. API & Implementation</a></li>
+ <li><a href="#__rgsvc_api_LayoutService_related-mixins-and-menus">8.2.2. Related Mixins and Menus</a></li>
+ <li><a href="#__rgsvc_api_LayoutService_related-domain-services">8.2.3. Related Domain Services</a></li>
</ul> </li>
<li><a href="#_rgsvc_api_MetaModelService">8.3. <code>MetaModelService3</code></a>
<ul class="sectlevel3">
@@ -11149,7 +11149,7 @@ log4j.additivity.org.apache.isis.applib.services.publish.PublisherServiceLogging
</ul> </li>
<li><a href="#_rgsvc_api_SwaggerService">8.5. <code>SwaggerService</code></a>
<ul class="sectlevel3">
- <li><a href="#_rgsvc_api_SwaggerService_api-and-implementation">8.5.1. API & Implementation</a></li>
+ <li><a href="#__rgsvc_api_SwaggerService_api-and-implementation">8.5.1. API & Implementation</a></li>
<li><a href="#_usage_within_the_framework_3">8.5.2. Usage within the framework</a></li>
<li><a href="#_registering_the_service_26">8.5.3. Registering the Service</a></li>
<li><a href="#_related_services_24">8.5.4. Related Services</a></li>
@@ -11178,7 +11178,7 @@ log4j.additivity.org.apache.isis.applib.services.publish.PublisherServiceLogging
<li><a href="#_implementation_28">9.4.2. Implementation</a></li>
<li><a href="#_usage_14">9.4.3. Usage</a>
<ul class="sectlevel4">
- <li><a href="#_rgsvc_api_SudoService_ACCESS-ALL-ROLE">ACCESS_ALL_ROLE</a></li>
+ <li><a href="#__rgsvc_api_SudoService_ACCESS-ALL-ROLE">ACCESS_ALL_ROLE</a></li>
</ul> </li>
<li><a href="#_spi_19">9.4.4. SPI</a></li>
<li><a href="#_registering_the_service_27">9.4.5. Registering the Service</a></li>
@@ -11193,11 +11193,11 @@ log4j.additivity.org.apache.isis.applib.services.publish.PublisherServiceLogging
<ul class="sectlevel2">
<li><a href="#_rgsvc_api_IsisJdoSupport">10.1. <code>IsisJdoSupport</code></a>
<ul class="sectlevel3">
- <li><a href="#_rgsvc_api_IsisJdoSupport_executing-sql">10.1.1. Executing SQL</a></li>
- <li><a href="#_rgsvc_api_IsisJdoSupport_type-safe-jdoql-queries">10.1.2. Type-safe JDOQL Queries</a></li>
- <li><a href="#_rgsvc_api_IsisJdoSupport_fixture-support">10.1.3. Fixture support</a></li>
- <li><a href="#_rgsvc_api_IsisJdoSupport_reloading-entities">10.1.4. Reloading entities</a></li>
- <li><a href="#_rgsvc_api_IsisJdoSupport_jdo-persistencemanager">10.1.5. JDO <code>PersistenceManager</code></a></li>
+ <li><a href="#__rgsvc_api_IsisJdoSupport_executing-sql">10.1.1. Executing SQL</a></li>
+ <li><a href="#__rgsvc_api_IsisJdoSupport_type-safe-jdoql-queries">10.1.2. Type-safe JDOQL Queries</a></li>
+ <li><a href="#__rgsvc_api_IsisJdoSupport_fixture-support">10.1.3. Fixture support</a></li>
+ <li><a href="#__rgsvc_api_IsisJdoSupport_reloading-entities">10.1.4. Reloading entities</a></li>
+ <li><a href="#__rgsvc_api_IsisJdoSupport_jdo-persistencemanager">10.1.5. JDO <code>PersistenceManager</code></a></li>
<li><a href="#_registering_the_services_18">10.1.6. Registering the Services</a></li>
</ul> </li>
<li><a href="#_rgsvc_api_MetricsService">10.2. <code>MetricsService</code></a>