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 2015/12/03 19:15:55 UTC
[37/51] [abbrv] isis git commit: ISIS-1243: removing manpage from
.adoc file names.
http://git-wip-us.apache.org/repos/asf/isis/blob/43fc7bc1/adocs/documentation/src/main/asciidoc/guides/_rgsvc-api_DomainObjectContainer_validation-api.adoc
----------------------------------------------------------------------
diff --git a/adocs/documentation/src/main/asciidoc/guides/_rgsvc-api_DomainObjectContainer_validation-api.adoc b/adocs/documentation/src/main/asciidoc/guides/_rgsvc-api_DomainObjectContainer_validation-api.adoc
index 30dbc15..fe1b732 100644
--- a/adocs/documentation/src/main/asciidoc/guides/_rgsvc-api_DomainObjectContainer_validation-api.adoc
+++ b/adocs/documentation/src/main/asciidoc/guides/_rgsvc-api_DomainObjectContainer_validation-api.adoc
@@ -6,7 +6,7 @@
-The validation API allows a domain object to programmatically validate itself or any other domain object. Specifically, this means the validating the current state of all properties, as well as any object-level validation defined by xref:rgcms.adoc#_rgcms_methods_reserved_manpage-validate[`validate()`].
+The validation API allows a domain object to programmatically validate itself or any other domain object. Specifically, this means the validating the current state of all properties, as well as any object-level validation defined by xref:rgcms.adoc#_rgcms_methods_reserved_validate[`validate()`].
The API provided is:
@@ -23,4 +23,4 @@ public interface DomainObjectContainer {
If an object is changed by editing its properties, then (using the xref:ugvw.adoc#[Wicket viewer] at least) Apache Isis will check that the state of the object is valid. There is currently however no equivalent guarantee for actions.
-The intent of this API was (originally at least) to provide a fallback whereby actions could at least be able to perform this validation programmatically (eg in their own xref:rgcms.adoc#_rgcms_methods_prefixes_manpage-validate[`validate...()`] or xref:rgcms.adoc#_rgcms_methods_prefixes_manpage-disable[`disable...()`] methods. However, this feature should be considered experimental; your mileage may vary.
\ No newline at end of file
+The intent of this API was (originally at least) to provide a fallback whereby actions could at least be able to perform this validation programmatically (eg in their own xref:rgcms.adoc#_rgcms_methods_prefixes_validate[`validate...()`] or xref:rgcms.adoc#_rgcms_methods_prefixes_disable[`disable...()`] methods. However, this feature should be considered experimental; your mileage may vary.
\ No newline at end of file
http://git-wip-us.apache.org/repos/asf/isis/blob/43fc7bc1/adocs/documentation/src/main/asciidoc/guides/_rgsvc-api_EventBusService.adoc
----------------------------------------------------------------------
diff --git a/adocs/documentation/src/main/asciidoc/guides/_rgsvc-api_EventBusService.adoc b/adocs/documentation/src/main/asciidoc/guides/_rgsvc-api_EventBusService.adoc
index b2d620a..7fdde83 100644
--- a/adocs/documentation/src/main/asciidoc/guides/_rgsvc-api_EventBusService.adoc
+++ b/adocs/documentation/src/main/asciidoc/guides/_rgsvc-api_EventBusService.adoc
@@ -89,7 +89,7 @@ This works for both singleton (application-scoped) and also xref:rgant.adoc#_rga
[TIP]
====
-The xref:rgcms.adoc#_rgcms_classes_super_manpage-AbstractSubscriber[`AbstractSubscriber`] class automatically performs this
+The xref:rgcms.adoc#_rgcms_classes_super_AbstractSubscriber[`AbstractSubscriber`] class automatically performs this
registration. As a convenience, (as of `1.11.0-SNAPSHOT`) it is also annotated with the
xref:rgant.adoc#_rgant-DomainServiceLayout_menuOrder[`@DomainServiceLayout#menuOrder()`] attribute.
====
http://git-wip-us.apache.org/repos/asf/isis/blob/43fc7bc1/adocs/documentation/src/main/asciidoc/guides/_rgsvc-api_FixtureScriptsDefault.adoc
----------------------------------------------------------------------
diff --git a/adocs/documentation/src/main/asciidoc/guides/_rgsvc-api_FixtureScriptsDefault.adoc b/adocs/documentation/src/main/asciidoc/guides/_rgsvc-api_FixtureScriptsDefault.adoc
index ac22f43..83e2fbb 100644
--- a/adocs/documentation/src/main/asciidoc/guides/_rgsvc-api_FixtureScriptsDefault.adoc
+++ b/adocs/documentation/src/main/asciidoc/guides/_rgsvc-api_FixtureScriptsDefault.adoc
@@ -8,13 +8,13 @@
The `FixtureScriptsDefault` service provides the ability to execute xref:ugtst.adoc#_ugtst_fixture-scripts_api-and-usage[fixture scripts] .
-The service extends from the xref:rgcms.adoc#_rgcms_classes_super_manpage-FixtureScripts[`FixtureScripts`], and is only instantiated by the framework if there no custom implementation of `FixtureScripts` has been otherwise provided; in other words it is a fallback.
+The service extends from the xref:rgcms.adoc#_rgcms_classes_super_FixtureScripts[`FixtureScripts`], and is only instantiated by the framework if there no custom implementation of `FixtureScripts` has been otherwise provided; in other words it is a fallback.
If this service is instantiated (as a fallback) then it uses the xref:rgsvc.adoc#_rgsvc-spi_FixtureScriptsSpecificationProvider[`FixtureScriptsSpecificationProvider`] to obtain a `FixtureScriptsSpecification`. This configures this service, telling it which package to search for `FixtureScript` classes, how to execute those classes, and hints that influence the UI.
[TIP]
====
-We recommend using xref:rgsvc.adoc#_rgsvc-spi_FixtureScriptsSpecificationProvider[`FixtureScriptsSpecificationProvider`] rather than subclassing xref:rgcms.adoc#_rgcms_classes_super_manpage-FixtureScripts[`FixtureScripts`].
+We recommend using xref:rgsvc.adoc#_rgsvc-spi_FixtureScriptsSpecificationProvider[`FixtureScriptsSpecificationProvider`] rather than subclassing xref:rgcms.adoc#_rgcms_classes_super_FixtureScripts[`FixtureScripts`].
====
@@ -33,7 +33,7 @@ public class FixtureScriptsDefault ... {
}
----
-... in other words the same as xref:rgcms.adoc#_rgcms_classes_super_manpage-FixtureScripts[`FixtureScripts`] superclass that it inherits from.
+... in other words the same as xref:rgcms.adoc#_rgcms_classes_super_FixtureScripts[`FixtureScripts`] superclass that it inherits from.
== Configuration
http://git-wip-us.apache.org/repos/asf/isis/blob/43fc7bc1/adocs/documentation/src/main/asciidoc/guides/_rgsvc-api_JaxbService.adoc
----------------------------------------------------------------------
diff --git a/adocs/documentation/src/main/asciidoc/guides/_rgsvc-api_JaxbService.adoc b/adocs/documentation/src/main/asciidoc/guides/_rgsvc-api_JaxbService.adoc
index 5008e43..198534d 100644
--- a/adocs/documentation/src/main/asciidoc/guides/_rgsvc-api_JaxbService.adoc
+++ b/adocs/documentation/src/main/asciidoc/guides/_rgsvc-api_JaxbService.adoc
@@ -50,7 +50,7 @@ Isis provides a default implementation of the service, `o.a.i.schema.services.ja
This service is provided as a convenience for applications, but is also used internally by the framework to
xref:rgant.adoc#_rgant-XmlRootElement[`@XmlRootElement`]-annotated
xref:ugbtb.adoc#_ugbtb_more-advanced_view-models[view models]. The functionality to download XML and XSD schemas is also
-exposed in the UI through mixins to xref:rgcms.adoc#_rgcms_classes_roles_manpage-Dto[`Dto`] interface.
+exposed in the UI through mixins to xref:rgcms.adoc#_rgcms_classes_roles_Dto[`Dto`] interface.
http://git-wip-us.apache.org/repos/asf/isis/blob/43fc7bc1/adocs/documentation/src/main/asciidoc/guides/_rgsvc-api_MementoService.adoc
----------------------------------------------------------------------
diff --git a/adocs/documentation/src/main/asciidoc/guides/_rgsvc-api_MementoService.adoc b/adocs/documentation/src/main/asciidoc/guides/_rgsvc-api_MementoService.adoc
index 3014184..7196374 100644
--- a/adocs/documentation/src/main/asciidoc/guides/_rgsvc-api_MementoService.adoc
+++ b/adocs/documentation/src/main/asciidoc/guides/_rgsvc-api_MementoService.adoc
@@ -71,7 +71,7 @@ If using another implementation, the `canSet(...)` method can be used to check i
== Usage
-As noted in the introduction, a common use case for this service is in the implementation of the xref:rgcms.adoc#_rgcms_classes_super_manpage-AbstractViewModel[`ViewModel`] interface.
+As noted in the introduction, a common use case for this service is in the implementation of the xref:rgcms.adoc#_rgcms_classes_super_AbstractViewModel[`ViewModel`] interface.
[TIP]
====
http://git-wip-us.apache.org/repos/asf/isis/blob/43fc7bc1/adocs/documentation/src/main/asciidoc/guides/_rgsvc-api_WrapperFactory.adoc
----------------------------------------------------------------------
diff --git a/adocs/documentation/src/main/asciidoc/guides/_rgsvc-api_WrapperFactory.adoc b/adocs/documentation/src/main/asciidoc/guides/_rgsvc-api_WrapperFactory.adoc
index 2fc4fa4..d83af8a 100644
--- a/adocs/documentation/src/main/asciidoc/guides/_rgsvc-api_WrapperFactory.adoc
+++ b/adocs/documentation/src/main/asciidoc/guides/_rgsvc-api_WrapperFactory.adoc
@@ -74,8 +74,8 @@ Calling any of the above methods may result in a (subclass of) `InteractionExcep
In addition, the following methods may also be called:
-* the xref:rgcms.adoc#_rgcms_methods_reserved_manpage-title[`title()`] and `toString()` methods
-* any xref:rgcms.adoc#_rgcms_methods_prefixes_manpage-default[`default...()`], xref:rgcms.adoc#_rgcms_methods_prefixes_manpage-choices[`choices...()`] or xref:rgcms.adoc#_rgcms_methods_prefixes_manpage-autoComplete[`autoComplete...()`] methods
+* the xref:rgcms.adoc#_rgcms_methods_reserved_title[`title()`] and `toString()` methods
+* any xref:rgcms.adoc#_rgcms_methods_prefixes_default[`default...()`], xref:rgcms.adoc#_rgcms_methods_prefixes_choices[`choices...()`] or xref:rgcms.adoc#_rgcms_methods_prefixes_autoComplete[`autoComplete...()`] methods
An exception will be thrown if any other methods are thrown.
http://git-wip-us.apache.org/repos/asf/isis/blob/43fc7bc1/adocs/documentation/src/main/asciidoc/guides/_rgsvc-spi.adoc
----------------------------------------------------------------------
diff --git a/adocs/documentation/src/main/asciidoc/guides/_rgsvc-spi.adoc b/adocs/documentation/src/main/asciidoc/guides/_rgsvc-spi.adoc
index 1d3f6cb..026909d 100644
--- a/adocs/documentation/src/main/asciidoc/guides/_rgsvc-spi.adoc
+++ b/adocs/documentation/src/main/asciidoc/guides/_rgsvc-spi.adoc
@@ -60,7 +60,7 @@ The table below lists the SPIs that are defined in the Isis applib (`o.a.i.core:
`ClassDiscoveryService`]
|Mechanism to locate (from the classpath) classes with a specific annotation (eg xref:rgant.adoc#_rgant-DomainService[`@DomainService`])
-Subtypes of a given type (eg xref:rgcms.adoc#_rgcms_classes_super_manpage-FixtureScript[`FixtureScript`]).
+Subtypes of a given type (eg xref:rgcms.adoc#_rgcms_classes_super_FixtureScript[`FixtureScript`]).
|`ClassDiscoveryService-` +
`UsingReflections` +
``o.a.i.core`` +
http://git-wip-us.apache.org/repos/asf/isis/blob/43fc7bc1/adocs/documentation/src/main/asciidoc/guides/_rgsvc-spi_AuditingService.adoc
----------------------------------------------------------------------
diff --git a/adocs/documentation/src/main/asciidoc/guides/_rgsvc-spi_AuditingService.adoc b/adocs/documentation/src/main/asciidoc/guides/_rgsvc-spi_AuditingService.adoc
index a07c4fb..c8d8a62 100644
--- a/adocs/documentation/src/main/asciidoc/guides/_rgsvc-spi_AuditingService.adoc
+++ b/adocs/documentation/src/main/asciidoc/guides/_rgsvc-spi_AuditingService.adoc
@@ -46,7 +46,7 @@ The module also provides:
* `AuditingServiceRepository` service to to search for persisted `AuditEntry``s. None of its actions are visible in the user interface (they are all `@Programmatic`).
-* `AuditingServiceContributions` which contrbutes collections to the xref:rgcms.adoc#_rgcms_classes_mixins_manpage-HasTransactionId[ `HasTransactionId`] interface. This will therefore display all audit entries that occurred in a given transaction, in other words whenever a command, a published event or another audit entry is displayed.
+* `AuditingServiceContributions` which contrbutes collections to the xref:rgcms.adoc#_rgcms_classes_mixins_HasTransactionId[ `HasTransactionId`] interface. This will therefore display all audit entries that occurred in a given transaction, in other words whenever a command, a published event or another audit entry is displayed.
@@ -81,5 +81,5 @@ The auditing service works very well with the xref:rgsvc.adoc#_rgsvc-spi_Command
You may also want to configure the xref:rgsvc.adoc#_rgsvc-spi_PublishingService[`PublishingService`].
-All three of these services collaborate implicitly by way of the xref:rgcms.adoc#_rgcms_classes_mixins_manpage-HasTransactionId[`HasTransactionId`] interface.
+All three of these services collaborate implicitly by way of the xref:rgcms.adoc#_rgcms_classes_mixins_HasTransactionId[`HasTransactionId`] interface.
http://git-wip-us.apache.org/repos/asf/isis/blob/43fc7bc1/adocs/documentation/src/main/asciidoc/guides/_rgsvc-spi_ClassDiscoveryService.adoc
----------------------------------------------------------------------
diff --git a/adocs/documentation/src/main/asciidoc/guides/_rgsvc-spi_ClassDiscoveryService.adoc b/adocs/documentation/src/main/asciidoc/guides/_rgsvc-spi_ClassDiscoveryService.adoc
index 583acef..8203208 100644
--- a/adocs/documentation/src/main/asciidoc/guides/_rgsvc-spi_ClassDiscoveryService.adoc
+++ b/adocs/documentation/src/main/asciidoc/guides/_rgsvc-spi_ClassDiscoveryService.adoc
@@ -8,7 +8,7 @@
The `ClassDiscovery` service is used to automatically discover subclasses of any given type on the classpath. The primary use case is to support "convention-over-configuration" designs that work with a minimum of configuration.
-This service is used by the xref:rgcms.adoc#_rgcms_classes_super_manpage-FixtureScripts[`FixtureScripts`] service to automatically locate any xref:rgcms.adoc#_rgcms_classes_super_manpage-FixtureScript[`FixtureScript`] implementations.
+This service is used by the xref:rgcms.adoc#_rgcms_classes_super_FixtureScripts[`FixtureScripts`] service to automatically locate any xref:rgcms.adoc#_rgcms_classes_super_FixtureScript[`FixtureScript`] implementations.
http://git-wip-us.apache.org/repos/asf/isis/blob/43fc7bc1/adocs/documentation/src/main/asciidoc/guides/_rgsvc-spi_CommandService.adoc
----------------------------------------------------------------------
diff --git a/adocs/documentation/src/main/asciidoc/guides/_rgsvc-spi_CommandService.adoc b/adocs/documentation/src/main/asciidoc/guides/_rgsvc-spi_CommandService.adoc
index 0382e91..b62629b 100644
--- a/adocs/documentation/src/main/asciidoc/guides/_rgsvc-spi_CommandService.adoc
+++ b/adocs/documentation/src/main/asciidoc/guides/_rgsvc-spi_CommandService.adoc
@@ -12,8 +12,8 @@ Persistent `Command`s support several use cases:
* they enable profiling of the running application (which actions are invoked then most often, what is their response time)
* they act as a parent to any background commands that might be invoked through the xref:rgsvc.adoc#_rgsvc-api_BackgroundService[`BackgroundService`]
-* if xref:rgsvc.adoc#_rgsvc-spi_AuditingService[auditing] is configured, they provide better audit information, since the `Command` (the 'cause' of an action) can be correlated to the audit records (the "effect" of the action) by way of the xref:rgcms.adoc#_rgcms_classes_mixins_manpage-HasTransactionId[`transactionId`]
-* if xref:rgsvc.adoc#_rgsvc-spi_PublishingService[publishing] is configured, they provide better traceability as the `Command` is also correlated with any published events, again through the unique xref:rgcms.adoc#_rgcms_classes_mixins_manpage-HasTransactionId[`transactionId`]
+* if xref:rgsvc.adoc#_rgsvc-spi_AuditingService[auditing] is configured, they provide better audit information, since the `Command` (the 'cause' of an action) can be correlated to the audit records (the "effect" of the action) by way of the xref:rgcms.adoc#_rgcms_classes_mixins_HasTransactionId[`transactionId`]
+* if xref:rgsvc.adoc#_rgsvc-spi_PublishingService[publishing] is configured, they provide better traceability as the `Command` is also correlated with any published events, again through the unique xref:rgcms.adoc#_rgcms_classes_mixins_HasTransactionId[`transactionId`]
* the associated xref:rgant.adoc#_rgant-Action_command[`@Action#command()`] annotation attribute 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 `Command` to the user.
@@ -96,5 +96,5 @@ The services provided by this module combines very well with the xref:rgsvc.adoc
You may also want to configure the xref:rgsvc.adoc#_rgsvc-spi_PublishingService[`PublishingService`].
-All three of these services collaborate implicitly by way of the xref:rgcms.adoc#_rgcms_classes_mixins_manpage-HasTransactionId[`HasTransactionId`] interface.
+All three of these services collaborate implicitly by way of the xref:rgcms.adoc#_rgcms_classes_mixins_HasTransactionId[`HasTransactionId`] interface.
http://git-wip-us.apache.org/repos/asf/isis/blob/43fc7bc1/adocs/documentation/src/main/asciidoc/guides/_rgsvc-spi_EventSerializer.adoc
----------------------------------------------------------------------
diff --git a/adocs/documentation/src/main/asciidoc/guides/_rgsvc-spi_EventSerializer.adoc b/adocs/documentation/src/main/asciidoc/guides/_rgsvc-spi_EventSerializer.adoc
index 9aed9ab..7ffe90f 100644
--- a/adocs/documentation/src/main/asciidoc/guides/_rgsvc-spi_EventSerializer.adoc
+++ b/adocs/documentation/src/main/asciidoc/guides/_rgsvc-spi_EventSerializer.adoc
@@ -25,7 +25,7 @@ public interface EventSerializer {
}
----
<1> returns an object for maximum flexibility, which is then handed off to the `PublishingService`.
-<2> standard metadata about the event, such as the user, the xref:rgcms.adoc#_rgcms_classes_mixins_manpage-HasTransactionId[`transactionId`], date/time etc
+<2> standard metadata about the event, such as the user, the xref:rgcms.adoc#_rgcms_classes_mixins_HasTransactionId[`transactionId`], date/time etc
<3> for published actions, will generally be an `EventPayloadForActionInvocation` (or subclass thereof); for published objects, will generally be an `EventPayloadForObjectChanged` (or subclass thereof)
It's important to make sure that the publishing service implementation is able to handle the serialized form. Strings are a good lowest common denominator, but in some cases a type-safe equivalent, such as a w3c DOM `Document` or JSON node might be passed instead.
http://git-wip-us.apache.org/repos/asf/isis/blob/43fc7bc1/adocs/documentation/src/main/asciidoc/guides/_rgsvc-spi_FixtureScriptsSpecificationProvider.adoc
----------------------------------------------------------------------
diff --git a/adocs/documentation/src/main/asciidoc/guides/_rgsvc-spi_FixtureScriptsSpecificationProvider.adoc b/adocs/documentation/src/main/asciidoc/guides/_rgsvc-spi_FixtureScriptsSpecificationProvider.adoc
index 4fffe73..5c9dea3 100644
--- a/adocs/documentation/src/main/asciidoc/guides/_rgsvc-spi_FixtureScriptsSpecificationProvider.adoc
+++ b/adocs/documentation/src/main/asciidoc/guides/_rgsvc-spi_FixtureScriptsSpecificationProvider.adoc
@@ -11,7 +11,7 @@ xref:rgsvc.adoc#_rgsvc-api_FixtureScriptsDefault[`FixtureScriptsDefault`] domain
location to search for fixture scripts and other settings.
The service is only used if the `FixtureScriptsDefault` service is instantiated as a fallback by the framework. If
-the application provides its own subclass of xref:rgcms.adoc#_rgcms_classes_super_manpage-FixtureScripts[`FixtureScripts`]
+the application provides its own subclass of xref:rgcms.adoc#_rgcms_classes_super_FixtureScripts[`FixtureScripts`]
superclass, then this provider service is not used.
[TIP]
http://git-wip-us.apache.org/repos/asf/isis/blob/43fc7bc1/adocs/documentation/src/main/asciidoc/guides/_rgsvc-spi_PublishingService.adoc
----------------------------------------------------------------------
diff --git a/adocs/documentation/src/main/asciidoc/guides/_rgsvc-spi_PublishingService.adoc b/adocs/documentation/src/main/asciidoc/guides/_rgsvc-spi_PublishingService.adoc
index 62634ff..97d1dc3 100644
--- a/adocs/documentation/src/main/asciidoc/guides/_rgsvc-spi_PublishingService.adoc
+++ b/adocs/documentation/src/main/asciidoc/guides/_rgsvc-spi_PublishingService.adoc
@@ -25,7 +25,7 @@ public interface PublishingService {
void setEventSerializer(EventSerializer eventSerializer); // <3>
}
----
-<1> standard metadata about the event, such as the user, the xref:rgcms.adoc#_rgcms_classes_mixins_manpage-HasTransactionId[`transactionId`], date/time etc
+<1> standard metadata about the event, such as the user, the xref:rgcms.adoc#_rgcms_classes_mixins_HasTransactionId[`transactionId`], date/time etc
<2> for published actions, an `EventPayloadForActionInvocation` (or subclass thereof); for published objects, an `EventPayloadForObjectChanged` (or subclass thereof)
<3> injects in the xref:rgsvc.adoc#_rgsvc-spi_EventSerializer[`EventSerializer`] service. This is deprecated because not every implementation is required to use an `EventSerializer` so its inclusion within the SPI of `PublishingService` was in retrospect a mistake.
@@ -178,7 +178,7 @@ The `PublishingService` is intended for coarse-grained publish/subscribe for sys
The xref:rgsvc.adoc#_rgsvc-api_EventBusService[`EventBusService`] meanwhile is intended for fine-grained publish/subscribe for object-to-object interactions within an Apache Isis domain object model. The event propagation is strictly in-memory, and there are no restrictions on the object acting as the event (it need not be serializable, for example).
-All three of these services collaborate implicitly by way of the xref:rgcms.adoc#_rgcms_classes_mixins_manpage-HasTransactionId[`HasTransactionId`] interface.
+All three of these services collaborate implicitly by way of the xref:rgcms.adoc#_rgcms_classes_mixins_HasTransactionId[`HasTransactionId`] interface.
http://git-wip-us.apache.org/repos/asf/isis/blob/43fc7bc1/adocs/documentation/src/main/asciidoc/guides/_tg_stop-scaffolding-start-coding.adoc
----------------------------------------------------------------------
diff --git a/adocs/documentation/src/main/asciidoc/guides/_tg_stop-scaffolding-start-coding.adoc b/adocs/documentation/src/main/asciidoc/guides/_tg_stop-scaffolding-start-coding.adoc
index 0b88f42..f4d40a3 100644
--- a/adocs/documentation/src/main/asciidoc/guides/_tg_stop-scaffolding-start-coding.adoc
+++ b/adocs/documentation/src/main/asciidoc/guides/_tg_stop-scaffolding-start-coding.adoc
@@ -307,7 +307,7 @@ Domain entities have state: either values (primitives, strings) or references to
* for all non-optional properties will either need to prompt for a value, or calculate some suitable default
* change the implementation of title, if need be
* revisit the title, consider whether to use the xref:rgant.adoc#_rgant-Title[`@Title`] annotation
-** rather than the xref:rgcms.adoc#_rgcms_methods_reserved_manpage-title[`title()`] `title()` method
+** rather than the xref:rgcms.adoc#_rgcms_methods_reserved_title[`title()`] `title()` method
* order the properties using the xref:rgant.adoc#_rgant-MemberOrder[`@MemberOrder`], also `@MemberGroupLayout`
** see also the docs on xref:ug.adoc#_ug_object-layout_static[static layouts]
* use the xref:rgant.adoc#_rgant-PropertyLayout[`@PropertyLayout`] annotation to position property/action parameter labels either to the LEFT, TOP or NONE
@@ -324,10 +324,10 @@ Domain entities can also reference other domain entities. These references may b
* update the corresponding domain service (for creation actoin)
* use different techniques to obtain references (shown in drop-down list box)
** use the xref:rgant.adoc#_rgant-DomainObject_bounded[`@DomainObjectLayout(bounded=...)`] annotation on the referenced type if there are only a small number (bounded) of instances
-** use a xref:rgcms.adoc#_rgcms_methods_prefixes_manpage-choices[`choices...()`] supporting method
+** use a xref:rgcms.adoc#_rgcms_methods_prefixes_choices[`choices...()`] supporting method
*** on a property
*** on an action parameter
-** use a xref:rgcms.adoc#_rgcms_methods_prefixes_manpage-autoComplete[`autoComplete...()`] supporting method
+** use a xref:rgcms.adoc#_rgcms_methods_prefixes_autoComplete[`autoComplete...()`] supporting method
*** on a property
*** on an action parameter
@@ -348,7 +348,7 @@ Quick detour: often we want to set up defaults to go with choices. Sensible defa
Returning back to references, Isis also supports vector (multi-valued) references to another object instances� in other words collections. We sometimes called these "parented" collections (to distinguish from a "standalone" collection as returned from an action)
* Ensure that all domain classes implement `java.lang.Comparable`
-** use the xref:rgcms.adoc#_rgcms_classes_utility_manpage-ObjectContracts[`ObjectContracts`] utility class to help implement `Comparable`
+** use the xref:rgcms.adoc#_rgcms_classes_utility_ObjectContracts[`ObjectContracts`] utility class to help implement `Comparable`
*** you can also `equals()`, `hashCode()`, `toString()`
* Add a xref:ug.adoc#_ug_how-tos_class-structure_collections[collection] to one of the entities
** Use `SortedSet` as the class
@@ -413,7 +413,7 @@ Or, more pithily: "see it, use it, do it"
* Use the xref:rgant.adoc#_rgant-Property_hidden[`Property(hidden=...)`] annotation to make properties invisible
** likewise xref:rgant.adoc#_rgant-Collection_hidden[`@Collection(hidden=...)`] for collections
** the xref:rgant.adoc#_rgant-Programmatic[`@Programmatic`] annotation can also be used and in many cases is to be preferred; the difference is that the latter means the member is not part of the Apache Isis metamodel.
-* Use the xref:rgcms.adoc#_rgcms_methods_prefixes_manpage-hide[`hide...()`] supporting method on properties, collections and actions to make a property/collection/action invisible according to some imperative rule
+* Use the xref:rgcms.adoc#_rgcms_methods_prefixes_hide[`hide...()`] supporting method on properties, collections and actions to make a property/collection/action invisible according to some imperative rule
=== Use it!
@@ -421,14 +421,14 @@ Or, more pithily: "see it, use it, do it"
* Use the xref:rgant.adoc#_rgant-Property_editing[`Property(editing=...)`] annotation to make property read-only
** likewise xref:rgant.adoc#_rgant-Collection_editing[`@Collection(editing=...)`] for collections
** alternatively, use xref:rgant.adoc#_rgant-DomainObject_editing[`@DomainObject(editing=...)`] to disable editing for all properties/collections
-* Use the xref:rgcms.adoc#_rgcms_methods_prefixes_manpage-disable[`disable...()`] supporting method on properties and actions to make a property/action disabled according to some imperative rule
+* Use the xref:rgcms.adoc#_rgcms_methods_prefixes_disable[`disable...()`] supporting method on properties and actions to make a property/action disabled according to some imperative rule
=== Do it!
* use the xref:rgant.adoc#_rgant-Property_regexPattern[`@Property(regexPattern=...)`] annotation to specify a regex pattern for properties, and use xref:rgant.adoc#_rgant-Parameter_regexPattern[`@Parameter(regexPattern=...)`] for parameters
* use the xref:rgant.adoc#_rgant-Property_maxLength[`@Property(maxLength=...)`] annotation to indicate a maxmum number of characters, and xref:rgant.adoc#_rgant-Parameter_maxLength[`@Parameter(maxLength=...)`] for parameters
-* Use the xref:rgcms.adoc#_rgcms_methods_prefixes_manpage-validate[`validate...()`] supporting method on properties or action parameter
+* Use the xref:rgcms.adoc#_rgcms_methods_prefixes_validate[`validate...()`] supporting method on properties or action parameter
* optional: for any data type:
** use the xref:rgant.adoc#_rgant-Property_mustSatisfy[`Property(mustSatisfy=...)`] and xref:rgant.adoc#_rgant-Parameter_mustSatisfy[`Parameter(mustSatisfy=...)`] annotations to specify arbitrary constraints on properties and parameters
@@ -602,7 +602,7 @@ In most cases users can accomplish the business operations they need by invoking
Also, if using Apache Isis' REST API then the REST client may be a native application (on a smartphone or tablet, say) that is deployed by a third party. In these cases exposing the entities directly would be inadvisable because a refactoring of the domain entity would change the REST API and probably break that REST client.
-To support these use cases, Apache Isis therefore allows you to write a view model, either by annotating the class with xref:rgant.adoc#_rgant-ViewModel[`@ViewModel`] or (for more control) by implementing the xref:rgcms.adoc#_rgcms_classes_super_manpage-AbstractViewModel[`ViewModel`] interface.
+To support these use cases, Apache Isis therefore allows you to write a view model, either by annotating the class with xref:rgant.adoc#_rgant-ViewModel[`@ViewModel`] or (for more control) by implementing the xref:rgcms.adoc#_rgcms_classes_super_AbstractViewModel[`ViewModel`] interface.
* build a view model summarizing the state of the app (a "dashboard")
* write a new `@HomePage` domain service action returning this dashboard viewmodel (and remove the `@HomePage` annotation from any other domain service if present)
http://git-wip-us.apache.org/repos/asf/isis/blob/43fc7bc1/adocs/documentation/src/main/asciidoc/guides/_ug_core-concepts_principles_apache-isis-vs_cqrs.adoc
----------------------------------------------------------------------
diff --git a/adocs/documentation/src/main/asciidoc/guides/_ug_core-concepts_principles_apache-isis-vs_cqrs.adoc b/adocs/documentation/src/main/asciidoc/guides/_ug_core-concepts_principles_apache-isis-vs_cqrs.adoc
index 5f5b82f..0a59241 100644
--- a/adocs/documentation/src/main/asciidoc/guides/_ug_core-concepts_principles_apache-isis-vs_cqrs.adoc
+++ b/adocs/documentation/src/main/asciidoc/guides/_ug_core-concepts_principles_apache-isis-vs_cqrs.adoc
@@ -17,7 +17,7 @@ Comparing CQRS to Apache Isis, the most obvious difference is that Apache Isis d
There are other reasons though why a separate read model might make sense, such as to precompute particular queries, or against denormalized data. In these cases Apache Isis can often provide a reasonable alternative, namely to map domain entities against RDBMS views, either materialized views or dynamic. In such cases there is still only a single physical datastore, and so transactional integrity is retained.
-Or, the CQRS architecture can be more fully implemented with Apache Isis by introducing a separate read model, synchronized using the xref:rgsvc.adoc#_rgsvc-api_PublishingService[`PublishingService`], or using xref:rgcms.adoc#_rgcms_classes_super_manpage-AbstractSubscriber[subscribers] on the xref:rgsvc.adoc#_rgsvc-api_EventBusService[`EventBusService`]. One can then use xref:ugbtb.adoc#_ugbtb_more-advanced_view-models[view models] to surface the data in the external read datastore.
+Or, the CQRS architecture can be more fully implemented with Apache Isis by introducing a separate read model, synchronized using the xref:rgsvc.adoc#_rgsvc-api_PublishingService[`PublishingService`], or using xref:rgcms.adoc#_rgcms_classes_super_AbstractSubscriber[subscribers] on the xref:rgsvc.adoc#_rgsvc-api_EventBusService[`EventBusService`]. One can then use xref:ugbtb.adoc#_ugbtb_more-advanced_view-models[view models] to surface the data in the external read datastore.
With respect to commands, Apache Isis does of course support the xref:rgsvc.adoc#_rgsvc-spi_CommandService[`CommandService`] which allows each business action to be reified into a `Command`. However, names are misleading here: Apache Isis' commands are relatively passive, merely recording the intent of the user to invoke some operation. In a CQRS architecture, though, commands take a more active role, locating and acting upon the domain objects. More significantly, in CQRS each command has its own class, such as `PlaceOrderCommand`, instantiated by the client and then executed. With Apache Isis, though, the end-user merely invokes the `placeOrder(...)` action upon the domain object; the framework itself creates the `Command` as a side-effect of this.
http://git-wip-us.apache.org/repos/asf/isis/blob/43fc7bc1/adocs/documentation/src/main/asciidoc/guides/_ug_core-concepts_principles_apache-isis-vs_event-sourcing.adoc
----------------------------------------------------------------------
diff --git a/adocs/documentation/src/main/asciidoc/guides/_ug_core-concepts_principles_apache-isis-vs_event-sourcing.adoc b/adocs/documentation/src/main/asciidoc/guides/_ug_core-concepts_principles_apache-isis-vs_event-sourcing.adoc
index f9653d8..3e756ee 100644
--- a/adocs/documentation/src/main/asciidoc/guides/_ug_core-concepts_principles_apache-isis-vs_event-sourcing.adoc
+++ b/adocs/documentation/src/main/asciidoc/guides/_ug_core-concepts_principles_apache-isis-vs_event-sourcing.adoc
@@ -14,6 +14,6 @@ Although it might seem counter-intuitive to be able store persistent state in th
When combined with CQRS we see a command that triggers a business operation, and an event that results from it. So, a `PlaceOrderCommand` command can result in an `OrderPlacedEvent` event. A subscriber to this event might then generate a further command to act upon some other system (eg to dispatch the system). Note that the event might be dispatched and consumed in-process or alternatively this might occur out-of-process. If the latter, then the subscriber will operate within a separate transaction, meaning the usual eventual consistency concerns and also compensating actions if a rollback is required. CQRS/event sourcing advocates point out - correctly that this is just how things are in the "real world" too.
-In Apache Isis every business action (and indeed, property and collection) emits domain events through the xref:rgsvc.adoc#_rgsvc-api_EventBusService[`EventBusService`] , and can optionally also be published through the xref:rgsvc.adoc#_rgsvc-spi_PublishingService[`PublishingService`]. The former are dispatched and consumed in-process and within the same transaction, and for this reason the xref:rgcms.adoc#_rgcms_classes_super_manpage-AbstractSubscriber[subscribers] can also veto the events. The latter are intended for out-of-process consumption; the (non-ASF) http://github.com/isisaddons/isis-module-publishing[Isis addons' publishing] and http://github.com/isisaddons/isis-module-publishmq[Isis addons' publishmq] modules provide implementations for dispatching either through a RDBMS database table, or directly through to an link:http://camel.apache.org[ActiveMQ] message queue (eg wired up to link:http://camel.apache.org[Apache Camel] event bus).
+In Apache Isis every business action (and indeed, property and collection) emits domain events through the xref:rgsvc.adoc#_rgsvc-api_EventBusService[`EventBusService`] , and can optionally also be published through the xref:rgsvc.adoc#_rgsvc-spi_PublishingService[`PublishingService`]. The former are dispatched and consumed in-process and within the same transaction, and for this reason the xref:rgcms.adoc#_rgcms_classes_super_AbstractSubscriber[subscribers] can also veto the events. The latter are intended for out-of-process consumption; the (non-ASF) http://github.com/isisaddons/isis-module-publishing[Isis addons' publishing] and http://github.com/isisaddons/isis-module-publishmq[Isis addons' publishmq] modules provide implementations for dispatching either through a RDBMS database table, or directly through to an link:http://camel.apache.org[ActiveMQ] message queue (eg wired up to link:http://camel.apache.org[Apache Camel] event bus).
http://git-wip-us.apache.org/repos/asf/isis/blob/43fc7bc1/adocs/documentation/src/main/asciidoc/guides/_ug_faqs_restful-image-property.adoc
----------------------------------------------------------------------
diff --git a/adocs/documentation/src/main/asciidoc/guides/_ug_faqs_restful-image-property.adoc b/adocs/documentation/src/main/asciidoc/guides/_ug_faqs_restful-image-property.adoc
index 12ddcf2..d025e8a 100644
--- a/adocs/documentation/src/main/asciidoc/guides/_ug_faqs_restful-image-property.adoc
+++ b/adocs/documentation/src/main/asciidoc/guides/_ug_faqs_restful-image-property.adoc
@@ -15,6 +15,6 @@ This is in the form:
(filename):(mime type):(binary data in base64)
-This is basically the xref:rgcms.adoc#_rgcms_classes_value-types_manpage-Blob[`Blob`] value type, in string form.
+This is basically the xref:rgcms.adoc#_rgcms_classes_value-types_Blob[`Blob`] value type, in string form.
To use, split the parts then format the mime type and base64 data correctly before using as source in an `<img>` tag.
http://git-wip-us.apache.org/repos/asf/isis/blob/43fc7bc1/adocs/documentation/src/main/asciidoc/guides/_ug_how-tos_business-rules.adoc
----------------------------------------------------------------------
diff --git a/adocs/documentation/src/main/asciidoc/guides/_ug_how-tos_business-rules.adoc b/adocs/documentation/src/main/asciidoc/guides/_ug_how-tos_business-rules.adoc
index aeea83e..71794c6 100644
--- a/adocs/documentation/src/main/asciidoc/guides/_ug_how-tos_business-rules.adoc
+++ b/adocs/documentation/src/main/asciidoc/guides/_ug_how-tos_business-rules.adoc
@@ -10,7 +10,7 @@ NOTE: TODO
== Visibility ("see it")
-NOTE: TODO - xref:rgcms.adoc#_rgcms_methods_prefixes_manpage-hide[`hide...()`]
+NOTE: TODO - xref:rgcms.adoc#_rgcms_methods_prefixes_hide[`hide...()`]
### Hide a Property
@@ -27,7 +27,7 @@ NOTE: TODO - xref:rgcms.adoc#_rgcms_methods_prefixes_manpage-hide[`hide...()`]
== Usability ("use it")
-NOTE: TODO - xref:rgcms.adoc#_rgcms_methods_prefixes_manpage-disable[`disable...()`]
+NOTE: TODO - xref:rgcms.adoc#_rgcms_methods_prefixes_disable[`disable...()`]
### Disable a Property
@@ -53,7 +53,7 @@ In the Wicket viewer this means disabling the edit button.
== Validity ("do it")
-NOTE: TODO - xref:rgcms.adoc#_rgcms_methods_prefixes_manpage-validate[`validate...()`], xref:rgcms.adoc#_rgcms_methods_prefixes_manpage-validateAddTo[`validateAddTo...()`], xref:rgcms.adoc#_rgcms_methods_prefixes_manpage-validateRemoveFrom[`validateRemoveFrom...()`] and xref:rgcms.adoc#_rgcms_methods_reserved_manpage-validate[`validate()`]
+NOTE: TODO - xref:rgcms.adoc#_rgcms_methods_prefixes_validate[`validate...()`], xref:rgcms.adoc#_rgcms_methods_prefixes_validateAddTo[`validateAddTo...()`], xref:rgcms.adoc#_rgcms_methods_prefixes_validateRemoveFrom[`validateRemoveFrom...()`] and xref:rgcms.adoc#_rgcms_methods_reserved_validate[`validate()`]
### Validate (change to) a Property
http://git-wip-us.apache.org/repos/asf/isis/blob/43fc7bc1/adocs/documentation/src/main/asciidoc/guides/_ug_how-tos_derived-members.adoc
----------------------------------------------------------------------
diff --git a/adocs/documentation/src/main/asciidoc/guides/_ug_how-tos_derived-members.adoc b/adocs/documentation/src/main/asciidoc/guides/_ug_how-tos_derived-members.adoc
index abe2ae8..dea0b06 100644
--- a/adocs/documentation/src/main/asciidoc/guides/_ug_how-tos_derived-members.adoc
+++ b/adocs/documentation/src/main/asciidoc/guides/_ug_how-tos_derived-members.adoc
@@ -39,10 +39,10 @@ public class Customer {
== Trigger on property change
-NOTE: TODO - xref:rgcms.adoc#_rgcms_methods_prefixes_manpage-modify[`modify...()`], xref:rgcms.adoc#_rgcms_methods_prefixes_manpage-clear[`clear...()`]
+NOTE: TODO - xref:rgcms.adoc#_rgcms_methods_prefixes_modify[`modify...()`], xref:rgcms.adoc#_rgcms_methods_prefixes_clear[`clear...()`]
== Trigger on collection change
-NOTE: TODO - xref:rgcms.adoc#_rgcms_methods_prefixes_manpage-addTo[`addTo...()`], xref:rgcms.adoc#_rgcms_methods_prefixes_manpage-removeFrom[`removeFrom...()`]
+NOTE: TODO - xref:rgcms.adoc#_rgcms_methods_prefixes_addTo[`addTo...()`], xref:rgcms.adoc#_rgcms_methods_prefixes_removeFrom[`removeFrom...()`]
http://git-wip-us.apache.org/repos/asf/isis/blob/43fc7bc1/adocs/documentation/src/main/asciidoc/guides/_ug_how-tos_domain-services.adoc
----------------------------------------------------------------------
diff --git a/adocs/documentation/src/main/asciidoc/guides/_ug_how-tos_domain-services.adoc b/adocs/documentation/src/main/asciidoc/guides/_ug_how-tos_domain-services.adoc
index 16c131a..eea9859 100644
--- a/adocs/documentation/src/main/asciidoc/guides/_ug_how-tos_domain-services.adoc
+++ b/adocs/documentation/src/main/asciidoc/guides/_ug_how-tos_domain-services.adoc
@@ -309,5 +309,5 @@ Shutdown is similar; the framework will call any method annotated with xref:rgan
== The getId() method
-Optionally, a service may provide a xref:rgcms.adoc#_rgcms_methods_reserved_manpage-getId[`getId()`] method. This method returns a logical identifier for a service, independent of its implementation.
+Optionally, a service may provide a xref:rgcms.adoc#_rgcms_methods_reserved_getId[`getId()`] method. This method returns a logical identifier for a service, independent of its implementation.
http://git-wip-us.apache.org/repos/asf/isis/blob/43fc7bc1/adocs/documentation/src/main/asciidoc/guides/_ug_how-tos_drop-downs-and-defaults.adoc
----------------------------------------------------------------------
diff --git a/adocs/documentation/src/main/asciidoc/guides/_ug_how-tos_drop-downs-and-defaults.adoc b/adocs/documentation/src/main/asciidoc/guides/_ug_how-tos_drop-downs-and-defaults.adoc
index c6bc242..94891a7 100644
--- a/adocs/documentation/src/main/asciidoc/guides/_ug_how-tos_drop-downs-and-defaults.adoc
+++ b/adocs/documentation/src/main/asciidoc/guides/_ug_how-tos_drop-downs-and-defaults.adoc
@@ -13,15 +13,15 @@ NOTE: TODO
### Choices for Property
-NOTE: TODO - xref:rgcms.adoc#_rgcms_methods_prefixes_manpage-choices[`choices...()`]
+NOTE: TODO - xref:rgcms.adoc#_rgcms_methods_prefixes_choices[`choices...()`]
### Auto-complete for property
-NOTE: TODO - xref:rgcms.adoc#_rgcms_methods_prefixes_manpage-autoComplete[`autoComplete...()`]
+NOTE: TODO - xref:rgcms.adoc#_rgcms_methods_prefixes_autoComplete[`autoComplete...()`]
### Default for property
-NOTE: TODO - xref:rgcms.adoc#_rgcms_methods_prefixes_manpage-default[`default...()`]
+NOTE: TODO - xref:rgcms.adoc#_rgcms_methods_prefixes_default[`default...()`]
@@ -32,19 +32,19 @@ NOTE: TODO
### Choices for action parameter
-NOTE: TODO - xref:rgcms.adoc#_rgcms_methods_prefixes_manpage-choices[`choices...()`]
+NOTE: TODO - xref:rgcms.adoc#_rgcms_methods_prefixes_choices[`choices...()`]
### Dependent choices for action params
-NOTE: TODO - xref:rgcms.adoc#_rgcms_methods_prefixes_manpage-choices[`choices...()`]
+NOTE: TODO - xref:rgcms.adoc#_rgcms_methods_prefixes_choices[`choices...()`]
### Auto-complete for action param
-NOTE: TODO - xref:rgcms.adoc#_rgcms_methods_prefixes_manpage-autoComplete[`autoComplete...()`]
+NOTE: TODO - xref:rgcms.adoc#_rgcms_methods_prefixes_autoComplete[`autoComplete...()`]
### Default for action param
-NOTE: TODO - xref:rgcms.adoc#_rgcms_methods_prefixes_manpage-default[`default...()`]
+NOTE: TODO - xref:rgcms.adoc#_rgcms_methods_prefixes_default[`default...()`]
http://git-wip-us.apache.org/repos/asf/isis/blob/43fc7bc1/adocs/documentation/src/main/asciidoc/guides/_ug_how-tos_entity-relationships_managed-1-to-m-bidirectional-relationships.adoc
----------------------------------------------------------------------
diff --git a/adocs/documentation/src/main/asciidoc/guides/_ug_how-tos_entity-relationships_managed-1-to-m-bidirectional-relationships.adoc b/adocs/documentation/src/main/asciidoc/guides/_ug_how-tos_entity-relationships_managed-1-to-m-bidirectional-relationships.adoc
index f7ec25f..0b1d64a 100644
--- a/adocs/documentation/src/main/asciidoc/guides/_ug_how-tos_entity-relationships_managed-1-to-m-bidirectional-relationships.adoc
+++ b/adocs/documentation/src/main/asciidoc/guides/_ug_how-tos_entity-relationships_managed-1-to-m-bidirectional-relationships.adoc
@@ -8,7 +8,7 @@
When an object is added to a 1:m bidirectional relationship, the child object must refer to the parent and the child must be added to the parent's children collection.
-If there were no database involved then we would have recommended that you use the link:http://www.two-sdg.demon.co.uk/curbralan/papers/MutualRegistration.pdf[mutual registration] pattern to ensure that both the parent and child are updated correctly. (The xref:rgcms.adoc#_rgcms_methods_prefixes_manpage-modify[`modify...()`] and xref:rgcms.adoc#_rgcms_methods_prefixes_manpage-clear[`clear...()`] supporting methods were introduced in the framework primarily to help support implement the mutual registration pattern.
+If there were no database involved then we would have recommended that you use the link:http://www.two-sdg.demon.co.uk/curbralan/papers/MutualRegistration.pdf[mutual registration] pattern to ensure that both the parent and child are updated correctly. (The xref:rgcms.adoc#_rgcms_methods_prefixes_modify[`modify...()`] and xref:rgcms.adoc#_rgcms_methods_prefixes_clear[`clear...()`] supporting methods were introduced in the framework primarily to help support implement the mutual registration pattern.
However, in a relational database, these two operations in the domain object model correspond simply to updating the foreign key of the child table to reference the parent's primary key.
http://git-wip-us.apache.org/repos/asf/isis/blob/43fc7bc1/adocs/documentation/src/main/asciidoc/guides/_ug_how-tos_ui-hints_object-titles-and-icons.adoc
----------------------------------------------------------------------
diff --git a/adocs/documentation/src/main/asciidoc/guides/_ug_how-tos_ui-hints_object-titles-and-icons.adoc b/adocs/documentation/src/main/asciidoc/guides/_ug_how-tos_ui-hints_object-titles-and-icons.adoc
index 2e4274d..1ec22ed 100644
--- a/adocs/documentation/src/main/asciidoc/guides/_ug_how-tos_ui-hints_object-titles-and-icons.adoc
+++ b/adocs/documentation/src/main/asciidoc/guides/_ug_how-tos_ui-hints_object-titles-and-icons.adoc
@@ -75,7 +75,7 @@ Titles can sometimes get be long and therefore rather cumbersome in "parented" t
=== Imperative style
-NOTE: TODO - see xref:rgcms.adoc#_rgcms_methods_reserved_manpage-title[`title()`]
+NOTE: TODO - see xref:rgcms.adoc#_rgcms_methods_reserved_title[`title()`]
@@ -84,7 +84,7 @@ NOTE: TODO - see xref:rgcms.adoc#_rgcms_methods_reserved_manpage-title[`title()`
The icon is often the same for all instances of a particular class, but it's also possible for an individual instance to return a custom icon. This could represent the state of that object (eg a shipped order, say, or overdue library book).
-NOTE: TODO - xref:rgcms.adoc#_rgcms_methods_reserved_manpage-iconName[`iconName()`], xref:rgant.adoc#_rgant-DomainObjectLayout_cssClassFa[`@DomainObjectLayout#cssClassFa()`]
+NOTE: TODO - xref:rgcms.adoc#_rgcms_methods_reserved_iconName[`iconName()`], xref:rgant.adoc#_rgant-DomainObjectLayout_cssClassFa[`@DomainObjectLayout#cssClassFa()`]
@@ -92,6 +92,6 @@ NOTE: TODO - xref:rgcms.adoc#_rgcms_methods_reserved_manpage-iconName[`iconName(
== Object CSS Styling
-It is also possible for an object to return a xref:rgcms.adoc#_rgcms_methods_reserved_manpage-cssClass[CSS class]. In conjunction with xref:ugvw.adoc#_ugvw_customisation_tweaking-css-classes[customized CSS] this can be used to apply arbitrary styling; for example each object could be rendered in a page with a different background colour.
+It is also possible for an object to return a xref:rgcms.adoc#_rgcms_methods_reserved_cssClass[CSS class]. In conjunction with xref:ugvw.adoc#_ugvw_customisation_tweaking-css-classes[customized CSS] this can be used to apply arbitrary styling; for example each object could be rendered in a page with a different background colour.
-NOTE: TODO - xref:rgcms.adoc#_rgcms_methods_reserved_manpage-cssClass[`cssClass()`], xref:rgant.adoc#_rgant-DomainObjectLayout_cssClass[`@DomainObjectLayout#cssClass()`] xref:rgant.adoc#_rgant-ActionLayout_cssClass[`@ActionLayout#cssClass()`], xref:rgant.adoc#_rgant-PropertyLayout_cssClass[`@PropertyLayout#cssClass()`], xref:rgant.adoc#_rgant-CollectionLayout_cssClass[`@CollectionLayout#cssClass()`]
+NOTE: TODO - xref:rgcms.adoc#_rgcms_methods_reserved_cssClass[`cssClass()`], xref:rgant.adoc#_rgant-DomainObjectLayout_cssClass[`@DomainObjectLayout#cssClass()`] xref:rgant.adoc#_rgant-ActionLayout_cssClass[`@ActionLayout#cssClass()`], xref:rgant.adoc#_rgant-PropertyLayout_cssClass[`@PropertyLayout#cssClass()`], xref:rgant.adoc#_rgant-CollectionLayout_cssClass[`@CollectionLayout#cssClass()`]
http://git-wip-us.apache.org/repos/asf/isis/blob/43fc7bc1/adocs/documentation/src/main/asciidoc/guides/_ug_how-tos_ui_are-you-sure.adoc
----------------------------------------------------------------------
diff --git a/adocs/documentation/src/main/asciidoc/guides/_ug_how-tos_ui_are-you-sure.adoc b/adocs/documentation/src/main/asciidoc/guides/_ug_how-tos_ui_are-you-sure.adoc
index 93d9fe8..2ce9903 100644
--- a/adocs/documentation/src/main/asciidoc/guides/_ug_how-tos_ui_are-you-sure.adoc
+++ b/adocs/documentation/src/main/asciidoc/guides/_ug_how-tos_ui_are-you-sure.adoc
@@ -73,4 +73,4 @@ public String validateDelete(boolean areYouSure) {
<1> invalid to return `this` (cannot render a deleted object)
Note that the action itself does not use the boolean parameter, it is only
-used by the supporting xref:rgcms.adoc#_rgcms_methods_prefixes_manpage-validate[`validate...()`] method.
\ No newline at end of file
+used by the supporting xref:rgcms.adoc#_rgcms_methods_prefixes_validate[`validate...()`] method.
\ No newline at end of file
http://git-wip-us.apache.org/repos/asf/isis/blob/43fc7bc1/adocs/documentation/src/main/asciidoc/guides/_ugbtb_deployment_cmd-line.adoc
----------------------------------------------------------------------
diff --git a/adocs/documentation/src/main/asciidoc/guides/_ugbtb_deployment_cmd-line.adoc b/adocs/documentation/src/main/asciidoc/guides/_ugbtb_deployment_cmd-line.adoc
index 7bc9c9c..2a26746 100644
--- a/adocs/documentation/src/main/asciidoc/guides/_ugbtb_deployment_cmd-line.adoc
+++ b/adocs/documentation/src/main/asciidoc/guides/_ugbtb_deployment_cmd-line.adoc
@@ -29,7 +29,7 @@ The class also supports a number of command line arguments:
|`-m`
|`--manifest`
|FQCN
-|Fully qualified class name of the xref:rgcms.adoc#_rgcms_classes_super_manpage-AppManifest[`AppManifest`] to use to bootstrap the system. +
+|Fully qualified class name of the xref:rgcms.adoc#_rgcms_classes_super_AppManifest[`AppManifest`] to use to bootstrap the system. +
This flag sets/overrides the `isis.appManifest` configuration property to the specified class name.
@@ -37,7 +37,7 @@ This flag sets/overrides the `isis.appManifest` configuration property to the sp
|`-f`
|`--fixture`
|FQCN
-|Fully qualified class name of the fixture (extending xref:rgcms.adoc#_rgcms_classes_super_manpage-FixtureScript[`FixtureScript`]) to be run to setup data. +
+|Fully qualified class name of the fixture (extending xref:rgcms.adoc#_rgcms_classes_super_FixtureScript[`FixtureScript`]) to be run to setup data. +
This flag sets/overrides the `isis.fixtures` configuration property to the specified class name, and also sets the `isis.persistor.datanucleus.install-fixtures` configuration property to `true` to instruct the JDO/DataNucleus objectstore to actually load in the fixtures. +
http://git-wip-us.apache.org/repos/asf/isis/blob/43fc7bc1/adocs/documentation/src/main/asciidoc/guides/_ugbtb_more-advanced_decoupling_mixins.adoc
----------------------------------------------------------------------
diff --git a/adocs/documentation/src/main/asciidoc/guides/_ugbtb_more-advanced_decoupling_mixins.adoc b/adocs/documentation/src/main/asciidoc/guides/_ugbtb_more-advanced_decoupling_mixins.adoc
index ea72d13..32b734f 100644
--- a/adocs/documentation/src/main/asciidoc/guides/_ugbtb_more-advanced_decoupling_mixins.adoc
+++ b/adocs/documentation/src/main/asciidoc/guides/_ugbtb_more-advanced_decoupling_mixins.adoc
@@ -144,7 +144,7 @@ DocumentHolder_documents mixin = container.mixin(DocumentHolder_documents.class,
----
The xref:ugtst.adoc#_ugtst_integ-test-support_bootstrapping_IntegrationTestAbstract[`IntegrationTestAbstract`] and
-xref:rgcms.adoc#_rgcms_classes_super_manpage-FixtureScript[`FixtureScript`] classes both provide a `mixin(...)` convenience
+xref:rgcms.adoc#_rgcms_classes_super_FixtureScript[`FixtureScript`] classes both provide a `mixin(...)` convenience
method.
http://git-wip-us.apache.org/repos/asf/isis/blob/43fc7bc1/adocs/documentation/src/main/asciidoc/guides/_ugbtb_more-advanced_decoupling_pushing-changes.adoc
----------------------------------------------------------------------
diff --git a/adocs/documentation/src/main/asciidoc/guides/_ugbtb_more-advanced_decoupling_pushing-changes.adoc b/adocs/documentation/src/main/asciidoc/guides/_ugbtb_more-advanced_decoupling_pushing-changes.adoc
index b357ec9..7cd2f5d 100644
--- a/adocs/documentation/src/main/asciidoc/guides/_ugbtb_more-advanced_decoupling_pushing-changes.adoc
+++ b/adocs/documentation/src/main/asciidoc/guides/_ugbtb_more-advanced_decoupling_pushing-changes.adoc
@@ -134,7 +134,7 @@ public class Department {
--
<1> maintain a count of the number of male ...
<2> ... and female employees (getters and setters omitted)
-<3> the xref:rgcms.adoc#_rgcms_methods_prefixes_manpage-addTo[`addTo...()`] method increments the derived properties
-<4> the xref:rgcms.adoc#_rgcms_methods_prefixes_manpage-removeFrom[`removeFrom...()`] method similarly decrements the derived properties
+<3> the xref:rgcms.adoc#_rgcms_methods_prefixes_addTo[`addTo...()`] method increments the derived properties
+<4> the xref:rgcms.adoc#_rgcms_methods_prefixes_removeFrom[`removeFrom...()`] method similarly decrements the derived properties
http://git-wip-us.apache.org/repos/asf/isis/blob/43fc7bc1/adocs/documentation/src/main/asciidoc/guides/_ugbtb_more-advanced_i18n.adoc
----------------------------------------------------------------------
diff --git a/adocs/documentation/src/main/asciidoc/guides/_ugbtb_more-advanced_i18n.adoc b/adocs/documentation/src/main/asciidoc/guides/_ugbtb_more-advanced_i18n.adoc
index fe40119..e119bac 100644
--- a/adocs/documentation/src/main/asciidoc/guides/_ugbtb_more-advanced_i18n.adoc
+++ b/adocs/documentation/src/main/asciidoc/guides/_ugbtb_more-advanced_i18n.adoc
@@ -7,7 +7,7 @@
Apache Isis' support for i18n allows every element of the domain model (the class names, property names, action names, parameter names and so forth) to be translated.
-It also supports translations of messages raised imperatively, by which we mean as the result of a call to `title()` to obtain an object's title, or messages resulting from any business rule violations (eg xref:rgcms.adoc#_rgcms_methods_prefixes_manpage-disable[`disable...()`] or xref:rgcms.adoc#_rgcms_methods_prefixes_manpage-validate[`validate...()`], and so on.
+It also supports translations of messages raised imperatively, by which we mean as the result of a call to `title()` to obtain an object's title, or messages resulting from any business rule violations (eg xref:rgcms.adoc#_rgcms_methods_prefixes_disable[`disable...()`] or xref:rgcms.adoc#_rgcms_methods_prefixes_validate[`validate...()`], and so on.
Isis does not translate the values of your domain objects, though. So, if you have a domain concept such as `Country` whose name is intended to be localized according to the current user, you will need to model
http://git-wip-us.apache.org/repos/asf/isis/blob/43fc7bc1/adocs/documentation/src/main/asciidoc/guides/_ugbtb_more-advanced_view-models_programming-model.adoc
----------------------------------------------------------------------
diff --git a/adocs/documentation/src/main/asciidoc/guides/_ugbtb_more-advanced_view-models_programming-model.adoc b/adocs/documentation/src/main/asciidoc/guides/_ugbtb_more-advanced_view-models_programming-model.adoc
index 9f8bd86..e7305b4 100644
--- a/adocs/documentation/src/main/asciidoc/guides/_ugbtb_more-advanced_view-models_programming-model.adoc
+++ b/adocs/documentation/src/main/asciidoc/guides/_ugbtb_more-advanced_view-models_programming-model.adoc
@@ -66,7 +66,7 @@ public class ExcelUploadManager implements ViewModel {
public String viewModelMemento() { ... }
public void viewModelInit(String memento) { ... }
}
-|Implement xref:rgcms.adoc#_rgcms_classes_super_manpage-ViewModel[`ViewModel`] interface. The memento is as defined by the
+|Implement xref:rgcms.adoc#_rgcms_classes_super_ViewModel[`ViewModel`] interface. The memento is as defined by the
interface's methods: the programmer has full control (but also full responsibility) for the string memento.
|DTO (`1.11.0-SNAPSHOT`)
http://git-wip-us.apache.org/repos/asf/isis/blob/43fc7bc1/adocs/documentation/src/main/asciidoc/guides/_ugtst_aaa.adoc
----------------------------------------------------------------------
diff --git a/adocs/documentation/src/main/asciidoc/guides/_ugtst_aaa.adoc b/adocs/documentation/src/main/asciidoc/guides/_ugtst_aaa.adoc
index 2e89107..e75a29b 100644
--- a/adocs/documentation/src/main/asciidoc/guides/_ugtst_aaa.adoc
+++ b/adocs/documentation/src/main/asciidoc/guides/_ugtst_aaa.adoc
@@ -125,7 +125,7 @@ In the previous section we discussed using given/when/then as a form of organizi
For integration tests though it can be difficult to keep the "given" short; there could be a lot of prerequisite data that needs to exist before you can actually exercise your system. Moreover, however we do set up that data, but we also want to do so in a way that is resilient to the system changing over time.
-The solution that Apache Isis provides is a domain service called xref:rgcms.adoc#_rgcms_classes_super_manpage-FixtureScripts[Fixture Scripts], that defines a pattern and supporting classes to help ensure that the "data setup" for your tests are reusable and maintainable over time.
+The solution that Apache Isis provides is a domain service called xref:rgcms.adoc#_rgcms_classes_super_FixtureScripts[Fixture Scripts], that defines a pattern and supporting classes to help ensure that the "data setup" for your tests are reusable and maintainable over time.
http://git-wip-us.apache.org/repos/asf/isis/blob/43fc7bc1/adocs/documentation/src/main/asciidoc/guides/_ugtst_integ-test-support_typical-usage.adoc
----------------------------------------------------------------------
diff --git a/adocs/documentation/src/main/asciidoc/guides/_ugtst_integ-test-support_typical-usage.adoc b/adocs/documentation/src/main/asciidoc/guides/_ugtst_integ-test-support_typical-usage.adoc
index d75f70c..310a002 100644
--- a/adocs/documentation/src/main/asciidoc/guides/_ugtst_integ-test-support_typical-usage.adoc
+++ b/adocs/documentation/src/main/asciidoc/guides/_ugtst_integ-test-support_typical-usage.adoc
@@ -58,7 +58,7 @@ public class ToDoItemIntegTest extends AbstractToDoIntegTest {
...
}
----
-<1> the xref:rgcms.adoc#_rgcms_classes_super_manpage-FixtureScripts[`FixtureScripts`] domain service is injected, providing us with the ability to run fixture scripts
+<1> the xref:rgcms.adoc#_rgcms_classes_super_FixtureScripts[`FixtureScripts`] domain service is injected, providing us with the ability to run fixture scripts
<2> likewise, an instance of the `ToDoItems` domain service is injected. We'll use this to lookup...
<3> the object under test, held as a field
<4> the fixture script for this test; it deletes all existing todo items (for the current user only) and then recreates them
http://git-wip-us.apache.org/repos/asf/isis/blob/43fc7bc1/adocs/documentation/src/main/asciidoc/guides/_ugtst_unit-test-support_contract-tests.adoc
----------------------------------------------------------------------
diff --git a/adocs/documentation/src/main/asciidoc/guides/_ugtst_unit-test-support_contract-tests.adoc b/adocs/documentation/src/main/asciidoc/guides/_ugtst_unit-test-support_contract-tests.adoc
index 30c4f90..24f7e1e 100644
--- a/adocs/documentation/src/main/asciidoc/guides/_ugtst_unit-test-support_contract-tests.adoc
+++ b/adocs/documentation/src/main/asciidoc/guides/_ugtst_unit-test-support_contract-tests.adoc
@@ -41,7 +41,7 @@ If using DataNucleus against an RDBMS (as you probably are) then we strongly rec
* second, `SortedSet` is preferable to `Set` because then the order is well-defined and predictable (to an end user, to the programmer). +
+
-The xref:rgcms.adoc#_rgcms_classes_utility_manpage-ObjectContracts[`ObjectContracts`] utility class substantially simplifies the task of implementing `Comparable` in your domain classes.
+The xref:rgcms.adoc#_rgcms_classes_utility_ObjectContracts[`ObjectContracts`] utility class substantially simplifies the task of implementing `Comparable` in your domain classes.
* third, if the relationship is bidirectional then JDO/Objectstore will automatically maintain the relationship.
http://git-wip-us.apache.org/repos/asf/isis/blob/43fc7bc1/adocs/documentation/src/main/asciidoc/guides/_ugvw_features_blob-attachments.adoc
----------------------------------------------------------------------
diff --git a/adocs/documentation/src/main/asciidoc/guides/_ugvw_features_blob-attachments.adoc b/adocs/documentation/src/main/asciidoc/guides/_ugvw_features_blob-attachments.adoc
index f150240..ffd425f 100644
--- a/adocs/documentation/src/main/asciidoc/guides/_ugvw_features_blob-attachments.adoc
+++ b/adocs/documentation/src/main/asciidoc/guides/_ugvw_features_blob-attachments.adoc
@@ -6,7 +6,7 @@
-The Isis application library provides the xref:rgcms.adoc#_rgcms_classes_value-types_manpage-Blob[Blob] value type (binary large objects) and also the xref:rgcms.adoc#_rgcms_classes_value-types_manpage-Clob[Clob]
+The Isis application library provides the xref:rgcms.adoc#_rgcms_classes_value-types_Blob[Blob] value type (binary large objects) and also the xref:rgcms.adoc#_rgcms_classes_value-types_Clob[Clob]
value type (character large object), each of which also includes metadata about the data (specifically the filename and mime type).
A class can define a property using either of these types, for example:
http://git-wip-us.apache.org/repos/asf/isis/blob/43fc7bc1/adocs/documentation/src/main/asciidoc/guides/rg.adoc
----------------------------------------------------------------------
diff --git a/adocs/documentation/src/main/asciidoc/guides/rg.adoc b/adocs/documentation/src/main/asciidoc/guides/rg.adoc
deleted file mode 100644
index 0951d3b..0000000
--- a/adocs/documentation/src/main/asciidoc/guides/rg.adoc
+++ /dev/null
@@ -1,27 +0,0 @@
-[[rg]]
-= Classes, Methods and Schema
-:Notice: Licensed to the Apache Software Foundation (ASF) under one or more contributor license agreements. See the NOTICE file distributed with this work for additional information regarding copyright ownership. The ASF licenses this file to you under the Apache License, Version 2.0 (the "License"); you may not use this file except in compliance with the License. You may obtain a copy of the License at. http://www.apache.org/licenses/LICENSE-2.0 . Unless required by applicable law or agreed to in writing, software distributed under the License is distributed on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the License for the specific language governing permissions and limitations under the License.
-:_basedir: ../
-:_imagesdir: images/
-:numbered:
-
-
-[[_rg]]
-= Classes, Methods and Schema
-
-This reference guide lists and describes various elements of the the Apache Isis Programming Model, specifically
-reserved and prefix xref:rgcms.adoc#_rgcms_methods[methods] (such as `title()` and `validate...()`) and various utility and
-supporting xref:rgcms.adoc#_rgcms_classes[classes].
-
-It also describes the xref:rgcms.adoc#_rgcms_schema[XSD schema] defined by Apache Isis. One use case is for the
-JAXB serialization of view models (`1.11.0-SNAPSHOT`).
-
-
-This reference guide does _not_ describe how to actually build an Apache Isis application; for that see the *xref:ug.adoc#_ug[Users' Guide]*. The reference guide also doesn't explain how to setup your development environment; for that see the *xref:cg.adoc#_cg[Contributors' Guide]*.
-
-
-
-
-include::_rgcms_methods.adoc[leveloffset=+1]
-include::_rgcms_classes.adoc[leveloffset=+1]
-include::_rgcms_schema.adoc[leveloffset=+1]
http://git-wip-us.apache.org/repos/asf/isis/blob/43fc7bc1/adocs/documentation/src/main/asciidoc/guides/rgcms.adoc
----------------------------------------------------------------------
diff --git a/adocs/documentation/src/main/asciidoc/guides/rgcms.adoc b/adocs/documentation/src/main/asciidoc/guides/rgcms.adoc
new file mode 100644
index 0000000..0951d3b
--- /dev/null
+++ b/adocs/documentation/src/main/asciidoc/guides/rgcms.adoc
@@ -0,0 +1,27 @@
+[[rg]]
+= Classes, Methods and Schema
+:Notice: Licensed to the Apache Software Foundation (ASF) under one or more contributor license agreements. See the NOTICE file distributed with this work for additional information regarding copyright ownership. The ASF licenses this file to you under the Apache License, Version 2.0 (the "License"); you may not use this file except in compliance with the License. You may obtain a copy of the License at. http://www.apache.org/licenses/LICENSE-2.0 . Unless required by applicable law or agreed to in writing, software distributed under the License is distributed on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the License for the specific language governing permissions and limitations under the License.
+:_basedir: ../
+:_imagesdir: images/
+:numbered:
+
+
+[[_rg]]
+= Classes, Methods and Schema
+
+This reference guide lists and describes various elements of the the Apache Isis Programming Model, specifically
+reserved and prefix xref:rgcms.adoc#_rgcms_methods[methods] (such as `title()` and `validate...()`) and various utility and
+supporting xref:rgcms.adoc#_rgcms_classes[classes].
+
+It also describes the xref:rgcms.adoc#_rgcms_schema[XSD schema] defined by Apache Isis. One use case is for the
+JAXB serialization of view models (`1.11.0-SNAPSHOT`).
+
+
+This reference guide does _not_ describe how to actually build an Apache Isis application; for that see the *xref:ug.adoc#_ug[Users' Guide]*. The reference guide also doesn't explain how to setup your development environment; for that see the *xref:cg.adoc#_cg[Contributors' Guide]*.
+
+
+
+
+include::_rgcms_methods.adoc[leveloffset=+1]
+include::_rgcms_classes.adoc[leveloffset=+1]
+include::_rgcms_schema.adoc[leveloffset=+1]