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 2019/09/24 07:10:50 UTC
[isis] 04/07: ISIS-2062: global search-n-replace for
http://platform.incode.org -> https://...
This is an automated email from the ASF dual-hosted git repository.
danhaywood pushed a commit to branch v2
in repository https://gitbox.apache.org/repos/asf/isis.git
commit 09b5171c0b6d1f8c8ad324f96c5ce9321f830c31
Author: danhaywood <da...@haywood-associates.co.uk>
AuthorDate: Mon Sep 23 22:49:36 2019 +0100
ISIS-2062: global search-n-replace for http://platform.incode.org -> https://...
---
README.adoc | 14 ++++++-------
.../modules/ROOT/pages/mn-1.12.0-to-1.13.0.adoc | 4 ++--
.../modules/ROOT/pages/mn-1.14.0-to-1.15.0.adoc | 2 +-
.../modules/ROOT/pages/mn-1.15.0-to-1.16.0.adoc | 2 +-
...0-to-1.9.0_bootstrapping-using-AppManifest.adoc | 2 +-
.../mn-1.8.0-to-1.9.0_upgrading-to-java8.adoc | 2 +-
.../modules/ROOT/pages/mn-1.9.0-to-1.10.0.adoc | 2 +-
.../relnotes/modules/ROOT/pages/rn-1.10.0.adoc | 2 +-
.../relnotes/modules/ROOT/pages/rn-1.12.0.adoc | 2 +-
.../relnotes/modules/ROOT/pages/rn-1.13.0.adoc | 4 ++--
.../relnotes/modules/ROOT/pages/rn-1.13.2.adoc | 4 ++--
.../relnotes/modules/ROOT/pages/rn-1.15.0.adoc | 4 ++--
.../relnotes/modules/ROOT/pages/rn-1.16.1.adoc | 2 +-
.../relnotes/modules/ROOT/pages/rn-1.7.0.adoc | 2 +-
.../ROOT/pages/_partials/_powered-by_commapp.adoc | 4 ++--
.../ROOT/pages/_partials/_powered-by_estatio.adoc | 2 +-
.../_partials/_powered-by_gesconsultor-grc.adoc | 2 +-
.../_partials/_powered-by_transport-planner.adoc | 6 +++---
.../toc/modules/ROOT/pages/downloads/how-to.adoc | 2 +-
.../what-is-apache-isis/common-use-cases.adoc | 2 +-
.../what-is-apache-isis/isis-in-pictures.adoc | 24 +++++++++++-----------
.../what-is-apache-isis/screencasts-older.adoc | 10 ++++-----
.../pages/what-is-apache-isis/screencasts.adoc | 12 +++++------
.../comguide/pages/post-release-successful.adoc | 2 +-
.../how-run-fixtures-on-app-startup.adoc | 2 +-
.../devguide/pages/working-with-many-repos.adoc | 2 +-
.../_adoc-rg/modules/ant/pages/Action/command.adoc | 6 +++---
.../modules/ant/pages/CollectionLayout.adoc | 2 +-
.../ant/pages/CollectionLayout/defaultView.adoc | 2 +-
core/_adoc-rg/modules/ant/pages/Discriminator.adoc | 2 +-
.../modules/ant/pages/DomainObject/objectType.adoc | 2 +-
.../modules/ant/pages/DomainService/nature.adoc | 2 +-
core/_adoc-rg/modules/ant/pages/Inject.adoc | 2 +-
.../modules/ant/pages/Parameter/fileAccept.adoc | 2 +-
.../modules/ant/pages/Parameter/maxLength.adoc | 2 +-
.../modules/ant/pages/ParameterLayout/named.adoc | 2 +-
.../modules/ant/pages/PersistenceCapable.adoc | 2 +-
.../modules/ant/pages/Property/command.adoc | 4 ++--
.../modules/ant/pages/ViewModel/objectType.adoc | 2 +-
.../modules/cfg/pages/configuring-core.adoc | 2 +-
.../pages/classes/AppManifest-bootstrapping.adoc | 4 ++--
.../classes/contributee/HasTransactionId.adoc | 2 +-
.../cms/pages/classes/contributee/HasUserName.adoc | 2 +-
.../pages/classes/super/AbstractSubscriber.adoc | 2 +-
core/_adoc-rg/modules/cms/pages/schema.adoc | 2 +-
.../modules/fis/pages/application-layer.adoc | 2 +-
.../modules/fis/pages/persistence-layer.adoc | 2 +-
.../modules/fis/pages/presentation-layer.adoc | 2 +-
.../modules/svc/pages/application-layer-api.adoc | 2 +-
.../application-layer-api/BackgroundService.adoc | 4 ++--
.../BackgroundService/Quartz.adoc | 2 +-
.../application-layer-api/CommandContext.adoc | 6 +++---
.../CommandExecutorService.adoc | 2 +-
.../application-layer-api/InteractionContext.adoc | 2 +-
.../modules/svc/pages/application-layer-spi.adoc | 2 +-
.../BackgroundCommandService.adoc | 6 +++---
.../application-layer-spi/CommandService.adoc | 6 +++---
.../modules/svc/pages/bootstrapping-spi.adoc | 2 +-
.../modules/svc/pages/core-domain-api.adoc | 2 +-
.../svc/pages/core-domain-api/EventBusService.adoc | 2 +-
.../modules/svc/pages/integration-api.adoc | 2 +-
.../svc/pages/integration-api/BookmarkService.adoc | 8 ++++----
core/_adoc-rg/modules/svc/pages/intro.adoc | 2 +-
core/_adoc-rg/modules/svc/pages/metadata-api.adoc | 2 +-
.../metadata-api/ApplicationFeatureRepository.adoc | 2 +-
.../modules/svc/pages/persistence-layer-api.adoc | 2 +-
.../modules/svc/pages/persistence-layer-spi.adoc | 2 +-
.../persistence-layer-spi/AuditerService.adoc | 4 ++--
.../persistence-layer-spi/PublisherService.adoc | 2 +-
.../modules/svc/pages/presentation-layer-spi.adoc | 2 +-
.../ContentMappingService.adoc | 2 +-
.../SessionLoggingService.adoc | 2 +-
core/_adoc-rg/modules/svc/pages/testing.adoc | 4 ++--
.../deployment/externalized-configuration.adoc | 2 +-
.../BackgroundCommandExecution.adoc | 2 +-
.../btb/pages/hints-and-tips/multi-tenancy.adoc | 4 ++--
.../modules/fun/pages/building-blocks/modules.adoc | 2 +-
.../jdo/_adoc/modules/ROOT/pages/db-schemas.adoc | 2 +-
.../pages/hints-and-tips/jdoql-and-timestamps.adoc | 2 +-
.../hints-and-tips/overriding-jdo-annotations.adoc | 2 +-
core/security/_adoc/modules/ROOT/pages/about.adoc | 6 +++---
.../modules/ROOT/pages/api-for-applications.adoc | 4 ++--
.../isisaddons-security-module-realm.adoc | 2 +-
.../shiro-realm-implementations/jdbc-realm.adoc | 2 +-
.../modules/ROOT/pages/usage-by-isis-viewers.adoc | 2 +-
.../ROOT/pages/fixture-scripts/api-and-usage.adoc | 4 ++--
.../_adoc/modules/ROOT/pages/overview.adoc | 4 ++--
.../soap-fake-server-junit-rule.adoc | 2 +-
.../_adoc/modules/ROOT/pages/about.adoc | 2 +-
.../login-via-query-args-prototyping.adoc | 2 +-
.../pages/extending/replacing-page-elements.adoc | 4 ++--
.../ROOT/pages/features/user-registration.adoc | 2 +-
.../_adoc/modules/ROOT/pages/incode-platform.adoc | 4 ++--
.../modules/ROOT/pages/layout/file-based.adoc | 2 +-
.../_adoc/modules/ROOT/pages/menubars-layout.adoc | 2 +-
.../simpleapp/_adoc/modules/ROOT/pages/about.adoc | 2 +-
96 files changed, 153 insertions(+), 153 deletions(-)
diff --git a/README.adoc b/README.adoc
index e4fd756..f892589 100644
--- a/README.adoc
+++ b/README.adoc
@@ -19,13 +19,13 @@ Isis automatically generates the UI from the domain classes.
The following screenshots are taken from the Isis Addons' http://github.com/isisaddons/isis-app-todoapp[todoapp example], which you are free to fork and use as you will.
The corresponding domain classes from which this UI was built can be found https://github.com/isisaddons/isis-app-todoapp/tree/0669d6e2acc5bcad1d9978a4514a17bcf7beab1f/dom/src/main/java/todoapp/dom/module/todoitem[here].
-The todoapp also integrates with a number of other modules provided by the link:http://platform.incode.org[Incode Platform].
+The todoapp also integrates with a number of other modules provided by the link:https://platform.incode.org[Incode Platform].
Please note that these modules are not part of ASF, but they *are* all licensed under Apache License 2.0 and are maintained by Apache the Isis committers.
=== Sign-in
Apache Isis integrates with http://shiro.apache.org[Apache Shiro].
-The core framework supports file-based realms, while the (non-ASF) link:http://platform.incode.org[Incode Platform]'s link:http://platform.incode.org/modules/spi/security/spi-security.html[security module] provides a well-features subdomain of users, roles and permissions against features derived from the Isis metamodel.
+The core framework supports file-based realms, while the (non-ASF) link:https://platform.incode.org[Incode Platform]'s link:https://platform.incode.org/modules/spi/security/spi-security.html[security module] provides a well-features subdomain of users, roles and permissions against features derived from the Isis metamodel.
The example todoapp integrates with the security module.
image::https://raw.github.com/apache/isis/master/adocs/documentation/src/main/asciidoc/pages/isis-in-pictures/images/isis-in-pictures/010-login.png[link="https://raw.github.com/apache/isis/master/adocs/documentation/src/main/asciidoc/images/isis-in-pictures/010-login.png"]
@@ -134,11 +134,11 @@ image::https://raw.github.com/apache/isis/master/adocs/documentation/src/main/as
As well as providing extensions to the UI, the (non-ASF) Incode Platform provides a rich set of modules to support various cross-cutting concerns.
-Under the activity menu are four sets of services which provide support for link:http://platform.incode.org/modules/spi/sessionlogger/spi-sessionlogger.html[user session logging/auditing], link:http://platform.incode.org/modules/spi/command/spi-command[command profiling], link:http://platform.incode.org/modules/spi/audit/spi-audit.html[(object change) auditing] (shown) and (inter-system) link:http://platform.incode.org/modules/spi/publishmq/spi-publishmq[event publishing]:
+Under the activity menu are four sets of services which provide support for link:https://platform.incode.org/modules/spi/sessionlogger/spi-sessionlogger.html[user session logging/auditing], link:https://platform.incode.org/modules/spi/command/spi-command[command profiling], link:https://platform.incode.org/modules/spi/audit/spi-audit.html[(object change) auditing] (shown) and (inter-system) link:https://platform.incode.org/modules/spi/publishmq/spi-publishmq[event publishing]:
image::https://raw.github.com/apache/isis/master/adocs/documentation/src/main/asciidoc/pages/isis-in-pictures/images/isis-in-pictures/120-auditing.png[link="https://raw.github.com/apache/isis/master/adocs/documentation/src/main/asciidoc/pages/isis-in-pictures/images/isis-in-pictures/120-auditing.png"]
-In the security menu is access to the rich set of functionality provided by the link:http://platform.incode.org/modules/spi/security/spi-security.html[security module]:
+In the security menu is access to the rich set of functionality provided by the link:https://platform.incode.org/modules/spi/security/spi-security.html[security module]:
image::https://raw.github.com/apache/isis/master/adocs/documentation/src/main/asciidoc/pages/isis-in-pictures/images/isis-in-pictures/130-security.png[link="https://raw.github.com/apache/isis/master/adocs/documentation/src/main/asciidoc/pages/isis-in-pictures/images/isis-in-pictures/130-security.png"]
@@ -147,21 +147,21 @@ This file can then be translated into multiple languages so that your app can su
image::https://raw.github.com/apache/isis/master/adocs/documentation/src/main/asciidoc/pages/isis-in-pictures/images/isis-in-pictures/140-i18n.png[link="https://raw.github.com/apache/isis/master/adocs/documentation/src/main/asciidoc/pages/isis-in-pictures/images/isis-in-pictures/140-i18n.png"]
-The Incode Platform also provides a module for managing link:http://platform.incode.org/modules/dom/settings/dom-settings.html[application and user settings].
+The Incode Platform also provides a module for managing link:https://platform.incode.org/modules/dom/settings/dom-settings.html[application and user settings].
Most apps (the todoapp example included) won't expose these services directly, but will usually wrap them in their own app-specific settings service that trivially delegates to the settings module's services:
image::https://raw.github.com/apache/isis/master/adocs/documentation/src/main/asciidoc/pages/isis-in-pictures/images/isis-in-pictures/150-appsettings.png[link="https://raw.github.com/apache/isis/master/adocs/documentation/src/main/asciidoc/pages/isis-in-pictures/images/isis-in-pictures/150-appsettings.png"]
=== Multi-tenancy support
-Of the various modules in the Incode Platform, the link:http://platform.incode.org/modules/spi/security/spi-security.html[security module] has the most features.
+Of the various modules in the Incode Platform, the link:https://platform.incode.org/modules/spi/security/spi-security.html[security module] has the most features.
One significant feature is the ability to associate users and objects with a "tenancy".
The todoapp uses this feature so that different users' list of todo items are kept separate from one another.
A user with administrator is able to switch their own "tenancy" to the tenancy of some other user, in order to access the objects in that tenancy:
image::https://raw.github.com/apache/isis/master/adocs/documentation/src/main/asciidoc/pages/isis-in-pictures/images/isis-in-pictures/160-switch-tenancy.png[link="https://raw.github.com/apache/isis/master/adocs/documentation/src/main/asciidoc/pages/isis-in-pictures/images/isis-in-pictures/160-switch-tenancy.png"]
-For more details, see the security module's link:http://platform.incode.org/modules/spi/security/spi-security.html[README].
+For more details, see the security module's link:https://platform.incode.org/modules/spi/security/spi-security.html[README].
=== Me
diff --git a/antora/components/mignotes/modules/ROOT/pages/mn-1.12.0-to-1.13.0.adoc b/antora/components/mignotes/modules/ROOT/pages/mn-1.12.0-to-1.13.0.adoc
index 3d31a5b..450b495 100644
--- a/antora/components/mignotes/modules/ROOT/pages/mn-1.12.0-to-1.13.0.adoc
+++ b/antora/components/mignotes/modules/ROOT/pages/mn-1.12.0-to-1.13.0.adoc
@@ -39,7 +39,7 @@ As a side-effect of this work, note also that:
The link:https://isis.apache.org/versions/1.13.0/guides/rgsvc/rgsvc.html#_rgsvc_persistence-layer-spi_AuditingService[`AuditingService`] SPI service has been deprecated, instead replaced by the link:https://isis.apache.org/versions/1.13.0/guides/rgsvc/rgsvc.html#_rgsvc_persistence-layer-spi_AuditerService[`AuditerService`].
There can be more than one implementation of this new SPI, and a framework-provided implementation (`AuditerServiceLogging`) will log to a file.
-The (non-ASF) link:http://platform.incode.org[Incode Platform^]'s audit module also implements the new SPI.
+The (non-ASF) link:https://platform.incode.org[Incode Platform^]'s audit module also implements the new SPI.
== Publishing
@@ -47,7 +47,7 @@ The (non-ASF) link:http://platform.incode.org[Incode Platform^]'s audit module a
The link:https://isis.apache.org/versions/1.13.0/guides/rgsvc/rgsvc.html#_rgsvc_persistence-layer-spi_PublishingService[`PublishingService`] SPI service and its supporting link:https://isis.apache.org/versions/1.13.0/guides/rgsvc/rgsvc.html#_rgsvc_persistence-layer-spi_EventSerializer[`EventSerializer`] domain service, have both deprecated, instead replaced by the link:https://isis.apache.org/versions/1.13.0/guides/rgsvc/rgsvc.html#_rgsvc_persistence-layer-spi_PublisherService[`Publisher [...]
There can be more than one implementation of this new SPI, and a framework-provided implementation (`PublisherServiceLogging`) will log to a file.
-The (non-ASF) link:http://platform.incode.org[Incode Platform^]'s publishmq module also implements the new SPI.
+The (non-ASF) link:https://platform.incode.org[Incode Platform^]'s publishmq module also implements the new SPI.
The new service also supports the notion of published property edits; the new link:https://isis.apache.org/versions/1.13.0/guides/rgant/rgant.html#_rgant-Property_publishing[`@Property#publishing()`] annotation attribute can be used to specify.
The ` isis.services.publish.properties` configuration property can be used to specify a fallback default for properties where the attribute is not set explicitly.
diff --git a/antora/components/mignotes/modules/ROOT/pages/mn-1.14.0-to-1.15.0.adoc b/antora/components/mignotes/modules/ROOT/pages/mn-1.14.0-to-1.15.0.adoc
index b858edf..ec48d0b 100644
--- a/antora/components/mignotes/modules/ROOT/pages/mn-1.14.0-to-1.15.0.adoc
+++ b/antora/components/mignotes/modules/ROOT/pages/mn-1.14.0-to-1.15.0.adoc
@@ -143,7 +143,7 @@ The first exception encountered is then re-thrown (to preserve similar behaviour
== (non-ASF) Incode Platform
-The various (non-ASF) link:http://isisaddons.org[Isis Addons] and link:http://catalog.incode.org[Incode Catalog] have also been combined into a single link:http://platform.incode.org["Incode Platform"].
+The various (non-ASF) link:http://isisaddons.org[Isis Addons] and link:http://catalog.incode.org[Incode Catalog] have also been combined into a single link:https://platform.incode.org["Incode Platform"].
While each module can still be consumed individually, the new platform versions consistently (a change in any one module will result in a re-release of all).
This should make these modules easier to consume, and easier to maintain/develop.
diff --git a/antora/components/mignotes/modules/ROOT/pages/mn-1.15.0-to-1.16.0.adoc b/antora/components/mignotes/modules/ROOT/pages/mn-1.15.0-to-1.16.0.adoc
index 4862ecd..c0c91a9 100644
--- a/antora/components/mignotes/modules/ROOT/pages/mn-1.15.0-to-1.16.0.adoc
+++ b/antora/components/mignotes/modules/ROOT/pages/mn-1.15.0-to-1.16.0.adoc
@@ -45,7 +45,7 @@ Note that `isis-mavendeps-webapp` has been updated with support for running with
== (non-ASF) Incode Platform
-The generic subdomain modules of the (non-ASF) link:http://platform.incode.org["Incode Platform"] have been demoted to instead act as examples.
+The generic subdomain modules of the (non-ASF) link:https://platform.incode.org["Incode Platform"] have been demoted to instead act as examples.
Rather than consume as binaries, the recommendation is to copy in the source code into your application and adapt as required.
diff --git a/antora/components/mignotes/modules/ROOT/pages/mn-1.8.0-to-1.9.0/mn-1.8.0-to-1.9.0_bootstrapping-using-AppManifest.adoc b/antora/components/mignotes/modules/ROOT/pages/mn-1.8.0-to-1.9.0/mn-1.8.0-to-1.9.0_bootstrapping-using-AppManifest.adoc
index c5b955c..cdb219e 100644
--- a/antora/components/mignotes/modules/ROOT/pages/mn-1.8.0-to-1.9.0/mn-1.8.0-to-1.9.0_bootstrapping-using-AppManifest.adoc
+++ b/antora/components/mignotes/modules/ROOT/pages/mn-1.8.0-to-1.9.0/mn-1.8.0-to-1.9.0_bootstrapping-using-AppManifest.adoc
@@ -122,7 +122,7 @@ public class MyAppAppManifest implements AppManifest {
----
<1> the module classes, whose packages specify the existence of domain services and/or persistent entities.
If your app uses (non-ASF) link:http://www.isisaddons.org[Isis Addons] modules, then include the module classes for these addons in `getModules()`.
-For example, the (non-ASF) link:http://platform.incode.org[Incode Platform^]'s security module provides the `org.isisaddons.module.security.SecurityModule` class.
+For example, the (non-ASF) link:https://platform.incode.org[Incode Platform^]'s security module provides the `org.isisaddons.module.security.SecurityModule` class.
<2> any additional services, as per `isis.services` configuration property.
diff --git a/antora/components/mignotes/modules/ROOT/pages/mn-1.8.0-to-1.9.0/mn-1.8.0-to-1.9.0_upgrading-to-java8.adoc b/antora/components/mignotes/modules/ROOT/pages/mn-1.8.0-to-1.9.0/mn-1.8.0-to-1.9.0_upgrading-to-java8.adoc
index 9ba5189..b57eb2f 100644
--- a/antora/components/mignotes/modules/ROOT/pages/mn-1.8.0-to-1.9.0/mn-1.8.0-to-1.9.0_upgrading-to-java8.adoc
+++ b/antora/components/mignotes/modules/ROOT/pages/mn-1.8.0-to-1.9.0/mn-1.8.0-to-1.9.0_upgrading-to-java8.adoc
@@ -39,7 +39,7 @@ under `build/pluginManagement/plugins`, add (or update) `maven-compiler-plugin`:
[TIP]
====
-The `-parameters` argument causes the Java compiler to capture the names of method parameters in the `.class` files. Apache Isis can be configured to use this, thereby avoiding the requirement to annotate every parameter with `@ParameterLayout(named=...)`. The necessary configuration is provided in the (non-ASF) link:http://platform.incode.org[Incode Platform^]'s paraname8 metamodel extension.
+The `-parameters` argument causes the Java compiler to capture the names of method parameters in the `.class` files. Apache Isis can be configured to use this, thereby avoiding the requirement to annotate every parameter with `@ParameterLayout(named=...)`. The necessary configuration is provided in the (non-ASF) link:https://platform.incode.org[Incode Platform^]'s paraname8 metamodel extension.
====
diff --git a/antora/components/mignotes/modules/ROOT/pages/mn-1.9.0-to-1.10.0.adoc b/antora/components/mignotes/modules/ROOT/pages/mn-1.9.0-to-1.10.0.adoc
index b8557ec..55bbb70 100644
--- a/antora/components/mignotes/modules/ROOT/pages/mn-1.9.0-to-1.10.0.adoc
+++ b/antora/components/mignotes/modules/ROOT/pages/mn-1.9.0-to-1.10.0.adoc
@@ -41,7 +41,7 @@ Therefore, in the parent `pom.xml` of your own domain applications, remove:
One possible issue is that (as per link:https://issues.apache.org/jira/browse/ISIS-830[ISIS-830]) the link:https://isis.apache.org/versions/1.10.0/guides/rgsvc/rgsvc.html#_rgsvc_core-domain-api_EventBusService[`EventBusService`] is now initialized as one of the first domain
services; this is to ensure that any object lifecycle events caused by domain services initializing themselves can be
posted on the event bus for subscribers. The typical case for such lifecycle events to occur is from domain services
-that seed reference data; one such example can be found in the (non-ASF) link:http://platform.incode.org[Incode Platform^]'s security module.
+that seed reference data; one such example can be found in the (non-ASF) link:https://platform.incode.org[Incode Platform^]'s security module.
In previous releases, the ordering of initialization for the `EventBusService` was undefined (but would typically be towards the
"end" of the list of services. What this meant in practice is that it generally didn't matter whether (domain service)
diff --git a/antora/components/relnotes/modules/ROOT/pages/rn-1.10.0.adoc b/antora/components/relnotes/modules/ROOT/pages/rn-1.10.0.adoc
index 2d45ced..5b6c62b 100644
--- a/antora/components/relnotes/modules/ROOT/pages/rn-1.10.0.adoc
+++ b/antora/components/relnotes/modules/ROOT/pages/rn-1.10.0.adoc
@@ -5,7 +5,7 @@ include::_attributes.adoc[]
-Apache Isis 1.10.0 provides a couple of new domain services. Client-side filtering of objects (eg to support (non-ASF) link:http://platform.incode.org[Incode Platform^]'s security module's multi-tenancy support) is completed so that autocomplete//choices, summary totals and components such as (non-ASF) link:http://platform.incode.org[Incode Platform^]'s gmap3 wicket component show only filtered objects.
+Apache Isis 1.10.0 provides a couple of new domain services. Client-side filtering of objects (eg to support (non-ASF) link:https://platform.incode.org[Incode Platform^]'s security module's multi-tenancy support) is completed so that autocomplete//choices, summary totals and components such as (non-ASF) link:https://platform.incode.org[Incode Platform^]'s gmap3 wicket component show only filtered objects.
The "are you sure" semantic and corresponding UI is also available, as well as the ability to specify the default view for collections.
The release also introduces a new type of contribution service (mixins), as well as bringing in support for Project Lombok
diff --git a/antora/components/relnotes/modules/ROOT/pages/rn-1.12.0.adoc b/antora/components/relnotes/modules/ROOT/pages/rn-1.12.0.adoc
index 2ce6c13..3d7ebcf 100644
--- a/antora/components/relnotes/modules/ROOT/pages/rn-1.12.0.adoc
+++ b/antora/components/relnotes/modules/ROOT/pages/rn-1.12.0.adoc
@@ -7,7 +7,7 @@ include::_attributes.adoc[]
The main feature in 1.12.0 is much enhanced support for custom layouts, using an optional separate XML layout file `Xxx.layout.xml` (where `Xxx` is the class of the object being rendered). This is similar in concept to the earlier support we have had for custom layouts through a `.layout.json` file, but introduces the ability to position object members anywhere using bootstrap columns and rows. It also brings in
-support for tabgroups, and allows object members to be included in the page more than once (eg a table view and also a (non-ASF) link:http://platform.incode.org[Incode Platform^]'s fullcalendar2 view).
+support for tabgroups, and allows object members to be included in the page more than once (eg a table view and also a (non-ASF) link:https://platform.incode.org[Incode Platform^]'s fullcalendar2 view).
As a result of this change, the support for editing objects has been modified; rather than an 'edit' button which toggles the entire
page into edit mode, instead each property is edited individually. The current implementation of this is using a prompt dialog (very
diff --git a/antora/components/relnotes/modules/ROOT/pages/rn-1.13.0.adoc b/antora/components/relnotes/modules/ROOT/pages/rn-1.13.0.adoc
index 6003c43..b11d23b 100644
--- a/antora/components/relnotes/modules/ROOT/pages/rn-1.13.0.adoc
+++ b/antora/components/relnotes/modules/ROOT/pages/rn-1.13.0.adoc
@@ -17,8 +17,8 @@ replaced by link:https://isis.apache.org/versions/1.13.0/guides/rgsvc/rgsvc.html
link:https://isis.apache.org/versions/1.13.0/guides/rgsvc/rgsvc.html#_rgsvc_persistence-layer-spi_PublisherService[`PublisherService`]. It is now possible to have multiple implementations
of each.
-The (non-ASF) link:http://platform.incode.org[Incode Platform^]'s auditing module has been reworked to
-implement link:https://isis.apache.org/versions/1.13.0/guides/rgsvc/rgsvc.html#_rgsvc_spi_AuditService[`AuditService`], while the new (non-ASF) link:http://platform.incode.org[Incode Platform^]'s publishmq module implements
+The (non-ASF) link:https://platform.incode.org[Incode Platform^]'s auditing module has been reworked to
+implement link:https://isis.apache.org/versions/1.13.0/guides/rgsvc/rgsvc.html#_rgsvc_spi_AuditService[`AuditService`], while the new (non-ASF) link:https://platform.incode.org[Incode Platform^]'s publishmq module implements
link:https://isis.apache.org/versions/1.13.0/guides/rgsvc/rgsvc.html#_rgsvc_persistence-layer-spi_PublisherService[`PublisherService`] to publish interaction events to an ActiveMQ bus (and
to allow such events to be replayed if necessary).
diff --git a/antora/components/relnotes/modules/ROOT/pages/rn-1.13.2.adoc b/antora/components/relnotes/modules/ROOT/pages/rn-1.13.2.adoc
index 4a10c09..50ac307 100644
--- a/antora/components/relnotes/modules/ROOT/pages/rn-1.13.2.adoc
+++ b/antora/components/relnotes/modules/ROOT/pages/rn-1.13.2.adoc
@@ -6,14 +6,14 @@ include::_attributes.adoc[]
This is a maintenance release with a number of minor improvements and bug fixes.
If these the main improvement is that the simpleapp archetype has been substantially reworked to be more modular.
-This release also closes the ticket to provide a better DB migration story; this has been implemented by way of the (non-ASF) link:http://platform.incode.org[Incode Platform^]'s flywaydb module.
+This release also closes the ticket to provide a better DB migration story; this has been implemented by way of the (non-ASF) link:https://platform.incode.org[Incode Platform^]'s flywaydb module.
== New Feature
* link:https://issues.apache.org/jira/browse/ISIS-1542[ISIS-1542] - Update simpleapp application/archetype to provide access to HSQL DB Manager (via their Swing UI) when running in-memory
-* link:https://issues.apache.org/jira/browse/ISIS-1471[ISIS-1471] - Integrate Flyway or Liquibase or something similar (see (non-ASF) link:http://platform.incode.org[Incode Platform^]'s flywaydb module.
+* link:https://issues.apache.org/jira/browse/ISIS-1471[ISIS-1471] - Integrate Flyway or Liquibase or something similar (see (non-ASF) link:https://platform.incode.org[Incode Platform^]'s flywaydb module.
== Improvement
diff --git a/antora/components/relnotes/modules/ROOT/pages/rn-1.15.0.adoc b/antora/components/relnotes/modules/ROOT/pages/rn-1.15.0.adoc
index c1b8fdb..1425965 100644
--- a/antora/components/relnotes/modules/ROOT/pages/rn-1.15.0.adoc
+++ b/antora/components/relnotes/modules/ROOT/pages/rn-1.15.0.adoc
@@ -16,7 +16,7 @@ That said, we do recommend that you read and keep in mind the link:https://isis.
[NOTE]
====
-The supporting (non-ASF) link:http://isisaddons.org[Isis Addons] and link:http://catalog.incode.org[Incode Catalog] have also been combined into a single link:http://platform.incode.org["Incode Platform"].
+The supporting (non-ASF) link:http://isisaddons.org[Isis Addons] and link:http://catalog.incode.org[Incode Catalog] have also been combined into a single link:https://platform.incode.org["Incode Platform"].
While each module can still be consumed individually, the new platform versions consistently (a change in any one module will result in a re-release of all).
This should make these modules easier to consume, and easier to maintain/develop.
@@ -129,7 +129,7 @@ All the modules remain open source, still licensed under the ASF v2.0 license.
== Incode Platform
-Implemented in the (non-ASF) link:http://platform.incode.org[Incode Platform^].
+Implemented in the (non-ASF) link:https://platform.incode.org[Incode Platform^].
* link:https://issues.apache.org/jira/browse/ISIS-513[ISIS-513] - [ADDONS] Wicket: Pdf.js display in browser natively
diff --git a/antora/components/relnotes/modules/ROOT/pages/rn-1.16.1.adoc b/antora/components/relnotes/modules/ROOT/pages/rn-1.16.1.adoc
index 3d9255d..9b7ad5d 100644
--- a/antora/components/relnotes/modules/ROOT/pages/rn-1.16.1.adoc
+++ b/antora/components/relnotes/modules/ROOT/pages/rn-1.16.1.adoc
@@ -17,7 +17,7 @@ As part of this change, the new `@Action(associateWith="...")` attribute can be
* link:https://issues.apache.org/jira/browse/ISIS-1569[ISIS-1569] provides infrastructure to enable commands to be replayed from master to slave (for regression testing purposes).
+
-The majority of the implementation is provided in the (non-ASF) (non-ASF) link:http://platform.incode.org[Incode Platform]'s new link:http://platform.incode.org/modules/spi/command/spi-command-replay.html[command replay] library.
+The majority of the implementation is provided in the (non-ASF) (non-ASF) link:https://platform.incode.org[Incode Platform]'s new link:https://platform.incode.org/modules/spi/command/spi-command-replay.html[command replay] library.
Applications written against v1.16.0 should run against v1.16.1 with few if any changes.
diff --git a/antora/components/relnotes/modules/ROOT/pages/rn-1.7.0.adoc b/antora/components/relnotes/modules/ROOT/pages/rn-1.7.0.adoc
index 38283d4..4058e98 100644
--- a/antora/components/relnotes/modules/ROOT/pages/rn-1.7.0.adoc
+++ b/antora/components/relnotes/modules/ROOT/pages/rn-1.7.0.adoc
@@ -53,7 +53,7 @@ include::_attributes.adoc[]
=== Removed features
-Moved to (non-ASF) link:http://www.isisaddons.org[Isis Addons] (as of 1.15.0, part of (non-ASF) link:http://platform.incode.org[Incode Platform^]).
+Moved to (non-ASF) link:http://www.isisaddons.org[Isis Addons] (as of 1.15.0, part of (non-ASF) link:https://platform.incode.org[Incode Platform^]).
* link:https://issues.apache.org/jira/browse/ISIS-851[ISIS-851] - Remove modules from Apache Isis core (available instead through isisaddons).
* link:https://issues.apache.org/jira/browse/ISIS-887[ISIS-887] - xxx modules, as now in isisaddons.
diff --git a/antora/components/toc/modules/ROOT/pages/_partials/_powered-by_commapp.adoc b/antora/components/toc/modules/ROOT/pages/_partials/_powered-by_commapp.adoc
index 776be94..dfe6106 100644
--- a/antora/components/toc/modules/ROOT/pages/_partials/_powered-by_commapp.adoc
+++ b/antora/components/toc/modules/ROOT/pages/_partials/_powered-by_commapp.adoc
@@ -9,7 +9,7 @@ of a business. You can get a feel for it from this screenshot:
image::powered-by/commapp/screenshot-1.png[width="900px",link="{imagesdir}/powered-by/commapp/screenshot-1.png"]
-which shows how the app integrates a number of the (non-ASF) link:http://platform.incode.org[Incode Platform^] components
+which shows how the app integrates a number of the (non-ASF) link:https://platform.incode.org[Incode Platform^] components
(excel, fullcalendar2, gmap3 and wickedcharts).
@@ -24,7 +24,7 @@ So we added Apache Isis to our evaluation, and we found it to be open in many as
Our main focus in the code is given to the business domain, with business logic treated as a first class citizen.
And because our code simply uses non-proprietary Java, we've been able to extend it the normal way.
Very little code in our application so far can be considered to be framework-specific, the few that is only because we chose to use some
-of the (non-ASF) link:http://platform.incode.org[Incode Platform^] modules that provide our applications with high value, and which are
+of the (non-ASF) link:https://platform.incode.org[Incode Platform^] modules that provide our applications with high value, and which are
open source also.
When creating our prototype and then subsequent application, we've found quite amazing support: most of the time the
diff --git a/antora/components/toc/modules/ROOT/pages/_partials/_powered-by_estatio.adoc b/antora/components/toc/modules/ROOT/pages/_partials/_powered-by_estatio.adoc
index 8122e6b..bc8738e 100644
--- a/antora/components/toc/modules/ROOT/pages/_partials/_powered-by_estatio.adoc
+++ b/antora/components/toc/modules/ROOT/pages/_partials/_powered-by_estatio.adoc
@@ -25,7 +25,7 @@ Since the initial release - as the scope of the application has grown - the team
== Supporting Open Source
-Much of Apache Isis' recent development has been driven out by the requirements of this application, so you can see for yourself how many of the features in Isis are used in real life. Much of the (non-ASF) link:http://platform.incode.org[Incode Platform^] also originate from the requirements of Estatio.
+Much of Apache Isis' recent development has been driven out by the requirements of this application, so you can see for yourself how many of the features in Isis are used in real life. Much of the (non-ASF) link:https://platform.incode.org[Incode Platform^] also originate from the requirements of Estatio.
Estatio itself is also open source, licensed under Apache Software License and available on link:https://github.com/estatio/estatio[github].
diff --git a/antora/components/toc/modules/ROOT/pages/_partials/_powered-by_gesconsultor-grc.adoc b/antora/components/toc/modules/ROOT/pages/_partials/_powered-by_gesconsultor-grc.adoc
index 74697f9..4194f43 100644
--- a/antora/components/toc/modules/ROOT/pages/_partials/_powered-by_gesconsultor-grc.adoc
+++ b/antora/components/toc/modules/ROOT/pages/_partials/_powered-by_gesconsultor-grc.adoc
@@ -78,7 +78,7 @@ We chose http://wavemaker.com[Wavemaker] for implementing the viewer, also lever
Even so, while GRC does (as the figures above show) include custom views, the majority of the views exposed by GRC are automatically generated from the underlying domain entities; the GRC viewer is a proprietary version of Isis' own xref:vw:ROOT:about.adoc[Wicket viewer].
At the last count more than 400 domain entities, across 6 different Bounded Contexts, are surfaced in the UI in this this way.
-At the Domain level, we also extensively use the xref:ug:fun:building-blocks.adoc#domain-events[domain events] functionality available in Apache Isis, along with many of the (non-ASF) link:http://platform.incode.org[Incode Platform^] (such as audit, security and excel modules).
+At the Domain level, we also extensively use the xref:ug:fun:building-blocks.adoc#domain-events[domain events] functionality available in Apache Isis, along with many of the (non-ASF) link:https://platform.incode.org[Incode Platform^] (such as audit, security and excel modules).
The GRC platform currently has more than 5600 automated tests, about 2000 being xref:testing:ROOT:bdd-spec-support.adoc[BDD tests] and 3600 xref:testing:ROOT:integ-test-support.adoc[integration tests], all leveraging Apache Isis' extensive testing capabilities.
diff --git a/antora/components/toc/modules/ROOT/pages/_partials/_powered-by_transport-planner.adoc b/antora/components/toc/modules/ROOT/pages/_partials/_powered-by_transport-planner.adoc
index 5dec2c5..325b0c5 100644
--- a/antora/components/toc/modules/ROOT/pages/_partials/_powered-by_transport-planner.adoc
+++ b/antora/components/toc/modules/ROOT/pages/_partials/_powered-by_transport-planner.adoc
@@ -22,16 +22,16 @@ is necessary).
[cols="2a,2a"]
|===
-|TransportPlanner allows schedules of journeys to be planned. It uses the (non-ASF) link:http://platform.incode.org[Incode Platform^]'s gmap3 wicket component to provide the map.
+|TransportPlanner allows schedules of journeys to be planned. It uses the (non-ASF) link:https://platform.incode.org[Incode Platform^]'s gmap3 wicket component to provide the map.
|image::https://www.assembla.com/code/transportplanner/git/node/blob/screenshots/TransportDemand.png?raw=1&rev=a9d5184ecb05c3d95dafec587c84cfcbc7a25b8b[width="530px",link="https://www.assembla.com/code/transportplanner/git/node/blob/screenshots/TransportDemand.png?raw=1&rev=a9d5184ecb05c3d95dafec587c84cfcbc7a25b8b"]
-|TransportPlanner uses the (non-ASF) link:http://platform.incode.org[Incode Platform^]'s wickedcharts wicket extension to provide custom graphs
+|TransportPlanner uses the (non-ASF) link:https://platform.incode.org[Incode Platform^]'s wickedcharts wicket extension to provide custom graphs
|image::https://www.assembla.com/code/transportplanner/git/node/blob/screenshots/TPM_CostPie.png?raw=1&rev=a9d5184ecb05c3d95dafec587c84cfcbc7a25b8b[width="530px",link="https://www.assembla.com/code/transportplanner/git/node/blob/screenshots/TPM_CostPie.png?raw=1&rev=a9d5184ecb05c3d95dafec587c84cfcbc7a25b8b"]
-|Another example of TransportPlanner's use of (non-ASF) link:http://platform.incode.org[Incode Platform^]'s wickedcharts component.
+|Another example of TransportPlanner's use of (non-ASF) link:https://platform.incode.org[Incode Platform^]'s wickedcharts component.
|image::https://www.assembla.com/code/transportplanner/git/node/blob/screenshots/Tpm_ResourceUsage.png?raw=1&rev=a9d5184ecb05c3d95dafec587c84cfcbc7a25b8b[width="530px",link="https://www.assembla.com/code/transportplanner/git/node/blob/screenshots/Tpm_ResourceUsage.png?raw=1&rev=a9d5184ecb05c3d95dafec587c84cfcbc7a25b8b"]
|===
diff --git a/antora/components/toc/modules/ROOT/pages/downloads/how-to.adoc b/antora/components/toc/modules/ROOT/pages/downloads/how-to.adoc
index b539c0b..64e1b26 100644
--- a/antora/components/toc/modules/ROOT/pages/downloads/how-to.adoc
+++ b/antora/components/toc/modules/ROOT/pages/downloads/how-to.adoc
@@ -105,7 +105,7 @@ The http://projects.apache.org/doap.html[description of a project] RDF file for
== Incode Platform
-The link:http://platform.incode.org[Incode Platform^] provides a number of (open source, but not ASF) supporting modules and extensions for you to use:
+The link:https://platform.incode.org[Incode Platform^] provides a number of (open source, but not ASF) supporting modules and extensions for you to use:
* technical libraries, such as excel, word and freemarker
diff --git a/antora/components/toc/modules/ROOT/pages/what-is-apache-isis/common-use-cases.adoc b/antora/components/toc/modules/ROOT/pages/what-is-apache-isis/common-use-cases.adoc
index 8385841..d0c99d4 100644
--- a/antora/components/toc/modules/ROOT/pages/what-is-apache-isis/common-use-cases.adoc
+++ b/antora/components/toc/modules/ROOT/pages/what-is-apache-isis/common-use-cases.adoc
@@ -24,7 +24,7 @@ One of the original motivations for Apache Isis itself was to be able automatica
Apache Isis' has a pluggable architecture allowing different user interface technologies.
The principal implementation (as configured by the xref:simpleapp:ROOT:about.adoc[SimpleApp archetype]) is the xref:vw:ROOT:about.adoc[Wicket viewer].
This provides an appealing default user interface, with the ability to customize the user interface by writing new http://wicket.apache.org[Apache Wicket] components.
-Some third-party components can be found in the (non-ASF) link:http://platform.incode.org[Incode Platform^].
+Some third-party components can be found in the (non-ASF) link:https://platform.incode.org[Incode Platform^].
Deploying on Apache Isis means that the framework also manages object persistence.
diff --git a/antora/components/toc/modules/ROOT/pages/what-is-apache-isis/isis-in-pictures.adoc b/antora/components/toc/modules/ROOT/pages/what-is-apache-isis/isis-in-pictures.adoc
index 4ea5ea8..9ff918d 100644
--- a/antora/components/toc/modules/ROOT/pages/what-is-apache-isis/isis-in-pictures.adoc
+++ b/antora/components/toc/modules/ROOT/pages/what-is-apache-isis/isis-in-pictures.adoc
@@ -11,7 +11,7 @@ On this page we want to show you what a modern Apache Isis application looks lik
The screenshots below are taken from the Isis Addons' http://github.com/isisaddons/isis-app-todoapp[todoapp example] (non ASF), which you are free to fork and use as you will.
The corresponding domain classes from which this UI was built can be found https://github.com/isisaddons/isis-app-todoapp/tree/master/dom/src/main/java/todoapp/dom/todoitem[here].
-The todoapp also integrates with a number of other modules from the (non-ASF) link:http://platform.incode.org[Incode Platform^].
+The todoapp also integrates with a number of other modules from the (non-ASF) link:https://platform.incode.org[Incode Platform^].
Because we expect that most apps will end up using one or more of these modules, we've chosen to include screenshots of those too.
[NOTE]
@@ -27,7 +27,7 @@ Let's start with the basics...
=== Sign-in
Apache Isis integrates with http://shiro.apache.org[Apache Shiro].
-The core framework supports file-based realms, while the (non-ASF) link:http://platform.incode.org[Incode Platform^]'s security module provides a well-features subdomain of users, roles and permissions against features derived from the Apache Isis metamodel.
+The core framework supports file-based realms, while the (non-ASF) link:https://platform.incode.org[Incode Platform^]'s security module provides a well-features subdomain of users, roles and permissions against features derived from the Apache Isis metamodel.
The example todoapp integrates with the security module.
@@ -133,7 +133,7 @@ For example, when a collection of objects is rendered, this is just one of sever
image::what-is-apache-isis/isis-in-pictures/070-pluggable-views.png[width="800px",link="{imagesdir}/what-is-apache-isis/isis-in-pictures/070-pluggable-views.png"]
-The (non-ASF) link:http://platform.incode.org[Incode Platform^] provides a number of such extensions.
+The (non-ASF) link:https://platform.incode.org[Incode Platform^] provides a number of such extensions.
For example, the gmap3 component will render any domain entity (such as `ToDoItem`) that implements its `Locatable` interface:
image::what-is-apache-isis/isis-in-pictures/080-gmap3-view.png[width="800px",link="{imagesdir}/what-is-apache-isis/isis-in-pictures/080-gmap3-view.png"]
@@ -141,7 +141,7 @@ image::what-is-apache-isis/isis-in-pictures/080-gmap3-view.png[width="800px",lin
-Similarly the (non-ASF) link:http://platform.incode.org[Incode Platform^]'s fullcalendar2 component will render any domain entity (such as `ToDoItem`) that implements its `Calendarable` interface:
+Similarly the (non-ASF) link:https://platform.incode.org[Incode Platform^]'s fullcalendar2 component will render any domain entity (such as `ToDoItem`) that implements its `Calendarable` interface:
image::what-is-apache-isis/isis-in-pictures/090-fullcalendar2-view.png[width="800px",link="{imagesdir}/what-is-apache-isis/isis-in-pictures/090-fullcalendar2-view.png"]
@@ -149,7 +149,7 @@ image::what-is-apache-isis/isis-in-pictures/090-fullcalendar2-view.png[width="80
-Yet another "view" (though this one is rather simpler) is that provided by the (non-ASF) link:http://platform.incode.org[Incode Platform^]'s excel Wicket component
+Yet another "view" (though this one is rather simpler) is that provided by the (non-ASF) link:https://platform.incode.org[Incode Platform^]'s excel Wicket component
This provides a download button to the table as a spreadsheet:
image::what-is-apache-isis/isis-in-pictures/100-excel-view-and-docx.png[width="800px",link="{imagesdir}/what-is-apache-isis/isis-in-pictures/100-excel-view-and-docx.png"]
@@ -158,7 +158,7 @@ image::what-is-apache-isis/isis-in-pictures/100-excel-view-and-docx.png[width="8
The screenshot above also shows an "export to Word" action.
-This is _not_ a view but instead is a (contributed) action that uses the (non-ASF) link:http://platform.incode.org[Incode Platform^]'s docx module to perform a "mail-merge":
+This is _not_ a view but instead is a (contributed) action that uses the (non-ASF) link:https://platform.incode.org[Incode Platform^]'s docx module to perform a "mail-merge":
image::what-is-apache-isis/isis-in-pictures/110-docx.png[width="800px",link="{imagesdir}/what-is-apache-isis/isis-in-pictures/110-docx.png"]
@@ -177,13 +177,13 @@ Please note that the Isis Addons are not part of ASF, but they _are_ all license
As well as providing extensions to the UI, the (non ASF) Isis Addons provide a rich set of modules to support various cross-cutting concerns.
-Under the activity menu are four sets of services which provide support for (non-ASF) link:http://platform.incode.org[Incode Platform^]'s sessionlogger module (for user session logging/auditing) , command module (audit/profiling), audit module (audit object changes) (shown) and (inter-system) event publishing:
+Under the activity menu are four sets of services which provide support for (non-ASF) link:https://platform.incode.org[Incode Platform^]'s sessionlogger module (for user session logging/auditing) , command module (audit/profiling), audit module (audit object changes) (shown) and (inter-system) event publishing:
image::what-is-apache-isis/isis-in-pictures/120-auditing.png[width="800px",link="{imagesdir}/what-is-apache-isis/isis-in-pictures/120-auditing.png"]
-In the security menu is access to the rich set of functionality provided by the (non-ASF) link:http://platform.incode.org[Incode Platform^]'s security module:
+In the security menu is access to the rich set of functionality provided by the (non-ASF) link:https://platform.incode.org[Incode Platform^]'s security module:
image::what-is-apache-isis/isis-in-pictures/130-security.png[width="800px",link="{imagesdir}/what-is-apache-isis/isis-in-pictures/130-security.png"]
@@ -199,7 +199,7 @@ image::what-is-apache-isis/isis-in-pictures/140-i18n.png[width="800px",link="{im
-The (non-ASF) link:http://platform.incode.org[Incode Platform^] also provides a module for managing application and user settings.
+The (non-ASF) link:https://platform.incode.org[Incode Platform^] also provides a module for managing application and user settings.
Most apps (the todoapp example included) won't expose these services directly, but will usually wrap them in their own app-specific settings service that trivially delegates to the settings module's services:
image::what-is-apache-isis/isis-in-pictures/150-appsettings.png[width="800px",link="{imagesdir}/what-is-apache-isis/isis-in-pictures/150-appsettings.png"]
@@ -209,7 +209,7 @@ image::what-is-apache-isis/isis-in-pictures/150-appsettings.png[width="800px",li
=== Multi-tenancy support
-One significant feature of the (non-ASF) link:http://platform.incode.org[Incode Platform^]'s security module is the ability to associate users and objects with a "tenancy".
+One significant feature of the (non-ASF) link:https://platform.incode.org[Incode Platform^]'s security module is the ability to associate users and objects with a "tenancy".
The todoapp uses this feature so that different users' list of todo items are kept separate from one another.
A user with administrator is able to switch their own "tenancy" to the tenancy of some other user, in order to access the objects in that tenancy:
@@ -217,12 +217,12 @@ image::what-is-apache-isis/isis-in-pictures/160-switch-tenancy.png[width="800px"
-For more details, see the (non-ASF) link:http://platform.incode.org[Incode Platform^]'s security module README.
+For more details, see the (non-ASF) link:https://platform.incode.org[Incode Platform^]'s security module README.
=== Me
-Most of the (non-ASF) link:http://platform.incode.org[Incode Platform^]'s security module's services are on the security menu, which would normally be provided only to administrators.
+Most of the (non-ASF) link:https://platform.incode.org[Incode Platform^]'s security module's services are on the security menu, which would normally be provided only to administrators.
Kept separate is the "me" action:
image::what-is-apache-isis/isis-in-pictures/170-me.png[width="800px",link="{imagesdir}/what-is-apache-isis/isis-in-pictures/170-me.png"]
diff --git a/antora/components/toc/modules/ROOT/pages/what-is-apache-isis/screencasts-older.adoc b/antora/components/toc/modules/ROOT/pages/what-is-apache-isis/screencasts-older.adoc
index 446e6c9..ec2b795 100644
--- a/antora/components/toc/modules/ROOT/pages/what-is-apache-isis/screencasts-older.adoc
+++ b/antora/components/toc/modules/ROOT/pages/what-is-apache-isis/screencasts-older.adoc
@@ -83,7 +83,7 @@ Learn more xref:toc:devguide:about.adoc#intellij[here]
_Configuring the command and auditing add-on modules for the xref:simpleapp:ROOT:about.adoc[SimpleApp]._ +
-Learn more at the (non-ASF) link:http://platform.incode.org[Incode Platform^]'s command and audit SPI modules
+Learn more at the (non-ASF) link:https://platform.incode.org[Incode Platform^]'s command and audit SPI modules
|video::g01tK58MxJ8[youtube,width="420px",height="236px"]
@@ -92,7 +92,7 @@ Learn more at the (non-ASF) link:http://platform.incode.org[Incode Platform^]'s
_Configuring the security add-on module for for the xref:simpleapp:ROOT:about.adoc[SimpleApp]._ +
-Learn more at the (non-ASF) link:http://platform.incode.org[Incode Platform^]'s security SPI module.
+Learn more at the (non-ASF) link:https://platform.incode.org[Incode Platform^]'s security SPI module.
|video::bj8735nBRR4[youtube,width="420px",height="236px"]
@@ -102,7 +102,7 @@ Learn more at the (non-ASF) link:http://platform.incode.org[Incode Platform^]'s
_A run-through of the command (profiling) service, auditing service, publishing service. 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._ +
-Learn more at the (non-ASF) link:http://platform.incode.org[Incode Platform^]'s command and audit modules (also the obsolete http://github.com/isisaddons-legacy/isis-module-publishing[publishing] modules).
+Learn more at the (non-ASF) link:https://platform.incode.org[Incode Platform^]'s command and audit modules (also the obsolete http://github.com/isisaddons-legacy/isis-module-publishing[publishing] modules).
|video::tqXUZkPB3EI[youtube,width="420px",height="210px"]
@@ -110,7 +110,7 @@ Learn more at the (non-ASF) link:http://platform.incode.org[Incode Platform^]'s
|Bulk updates in Apache Isis (v1.5.0) +
-_Using the (non-ASF) link:http://platform.incode.org[Incode Platform^]'s excel module and view models to perform bulk updates)._
+_Using the (non-ASF) link:https://platform.incode.org[Incode Platform^]'s excel module and view models to perform bulk updates)._
|video::8SsRDhCUuRc[youtube,width="420px",height="315px"]
@@ -130,7 +130,7 @@ _Using the (non-ASF) link:http://platform.incode.org[Incode Platform^]'s excel m
|Customizing the Wicket viewer +
-_How to customize the Wicket viewer, integrating the (non-ASF) link:http://platform.incode.org[Incode Platform^]'s gmap3 wicket component._
+_How to customize the Wicket viewer, integrating the (non-ASF) link:https://platform.incode.org[Incode Platform^]'s gmap3 wicket component._
|video::9o5zAME8LrM[youtube,width="420px",height="315px"]
diff --git a/antora/components/toc/modules/ROOT/pages/what-is-apache-isis/screencasts.adoc b/antora/components/toc/modules/ROOT/pages/what-is-apache-isis/screencasts.adoc
index d7597b2..2c8dde6 100644
--- a/antora/components/toc/modules/ROOT/pages/what-is-apache-isis/screencasts.adoc
+++ b/antora/components/toc/modules/ROOT/pages/what-is-apache-isis/screencasts.adoc
@@ -307,7 +307,7 @@ Using link:https://projectlombok.org/[Project Lombok] to remove boilerplate from
|link:https://www.youtube.com/watch?v=AXuxULuRtm0[029^] +
-Using the (non-ASF) link:http://platform.incode.org[Incode Platform^]'s paraname8 metamodel extension to remove boilerplate from your domain object (xref:rg:ant:ParameterLayout/named.adoc[`@ParameterLayout#named()`] annotation attribute on action parameters).
+Using the (non-ASF) link:https://platform.incode.org[Incode Platform^]'s paraname8 metamodel extension to remove boilerplate from your domain object (xref:rg:ant:ParameterLayout/named.adoc[`@ParameterLayout#named()`] annotation attribute on action parameters).
|||||x|||x|||
@@ -412,7 +412,7 @@ Using the xref:rg:cms:classes/super/FixtureScript.adoc[`FixtureScript`] `default
|link:https://www.youtube.com/watch?v=-jMiD9n1L5U[040^] +
-Using the (non-ASF) link:http://platform.incode.org[Incode Platform^]'s fakedata module's `FakeDataService` to provide fake (random) names within a fixture script.
+Using the (non-ASF) link:https://platform.incode.org[Incode Platform^]'s fakedata module's `FakeDataService` to provide fake (random) names within a fixture script.
||x|||x||||||
@@ -475,27 +475,27 @@ include::partial$_screencasts-playlists.adoc[]
|link:https://www.youtube.com/watch?v=SoREp-8MQz0[047^] +
-Configuring an Apache Isis app to allow tables of objects to be downloaded as an Excel spreadsheet, using the (non-ASF) link:http://platform.incode.org[Incode Platform^]'s excel wicket component.
+Configuring an Apache Isis app to allow tables of objects to be downloaded as an Excel spreadsheet, using the (non-ASF) link:https://platform.incode.org[Incode Platform^]'s excel wicket component.
|||||x||||||
|link:https://www.youtube.com/watch?v=bqjLx8gMOEw[048^] +
Configuring an Apache Isis app to allow tables of domain objects with date information to be rendered on a full-page
-calendar, using the (non-ASF) link:http://platform.incode.org[Incode Platform^]'s fullcalendar2 wicket
+calendar, using the (non-ASF) link:https://platform.incode.org[Incode Platform^]'s fullcalendar2 wicket
component.
|||||x||||||
|link:https://www.youtube.com/watch?v=0YoFa44Xr6M[049^] +
Using the xref:rg:ant:Programmatic.adoc[`@Programmatic`] annotation to exclude methods from a domain object
-(eg implementing methods of an interface as defined by the (non-ASF) link:http://platform.incode.org[Incode Platform^]'s fullcalendar2 wicket component) that would
+(eg implementing methods of an interface as defined by the (non-ASF) link:https://platform.incode.org[Incode Platform^]'s fullcalendar2 wicket component) that would
otherwise be part of the Apache Isis metamodel (and thus show up in the UI).
||||||||||x|
|link:https://www.youtube.com/watch?v=mIwptdeZ67Q[050^] +
Configuring an Apache Isis app to allow tables of domain objects with location information to be rendered on map,
- using the (non-ASF) link:http://platform.incode.org[Incode Platform^]'s gmap3 wicket component.
+ using the (non-ASF) link:https://platform.incode.org[Incode Platform^]'s gmap3 wicket component.
|||||x||||||
diff --git a/antora/components/toc/modules/comguide/pages/post-release-successful.adoc b/antora/components/toc/modules/comguide/pages/post-release-successful.adoc
index 18cb8ca..859da3c 100644
--- a/antora/components/toc/modules/comguide/pages/post-release-successful.adoc
+++ b/antora/components/toc/modules/comguide/pages/post-release-successful.adoc
@@ -585,5 +585,5 @@ git push
== Release (non-ASF) Modules
-The (non-ASF) link:http://platform.incode.org[Incode Platform^] should also be released, as per their link:http://platform.incode.org/pages/committers-guide/committers-guide.html#_release_to_maven_central[release guide].
+The (non-ASF) link:https://platform.incode.org[Incode Platform^] should also be released, as per their link:https://platform.incode.org/pages/committers-guide/committers-guide.html#_release_to_maven_central[release guide].
diff --git a/antora/components/toc/modules/devguide/pages/hints-and-tips/how-run-fixtures-on-app-startup.adoc b/antora/components/toc/modules/devguide/pages/hints-and-tips/how-run-fixtures-on-app-startup.adoc
index f2b4719..993f08a 100644
--- a/antora/components/toc/modules/devguide/pages/hints-and-tips/how-run-fixtures-on-app-startup.adoc
+++ b/antora/components/toc/modules/devguide/pages/hints-and-tips/how-run-fixtures-on-app-startup.adoc
@@ -18,7 +18,7 @@ These can be run in on start-up typically by being specified in the xref:rg:cms:
Alternatively just set `isis.fixtures` and `isis.persistor.datanucleus.install-fixtures` properties.
-In terms of implementations, you might also want to check out the (non-ASF) link:http://platform.incode.org[Incode Platform^]'s excel module, by using `ExcelFixture` and overriding `ExcelFixtureRowHandler`.
+In terms of implementations, you might also want to check out the (non-ASF) link:https://platform.incode.org[Incode Platform^]'s excel module, by using `ExcelFixture` and overriding `ExcelFixtureRowHandler`.
An example can be found in this (non ASF) link:https://github.com/incodehq/contactapp[contactapp], see link:https://github.com/incodehq/contactapp/blob/master/backend/fixture/src/main/java/org/incode/eurocommercial/contactapp/fixture/scenarios/demo/ContactImport.java[`ContactRowHandler`].
diff --git a/antora/components/toc/modules/devguide/pages/working-with-many-repos.adoc b/antora/components/toc/modules/devguide/pages/working-with-many-repos.adoc
index 4f5faf4..f49968e 100644
--- a/antora/components/toc/modules/devguide/pages/working-with-many-repos.adoc
+++ b/antora/components/toc/modules/devguide/pages/working-with-many-repos.adoc
@@ -7,7 +7,7 @@ include::_attributes.adoc[]
Applications built with Apache Isis often (should) consist of multiple modules.
-For example, there are the various modules that make up the (non-ASF) link:http://platform.incode.org[Incode Platform^] that provide various technical/cross-cutting concerns and generic business functionality.
+For example, there are the various modules that make up the (non-ASF) link:https://platform.incode.org[Incode Platform^] that provide various technical/cross-cutting concerns and generic business functionality.
In addition, your own application may well be structured as a number of distinct modules (probably with the entities in each module being mapped to a different schema), and using such techniques as the xref:ug:fun:building-blocks.adoc#domain-events[event bus] and xref:ug:fun:building-blocks.adoc#mixins[mixins] so that these modules are decoupled from each other.
diff --git a/core/_adoc-rg/modules/ant/pages/Action/command.adoc b/core/_adoc-rg/modules/ant/pages/Action/command.adoc
index 3137847..308dca0 100644
--- a/core/_adoc-rg/modules/ant/pages/Action/command.adoc
+++ b/core/_adoc-rg/modules/ant/pages/Action/command.adoc
@@ -9,7 +9,7 @@ The primary use cases for this are to support the deferring the execution of the
Note that for a `Command` to actually be persisted requires an appropriate implementation of `CommandService` SPI.
The framework does _not_ provide an implementation of this SPI "out-of-the-box".
-However, the (non-ASF) Incode Platform's link:http://platform.incode.org/modules/spi/command/spi-command.html[ command module]) _does_ provide such an implementation.
+However, the (non-ASF) Incode Platform's link:https://platform.incode.org/modules/spi/command/spi-command.html[ command module]) _does_ provide such an implementation.
== Design
@@ -24,10 +24,10 @@ The annotation works with (and is influenced by the behaviour of) a number of do
Each action invocation is automatically reified by the xref:rg:svc:application-layer-api/CommandContext.adoc[`CommandContext`] service into a `Command` object, capturing details of the target object, the action, the parameter arguments, the user, a timestamp and so on.
-If an appropriate `CommandService` is configured (for example using (non-ASF) link:http://platform.incode.org/modules/spi/command/spi-command.html[Incode Platform's command] module), then the `Command` itself is persisted.
+If an appropriate `CommandService` is configured (for example using (non-ASF) link:https://platform.incode.org/modules/spi/command/spi-command.html[Incode Platform's command] module), then the `Command` itself is persisted.
By default, actions are invoked in directly in the thread of the invocation.
-If there is an implementation of `BackgroundCommandService` (as the (non-ASF) link:http://platform.incode.org[Incode Platform^]'s command module does provide), then this means in turn that the `BackgroundService` can be used by the domain object code to programmatically create background ``Command``s.
+If there is an implementation of `BackgroundCommandService` (as the (non-ASF) link:https://platform.incode.org[Incode Platform^]'s command module does provide), then this means in turn that the `BackgroundService` can be used by the domain object code to programmatically create background ``Command``s.
[NOTE]
====
diff --git a/core/_adoc-rg/modules/ant/pages/CollectionLayout.adoc b/core/_adoc-rg/modules/ant/pages/CollectionLayout.adoc
index 498e82b..140059c 100644
--- a/core/_adoc-rg/modules/ant/pages/CollectionLayout.adoc
+++ b/core/_adoc-rg/modules/ant/pages/CollectionLayout.adoc
@@ -26,7 +26,7 @@ The table below summarizes the annotation's attributes.
|`table`, `excel`, `calendar`, `map`, ...
|Which view is selected by default, if multiple views are available.
-See the (non-ASF) link:http://platform.incode.org[Incode Platform^] for further Wicket components providing views.
+See the (non-ASF) link:https://platform.incode.org[Incode Platform^] for further Wicket components providing views.
diff --git a/core/_adoc-rg/modules/ant/pages/CollectionLayout/defaultView.adoc b/core/_adoc-rg/modules/ant/pages/CollectionLayout/defaultView.adoc
index 1c6cb6e..9054fa9 100644
--- a/core/_adoc-rg/modules/ant/pages/CollectionLayout/defaultView.adoc
+++ b/core/_adoc-rg/modules/ant/pages/CollectionLayout/defaultView.adoc
@@ -3,7 +3,7 @@
include::_attributes.adoc[]
-The xref:vw:ROOT:about.adoc[Wicket viewer] allows additional views to be configured to render collections of objects; at the time of writing thesee include the excel, fullcalendar2 and gmap3 provided by the (non-ASF) link:http://platform.incode.org[Incode Platform^].
+The xref:vw:ROOT:about.adoc[Wicket viewer] allows additional views to be configured to render collections of objects; at the time of writing thesee include the excel, fullcalendar2 and gmap3 provided by the (non-ASF) link:https://platform.incode.org[Incode Platform^].
If the objects to be rendered have the correct "shape", then the appropriate view will be made available. For example, objects with a date can be rendered using `calendar`; objects with locations can be rendered using `map`.
The `defaultView()` attribute is used to select which of these views should be used by default for a given collection.
diff --git a/core/_adoc-rg/modules/ant/pages/Discriminator.adoc b/core/_adoc-rg/modules/ant/pages/Discriminator.adoc
index 6cb2a48..832532c 100644
--- a/core/_adoc-rg/modules/ant/pages/Discriminator.adoc
+++ b/core/_adoc-rg/modules/ant/pages/Discriminator.adoc
@@ -20,7 +20,7 @@ This can appear in several contexts, including:
* as the value of `Bookmark#getObjectType()` and in the `toString()` value of `Bookmark`
(see xref:rg:svc:integration-api/BookmarkService.adoc[`BookmarkService`])
- ** and thus in the "table-of-two-halves" pattern, as per the (non-ASF) link:http://platform.incode.org[Incode Platform^]'s poly module
+ ** and thus in the "table-of-two-halves" pattern, as per the (non-ASF) link:https://platform.incode.org[Incode Platform^]'s poly module
* in the serialization of `OidDto` in the xref:rg:cms:schema/cmd.adoc[command] and xref:rg:cms:schema/ixn.adoc[interaction] schemas
* in the URLs of the xref:vro:ROOT:about.adoc[RestfulObjects viewer]
* in the URLs of the xref:vw:ROOT:about.adoc[Wicket viewer] (in general and in particular if xref:vw:ROOT:features/hints-and-copy-url.adoc[copying URLs])
diff --git a/core/_adoc-rg/modules/ant/pages/DomainObject/objectType.adoc b/core/_adoc-rg/modules/ant/pages/DomainObject/objectType.adoc
index d9fb9d2..9b7ab44 100644
--- a/core/_adoc-rg/modules/ant/pages/DomainObject/objectType.adoc
+++ b/core/_adoc-rg/modules/ant/pages/DomainObject/objectType.adoc
@@ -10,7 +10,7 @@ This can appear in several contexts, including:
* as the value of `Bookmark#getObjectType()` and in the `toString()` value of `Bookmark`
(see xref:rg:svc:integration-api/BookmarkService.adoc[`BookmarkService`])
-** and thus in the "table-of-two-halves" pattern, as per the (non-ASF) link:http://platform.incode.org[Incode Platform^]'s poly module
+** and thus in the "table-of-two-halves" pattern, as per the (non-ASF) link:https://platform.incode.org[Incode Platform^]'s poly module
* in the serialization of `OidDto` in the xref:rg:cms:schema/cmd.adoc[command] and xref:rg:cms:schema/ixn.adoc[interaction] schemas
* in the URLs of the xref:vro:ROOT:about.adoc[RestfulObjects viewer]
* in the URLs of the xref:vw:ROOT:about.adoc[Wicket viewer] (in general and in particular if xref:vw:ROOT:features/hints-and-copy-url.adoc[copying URLs])
diff --git a/core/_adoc-rg/modules/ant/pages/DomainService/nature.adoc b/core/_adoc-rg/modules/ant/pages/DomainService/nature.adoc
index dab0ddf..087c21d 100644
--- a/core/_adoc-rg/modules/ant/pages/DomainService/nature.adoc
+++ b/core/_adoc-rg/modules/ant/pages/DomainService/nature.adoc
@@ -34,7 +34,7 @@ The service and its actions are only intended to be invoked programmatically; th
The actual class name of the domain service is only rendered for the `VIEW`, `VIEW_MENU_ONLY` and `VIEW_REST_ONLY` natures.
Thus, you might also want to adopt naming conventions for your domain classes so you can infer the nature from the class.
-For example, the naming convention adopted (by and large) by the (non-ASF) link:http://platform.incode.org[Incode Platform^] is `ProgrammaticServices` or `Repository` as a suffix for `DOMAIN` services, and `Contributions` as a suffix for `VIEW_CONTRIBUTIONS_ONLY` services.
+For example, the naming convention adopted (by and large) by the (non-ASF) link:https://platform.incode.org[Incode Platform^] is `ProgrammaticServices` or `Repository` as a suffix for `DOMAIN` services, and `Contributions` as a suffix for `VIEW_CONTRIBUTIONS_ONLY` services.
For example:
diff --git a/core/_adoc-rg/modules/ant/pages/Inject.adoc b/core/_adoc-rg/modules/ant/pages/Inject.adoc
index ed76442..57a55e8 100644
--- a/core/_adoc-rg/modules/ant/pages/Inject.adoc
+++ b/core/_adoc-rg/modules/ant/pages/Inject.adoc
@@ -95,7 +95,7 @@ public class Customer {
[NOTE]
====
An alternative and almost equivalent design would be to publish an event using the xref:rg:svc:core-domain-api/EventBusService.adoc[`EventBusService`] and implement the domain services as subscribers to the event.
-This alternative design is used in the (non-ASF) link:http://platform.incode.org[Incode Platform^]'s poly module, for example.
+This alternative design is used in the (non-ASF) link:https://platform.incode.org[Incode Platform^]'s poly module, for example.
====
diff --git a/core/_adoc-rg/modules/ant/pages/Parameter/fileAccept.adoc b/core/_adoc-rg/modules/ant/pages/Parameter/fileAccept.adoc
index 18bdaa8..5039d9c 100644
--- a/core/_adoc-rg/modules/ant/pages/Parameter/fileAccept.adoc
+++ b/core/_adoc-rg/modules/ant/pages/Parameter/fileAccept.adoc
@@ -24,7 +24,7 @@ public class Scanner {
<1> as per link:http://www.w3schools.com/tags/att_input_accept.asp[reference docs], either a media type (such as
`image/*`) or a file type extension (such as `.png`).
<2> the `@ParameterLayout(named=...)` attribute is required for Java 7; for Java 8 it can be omitted if the
-(non-ASF) link:http://platform.incode.org[Incode Platform^]'s paraname8 metamodel extension is used.
+(non-ASF) link:https://platform.incode.org[Incode Platform^]'s paraname8 metamodel extension is used.
diff --git a/core/_adoc-rg/modules/ant/pages/Parameter/maxLength.adoc b/core/_adoc-rg/modules/ant/pages/Parameter/maxLength.adoc
index d92d8d7..df15e3d 100644
--- a/core/_adoc-rg/modules/ant/pages/Parameter/maxLength.adoc
+++ b/core/_adoc-rg/modules/ant/pages/Parameter/maxLength.adoc
@@ -23,7 +23,7 @@ public class CustomerRepository {
}
}
----
-<1> the `@ParameterLayout(named=...)` attribute is required for Java 7; for Java 8 it can be omitted if the (non-ASF) link:http://platform.incode.org[Incode Platform^]'s paraname8 metamodel extension is used.
+<1> the `@ParameterLayout(named=...)` attribute is required for Java 7; for Java 8 it can be omitted if the (non-ASF) link:https://platform.incode.org[Incode Platform^]'s paraname8 metamodel extension is used.
diff --git a/core/_adoc-rg/modules/ant/pages/ParameterLayout/named.adoc b/core/_adoc-rg/modules/ant/pages/ParameterLayout/named.adoc
index bd1335a..8870a7b 100644
--- a/core/_adoc-rg/modules/ant/pages/ParameterLayout/named.adoc
+++ b/core/_adoc-rg/modules/ant/pages/ParameterLayout/named.adoc
@@ -12,7 +12,7 @@ This can be sufficient for application-specific reference types (eg `ToDoItem`)
The `named()` attribute is therefore often required to specify the parameter name.
As of Java 8, the Java reflection API has been extended.
-The (non-ASF) link:http://platform.incode.org[Incode Platform^]'s paraname8 metamodel extension provides support for this.
+The (non-ASF) link:https://platform.incode.org[Incode Platform^]'s paraname8 metamodel extension provides support for this.
Note that your application must (obviously) be running on Java 8, and be compiled with the `-parameters` compile flag for javac.
diff --git a/core/_adoc-rg/modules/ant/pages/PersistenceCapable.adoc b/core/_adoc-rg/modules/ant/pages/PersistenceCapable.adoc
index 70744b8..11bcc62 100644
--- a/core/_adoc-rg/modules/ant/pages/PersistenceCapable.adoc
+++ b/core/_adoc-rg/modules/ant/pages/PersistenceCapable.adoc
@@ -21,7 +21,7 @@ This can appear in several contexts, including:
* as the value of `Bookmark#getObjectType()` and in the `toString()` value of `Bookmark`
(see xref:rg:svc:integration-api/BookmarkService.adoc[`BookmarkService`])
- ** and thus in the "table-of-two-halves" pattern, as per the (non-ASF) link:http://platform.incode.org[Incode Platform^]'s poly module
+ ** and thus in the "table-of-two-halves" pattern, as per the (non-ASF) link:https://platform.incode.org[Incode Platform^]'s poly module
* in the serialization of `OidDto` in the xref:rg:cms:schema/cmd.adoc[command] and xref:rg:cms:schema/ixn.adoc[interaction] schemas
* in the URLs of the xref:vro:ROOT:about.adoc[RestfulObjects viewer]
* in the URLs of the xref:vw:ROOT:about.adoc[Wicket viewer] (in general and in particular if xref:vw:ROOT:features/hints-and-copy-url.adoc[copying URLs])
diff --git a/core/_adoc-rg/modules/ant/pages/Property/command.adoc b/core/_adoc-rg/modules/ant/pages/Property/command.adoc
index 2022ab0..ca6ff87 100644
--- a/core/_adoc-rg/modules/ant/pages/Property/command.adoc
+++ b/core/_adoc-rg/modules/ant/pages/Property/command.adoc
@@ -20,10 +20,10 @@ The annotation works with (and is influenced by the behaviour of) a number of do
Each property edit is automatically reified by the xref:rg:svc:application-layer-api/CommandContext.adoc[`CommandContext`] service into a `Command` object, capturing details of the target object, the property, the proposed new value fo the property, the user, a timestamp and so on.
-If an appropriate `CommandService` is configured (for example using (non-ASF) link:http://platform.incode.org/modules/spi/command/spi-command.html[Incode Platform's command] module), then the `Command` itself is persisted.
+If an appropriate `CommandService` is configured (for example using (non-ASF) link:https://platform.incode.org/modules/spi/command/spi-command.html[Incode Platform's command] module), then the `Command` itself is persisted.
By default, actions are invoked in directly in the thread of the invocation.
-If there is an implementation of `BackgroundCommandService` (as the (non-ASF) link:http://platform.incode.org[Incode Platform^]'s command module does provide), then this means in turn that the `BackgroundService` can be used by the domain object code to programmatically create background ``Command``s.
+If there is an implementation of `BackgroundCommandService` (as the (non-ASF) link:https://platform.incode.org[Incode Platform^]'s command module does provide), then this means in turn that the `BackgroundService` can be used by the domain object code to programmatically create background ``Command``s.
[NOTE]
====
diff --git a/core/_adoc-rg/modules/ant/pages/ViewModel/objectType.adoc b/core/_adoc-rg/modules/ant/pages/ViewModel/objectType.adoc
index eb99c44..f430c32 100644
--- a/core/_adoc-rg/modules/ant/pages/ViewModel/objectType.adoc
+++ b/core/_adoc-rg/modules/ant/pages/ViewModel/objectType.adoc
@@ -10,7 +10,7 @@ This can appear in several contexts, including:
* as the value of `Bookmark#getObjectType()` and in the `toString()` value of `Bookmark`
(see xref:rg:svc:integration-api/BookmarkService.adoc[`BookmarkService`])
- ** and thus in the "table-of-two-halves" pattern, as per the (non-ASF) link:http://platform.incode.org[Incode Platform^]'s poly module
+ ** and thus in the "table-of-two-halves" pattern, as per the (non-ASF) link:https://platform.incode.org[Incode Platform^]'s poly module
* in the serialization of `OidDto` in the xref:rg:cms:schema/cmd.adoc[command] and xref:rg:cms:schema/ixn.adoc[interaction] schemas
* in the URLs of the xref:vro:ROOT:about.adoc[RestfulObjects viewer]
* in the URLs of the xref:vw:ROOT:about.adoc[Wicket viewer] (in general and in particular if xref:vw:ROOT:features/hints-and-copy-url.adoc[copying URLs])
diff --git a/core/_adoc-rg/modules/cfg/pages/configuring-core.adoc b/core/_adoc-rg/modules/cfg/pages/configuring-core.adoc
index 6cf237b..5ba53fe 100644
--- a/core/_adoc-rg/modules/cfg/pages/configuring-core.adoc
+++ b/core/_adoc-rg/modules/cfg/pages/configuring-core.adoc
@@ -695,7 +695,7 @@ If an parent object has a (scalar) reference some other object to which the user
+
If an object is returned in a list of choices or within an auto-complete list, and the user does not have access, then it is excluded from the rendered list.
-The original motivation for this feature was to transparently support such features as multi-tenancy (as per the (non-ASF) link:http://platform.incode.org[Incode Platform^]'s security module).
+The original motivation for this feature was to transparently support such features as multi-tenancy (as per the (non-ASF) link:https://platform.incode.org[Incode Platform^]'s security module).
That is, if an entity is logically "owned" by a user, then the multi-tenancy support can be arranged to prevent some other user from viewing that object.
By default this configuration property is enabled. To disable the visibility filtering, set the appropriate configuration property to `false`:
diff --git a/core/_adoc-rg/modules/cms/pages/classes/AppManifest-bootstrapping.adoc b/core/_adoc-rg/modules/cms/pages/classes/AppManifest-bootstrapping.adoc
index 82a4f90..1e8d35c 100644
--- a/core/_adoc-rg/modules/cms/pages/classes/AppManifest-bootstrapping.adoc
+++ b/core/_adoc-rg/modules/cms/pages/classes/AppManifest-bootstrapping.adoc
@@ -86,7 +86,7 @@ public List<Class<?>> getModules() {
}
----
-As can be seen, the various (non-ASF) link:http://platform.incode.org[Incode Platform^] modules also each provide a module class that can be easily referenced.
+As can be seen, the various (non-ASF) link:https://platform.incode.org[Incode Platform^] modules also each provide a module class that can be easily referenced.
=== `getAdditionalServices()`
@@ -94,7 +94,7 @@ As can be seen, the various (non-ASF) link:http://platform.incode.org[Incode Pla
We normally we recommend that services are defined exclusively through `getModules()`, and that this method should therefore return an empty list.
However, there are certain use cases where the a service must be explicitly specified either because the service required does not (for whatever reason) have a xref:rg:ant:DomainService.adoc[`@DomainService`] annotation.
-For example, the (non-ASF) link:http://platform.incode.org[Incode Platform^]'s security module allows the policy to evaluate conflicting permissions to be specified by explicitly registering either the `PermissionsEvaluationServiceAllowBeatsVeto` domain service or the `PermissionsEvaluationServiceVetoBeatsAllow` domain service:
+For example, the (non-ASF) link:https://platform.incode.org[Incode Platform^]'s security module allows the policy to evaluate conflicting permissions to be specified by explicitly registering either the `PermissionsEvaluationServiceAllowBeatsVeto` domain service or the `PermissionsEvaluationServiceVetoBeatsAllow` domain service:
[source,java]
----
diff --git a/core/_adoc-rg/modules/cms/pages/classes/contributee/HasTransactionId.adoc b/core/_adoc-rg/modules/cms/pages/classes/contributee/HasTransactionId.adoc
index 6a9bbb8..68bf451 100644
--- a/core/_adoc-rg/modules/cms/pages/classes/contributee/HasTransactionId.adoc
+++ b/core/_adoc-rg/modules/cms/pages/classes/contributee/HasTransactionId.adoc
@@ -23,7 +23,7 @@ public interface HasTransactionId {
<1> unique identifier (a GUID) of this request/interaction.
-Modules in the (non-ASF) link:http://platform.incode.org[Incode Platform^] that have domain entity/ies that implement this interface, and/or services that contribute this interface are:
+Modules in the (non-ASF) link:https://platform.incode.org[Incode Platform^] that have domain entity/ies that implement this interface, and/or services that contribute this interface are:
* audit module: `AuditEntry` entity, `AuditingServiceContributions` service
* command module: `CommandJdo` entity, `CommandServiceJdoContributions` service
diff --git a/core/_adoc-rg/modules/cms/pages/classes/contributee/HasUserName.adoc b/core/_adoc-rg/modules/cms/pages/classes/contributee/HasUserName.adoc
index 90b35b9..3a2b9a6 100644
--- a/core/_adoc-rg/modules/cms/pages/classes/contributee/HasUserName.adoc
+++ b/core/_adoc-rg/modules/cms/pages/classes/contributee/HasUserName.adoc
@@ -15,7 +15,7 @@ public interface HasUsername {
}
----
-Modules in the (non-ASF) link:http://platform.incode.org[Incode Platform^] that either have domain entity that implement and/or services that contribute this interface are:
+Modules in the (non-ASF) link:https://platform.incode.org[Incode Platform^] that either have domain entity that implement and/or services that contribute this interface are:
* security module: `ApplicationUser` entity, `HasUsernameContributions` service
* audit module: `AuditEntry` entity
diff --git a/core/_adoc-rg/modules/cms/pages/classes/super/AbstractSubscriber.adoc b/core/_adoc-rg/modules/cms/pages/classes/super/AbstractSubscriber.adoc
index 1b68d88..3f8de63 100644
--- a/core/_adoc-rg/modules/cms/pages/classes/super/AbstractSubscriber.adoc
+++ b/core/_adoc-rg/modules/cms/pages/classes/super/AbstractSubscriber.adoc
@@ -7,7 +7,7 @@ This is a convenience superclass for creating subscriber domain services on the
It uses xref:rg:ant:PostConstruct.adoc[`@PostConstruct`] and xref:rg:ant:PreDestroy.adoc[`@PreDestroy`] callbacks to automatically register/unregister itself with the `EventBusService`.
It's important that subscribers register before any domain services that might emit events on the xref:rg:svc:core-domain-api/EventBusService.adoc[`EventBusService`].
-For example, the (non-ASF) link:http://platform.incode.org[Incode Platform^] security module provides a domain service that automatically seeds certain domain entities; these will generate xref:rg:cms:classes/lifecycleevent.adoc[lifecycle events] and so any subscribers must be registered before such seed services.
+For example, the (non-ASF) link:https://platform.incode.org[Incode Platform^] security module provides a domain service that automatically seeds certain domain entities; these will generate xref:rg:cms:classes/lifecycleevent.adoc[lifecycle events] and so any subscribers must be registered before such seed services.
The easiest way to do this is to use the xref:rg:ant:DomainServiceLayout/menuOrder.adoc[`@DomainServiceLayout#menuOrder()`] attribute.
As a convenience, the `AbstractSubscriber` specifies this attribute.
\ No newline at end of file
diff --git a/core/_adoc-rg/modules/cms/pages/schema.adoc b/core/_adoc-rg/modules/cms/pages/schema.adoc
index faf64d7..e8f5f43 100644
--- a/core/_adoc-rg/modules/cms/pages/schema.adoc
+++ b/core/_adoc-rg/modules/cms/pages/schema.adoc
@@ -20,7 +20,7 @@ created, updated or deleted as the result of an execution of an action invocatio
These each use XSD types defined by the xref:rg:cms:schema/common.adoc[common schema] (most notably the `oidDto`
complex type which identifies a domain object).
-The (non-ASF) link:http://platform.incode.org[Incode Platform^]'s command and publishmq modules use these schemas to reify
+The (non-ASF) link:https://platform.incode.org[Incode Platform^]'s command and publishmq modules use these schemas to reify
corresponding applib objects (`Command`, `Interaction.Execution` and `PublishedObjects`), either to persist or publishing using an link:http://activemq.apache.org[Apache ActiveMQ] message queue.
The sections below discuss these schemas in more detail.
diff --git a/core/_adoc-rg/modules/fis/pages/application-layer.adoc b/core/_adoc-rg/modules/fis/pages/application-layer.adoc
index 688ef0e..edea2fb 100644
--- a/core/_adoc-rg/modules/fis/pages/application-layer.adoc
+++ b/core/_adoc-rg/modules/fis/pages/application-layer.adoc
@@ -7,7 +7,7 @@ include::_attributes.adoc[]
These domain services are internal to the framework, controlling various aspects of the application layer.
The table below summarizes the application layer internal SPIs defined by Apache Isis.
-It also lists their corresponding implementation, either a default implementation provided by Apache Isis itself, or provided by one of the (non-ASF) link:http://platform.incode.org[Incode Platform^] modules.
+It also lists their corresponding implementation, either a default implementation provided by Apache Isis itself, or provided by one of the (non-ASF) link:https://platform.incode.org[Incode Platform^] modules.
diff --git a/core/_adoc-rg/modules/fis/pages/persistence-layer.adoc b/core/_adoc-rg/modules/fis/pages/persistence-layer.adoc
index e94ab21..3f110f6 100644
--- a/core/_adoc-rg/modules/fis/pages/persistence-layer.adoc
+++ b/core/_adoc-rg/modules/fis/pages/persistence-layer.adoc
@@ -8,7 +8,7 @@ These domain services are internal to the framework, controlling various aspects
The table below summarizes the persistence layer internal SPIs defined by Apache Isis.
-It also lists their corresponding implementation, either a default implementation provided by Apache Isis itself, or provided by one of the (non-ASF) link:http://platform.incode.org[Incode Platform^] modules.
+It also lists their corresponding implementation, either a default implementation provided by Apache Isis itself, or provided by one of the (non-ASF) link:https://platform.incode.org[Incode Platform^] modules.
diff --git a/core/_adoc-rg/modules/fis/pages/presentation-layer.adoc b/core/_adoc-rg/modules/fis/pages/presentation-layer.adoc
index 5234005..2d8ebca 100644
--- a/core/_adoc-rg/modules/fis/pages/presentation-layer.adoc
+++ b/core/_adoc-rg/modules/fis/pages/presentation-layer.adoc
@@ -9,7 +9,7 @@ These domain services are internal to the framework, controlling various aspects
The table below summarizes the presentation layer internal SPIs defined by Apache Isis.
-It also lists their corresponding implementation, either a default implementation provided by Apache Isis itself, or provided by one of the (non-ASF) link:http://platform.incode.org[Incode Platform^] modules.
+It also lists their corresponding implementation, either a default implementation provided by Apache Isis itself, or provided by one of the (non-ASF) link:https://platform.incode.org[Incode Platform^] modules.
diff --git a/core/_adoc-rg/modules/svc/pages/application-layer-api.adoc b/core/_adoc-rg/modules/svc/pages/application-layer-api.adoc
index a59e027..12e7854 100644
--- a/core/_adoc-rg/modules/svc/pages/application-layer-api.adoc
+++ b/core/_adoc-rg/modules/svc/pages/application-layer-api.adoc
@@ -8,7 +8,7 @@ Domain service APIs for the application layer allow the domain objects to contro
The table below summarizes the application layer APIs defined by Apache Isis.
-It also lists their corresponding implementation, either a default implementation provided by Apache Isis itself, or provided by one of the (non-ASF) link:http://platform.incode.org[Incode Platform^] modules.
+It also lists their corresponding implementation, either a default implementation provided by Apache Isis itself, or provided by one of the (non-ASF) link:https://platform.incode.org[Incode Platform^] modules.
.Application Layer API
[cols="2,4a,1,1", options="header"]
diff --git a/core/_adoc-rg/modules/svc/pages/application-layer-api/BackgroundService.adoc b/core/_adoc-rg/modules/svc/pages/application-layer-api/BackgroundService.adoc
index 5cdee56..f9dbd70 100644
--- a/core/_adoc-rg/modules/svc/pages/application-layer-api/BackgroundService.adoc
+++ b/core/_adoc-rg/modules/svc/pages/application-layer-api/BackgroundService.adoc
@@ -78,7 +78,7 @@ One could imagine more complex designs where only the final command executed not
However, an alternative is to rely on the fact that the `BackgroundService` will automatically hint that the `Command` representing the original interaction (to `submitCustomerInvoices()` in the example above) should be persisted.
This will be available if the related xref:rg:svc:application-layer-api/CommandContext.adoc[`CommandContext`] and xref:rg:svc:application-layer-spi/CommandService.adoc[`CommandService`] domain services are configured, and the `CommandService` supports persistent commands.
-Note that (non-ASF) link:http://platform.incode.org[Incode Platform^]'s command module does indeed provide such an implementation of `CommandService` (as well as of the required `BackgroundCommandService`).
+Note that (non-ASF) link:https://platform.incode.org[Incode Platform^]'s command module does indeed provide such an implementation of `CommandService` (as well as of the required `BackgroundCommandService`).
Thus, the original action can run a query to obtain it corresponding `Command`, and return this to the user.
The upshot is that the child ``Command``s created by the `BackgroundService` will then be associated with `Command` for the original action.
@@ -111,7 +111,7 @@ The `CommandContext` service is responsible for providing a parent `Command` wit
The latter is analogous to the way in which the `BackgroundCommandService` persists the child background `Command`s.
The implementations of `CommandService` and `BackgroundCommandService` go together; typically both parent `Command`s and child background `Command`s will be persisted in the same way.
-The (non-ASF) link:http://platform.incode.org[Incode Platform^]'s command module provides implementations of both (see xref:rg:svc:application-layer-spi/CommandService.adoc[`CommandService`] and xref:rg:svc:application-layer-spi/BackgroundCommandService.adoc[`BackgroundCommandService`]).
+The (non-ASF) link:https://platform.incode.org[Incode Platform^]'s command module provides implementations of both (see xref:rg:svc:application-layer-spi/CommandService.adoc[`CommandService`] and xref:rg:svc:application-layer-spi/BackgroundCommandService.adoc[`BackgroundCommandService`]).
The xref:rg:fis:application-layer/CommandDtoServiceInternal.adoc[`CommandDtoServiceInternal`] is used to obtain a memento of the command such that it can be persisted.
(In earlier versions, xref:rg:svc:integration-api/MementoService.adoc[`MementoService`] was used for this purpose).
diff --git a/core/_adoc-rg/modules/svc/pages/application-layer-api/BackgroundService/Quartz.adoc b/core/_adoc-rg/modules/svc/pages/application-layer-api/BackgroundService/Quartz.adoc
index 0bcba4a..a4289f5 100644
--- a/core/_adoc-rg/modules/svc/pages/application-layer-api/BackgroundService/Quartz.adoc
+++ b/core/_adoc-rg/modules/svc/pages/application-layer-api/BackgroundService/Quartz.adoc
@@ -8,7 +8,7 @@ The last part of the puzzle is to actually run the (appropriate implementation o
This could be run in a batch job overnight, or run continually by, say, the http://quartz-scheduler.org[Quartz] scheduler or by link:http://camel.apache.org[Apache Camel].
This section looks at configuring Quartz.
-If using (non-ASF) link:http://platform.incode.org[Incode Platform^]'s command module, then note that this already provides a suitable concrete implementation, namely `org.isisaddons.module.command.dom.BackgroundCommandExecutionFromBackgroundCommandServiceJdo`.
+If using (non-ASF) link:https://platform.incode.org[Incode Platform^]'s command module, then note that this already provides a suitable concrete implementation, namely `org.isisaddons.module.command.dom.BackgroundCommandExecutionFromBackgroundCommandServiceJdo`.
We therefore just need to schedule this to run as a Quartz job.
diff --git a/core/_adoc-rg/modules/svc/pages/application-layer-api/CommandContext.adoc b/core/_adoc-rg/modules/svc/pages/application-layer-api/CommandContext.adoc
index a991e1b..95c51c2 100644
--- a/core/_adoc-rg/modules/svc/pages/application-layer-api/CommandContext.adoc
+++ b/core/_adoc-rg/modules/svc/pages/application-layer-api/CommandContext.adoc
@@ -8,7 +8,7 @@ The `CommandContext` service is a xref:rg:ant:RequestScoped.adoc[request-scoped]
By default, the `Command` is held in-memory only; once the action invocation has completed, the `Command` object is gone.
The optional supporting xref:rg:svc:application-layer-spi/CommandService.adoc[`CommandService`] enables the implementation of `Command` to be pluggable.
-With an appropriate implementation (eg as provided by the (non-ASF) link:http://platform.incode.org[Incode Platform^]'s command module's xref:rg:svc:application-layer-spi/CommandService.adoc[`CommandService`]) the `Command` may then be persisted.
+With an appropriate implementation (eg as provided by the (non-ASF) link:https://platform.incode.org[Incode Platform^]'s command module's xref:rg:svc:application-layer-spi/CommandService.adoc[`CommandService`]) the `Command` may then be persisted.
The primary use case for persistent ``Command``s is in support of background commands; they act as a parent to any background commands that can be persisted either explicitly using the xref:rg:svc:application-layer-api/BackgroundService.adoc[`BackgroundService`], or implicitly by way of the xref:rg:ant:Action/command.adoc[`@Action#command()`] annotation.
@@ -18,7 +18,7 @@ There are a number of related use cases:
* if a xref:rg:svc:persistence-layer-spi/PublisherService.adoc[`PublisherService`] is configured, they provide better traceability as the `Command` is also correlated with any published events, again through the unique `transactionId` GUID
* if a xref:rg:svc:spi/AuderService.adoc[`AuditerService`] 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) through the `transactionId` GUID
-However, while persistent ``Command``s _can_ be used for these use cases, it is recommended instead to use the xref:rg:svc:application-layer-api/InteractionContext.adoc[`InteractionContext`] service and persistent implementations of the ``Interaction`` object, eg as provided by the (non-ASF) link:http://platform.incode.org[Incode Platform^]'s publishmq module.
+However, while persistent ``Command``s _can_ be used for these use cases, it is recommended instead to use the xref:rg:svc:application-layer-api/InteractionContext.adoc[`InteractionContext`] service and persistent implementations of the ``Interaction`` object, eg as provided by the (non-ASF) link:https://platform.incode.org[Incode Platform^]'s publishmq module.
@@ -150,7 +150,7 @@ public class ToDoItem ... {
When a background command is invoked, the user is returned the command object itself (to provide a handle to the command being invoked).
-This requires that an implementation of xref:rg:svc:application-layer-spi/CommandService.adoc[`CommandService`] that persists the commands (such as the (non-ASF) link:http://platform.incode.org[Incode Platform^]'s command module's `CommandService`) is configured.
+This requires that an implementation of xref:rg:svc:application-layer-spi/CommandService.adoc[`CommandService`] that persists the commands (such as the (non-ASF) link:https://platform.incode.org[Incode Platform^]'s command module's `CommandService`) is configured.
It also requires that a scheduler is configured to execute the background commands, see xref:rg:svc:application-layer-spi/BackgroundCommandService.adoc[`BackgroundCommandService`]).
diff --git a/core/_adoc-rg/modules/svc/pages/application-layer-api/CommandExecutorService.adoc b/core/_adoc-rg/modules/svc/pages/application-layer-api/CommandExecutorService.adoc
index 069bd3e..1da5872 100644
--- a/core/_adoc-rg/modules/svc/pages/application-layer-api/CommandExecutorService.adoc
+++ b/core/_adoc-rg/modules/svc/pages/application-layer-api/CommandExecutorService.adoc
@@ -10,7 +10,7 @@ In fact, the service requires that the implementation of the `Command` being exe
This allows the xref:rg:cms:schema/cmd.adoc[`CommandDto`] memento to be extracted, from which the action can be invoked/property edited.
The primary use case for this service is to allow the replay of commands, eg for regression testing.
-This is implemented by the (non-ASF) link:http://platform.incode.org/modules/spi/command/spi-command-replay.html[command replay module].
+This is implemented by the (non-ASF) link:https://platform.incode.org/modules/spi/command/spi-command-replay.html[command replay module].
(The command replay module also provides a decorator implementation of this service that allows the command to be re-executed at the same _time_ as the original command, leveraging the `TickingClock` implementation provided by the framework).
diff --git a/core/_adoc-rg/modules/svc/pages/application-layer-api/InteractionContext.adoc b/core/_adoc-rg/modules/svc/pages/application-layer-api/InteractionContext.adoc
index 08726e9..388be58 100644
--- a/core/_adoc-rg/modules/svc/pages/application-layer-api/InteractionContext.adoc
+++ b/core/_adoc-rg/modules/svc/pages/application-layer-api/InteractionContext.adoc
@@ -17,7 +17,7 @@ xref:rg:ant:Action/invokeOn.adoc[`@Action#invokeOn()`]), then this will result i
per selected object (not one `Interaction` with multiple top-level ``Execution``s).
-It is possible for ``Interaction.Execution``s to be persisted; this is supported by the (non-ASF) link:http://platform.incode.org[Incode Platform^]'s publishmq module, for example. Persistent
+It is possible for ``Interaction.Execution``s to be persisted; this is supported by the (non-ASF) link:https://platform.incode.org[Incode Platform^]'s publishmq module, for example. Persistent
``Interaction``s support several use cases:
* they enable profiling of the running application (which actions are invoked then most often, what is their response
diff --git a/core/_adoc-rg/modules/svc/pages/application-layer-spi.adoc b/core/_adoc-rg/modules/svc/pages/application-layer-spi.adoc
index 1c2c902..19b3801 100644
--- a/core/_adoc-rg/modules/svc/pages/application-layer-spi.adoc
+++ b/core/_adoc-rg/modules/svc/pages/application-layer-spi.adoc
@@ -7,7 +7,7 @@ Domain service SPIs influence how the framework handles application layer concer
The table below summarizes the application layer SPIs defined by Apache Isis.
-It also lists their corresponding implementation, either a default implementation provided by Apache Isis itself, or provided by one of the (non-ASF) link:http://platform.incode.org[Incode Platform^] modules.
+It also lists their corresponding implementation, either a default implementation provided by Apache Isis itself, or provided by one of the (non-ASF) link:https://platform.incode.org[Incode Platform^] modules.
.Application Layer SPI
[cols="2,4a,1,1", options="header"]
diff --git a/core/_adoc-rg/modules/svc/pages/application-layer-spi/BackgroundCommandService.adoc b/core/_adoc-rg/modules/svc/pages/application-layer-spi/BackgroundCommandService.adoc
index e2c75fc..be82dbe 100644
--- a/core/_adoc-rg/modules/svc/pages/application-layer-spi/BackgroundCommandService.adoc
+++ b/core/_adoc-rg/modules/svc/pages/application-layer-spi/BackgroundCommandService.adoc
@@ -55,7 +55,7 @@ The developer is required to implement this hook method in a subclass.
== Implementation
-The (non-ASF) link:http://platform.incode.org[Incode Platform^]'s command module provides an implementation (`org.isisaddons.module.command.dom.BackgroundCommandServiceJdo`) that persists ``Command``s using the JDO/DataNucleus object store.
+The (non-ASF) link:https://platform.incode.org[Incode Platform^]'s command module provides an implementation (`org.isisaddons.module.command.dom.BackgroundCommandServiceJdo`) that persists ``Command``s using the JDO/DataNucleus object store.
It further provides a number of supporting services:
* `org.isisaddons.module.command.dom.BackgroundCommandServiceJdoRepository` is a repository to search for persisted background ``Command``s
@@ -85,7 +85,7 @@ The imperative approach involves explicitly calling the xref:rg:svc:application-
== Alternative Implementations
-The (non-ASF) link:http://platform.incode.org[Incode Platform^]'s command module provides an implementation of this service (`BackgroundCommandService`), and also provides a number of related domain services (`BackgroundCommandServiceJdo`, `BackgroundCommandJdoRepository` and `BackgroundCommandServiceJdoContributions`).
+The (non-ASF) link:https://platform.incode.org[Incode Platform^]'s command module provides an implementation of this service (`BackgroundCommandService`), and also provides a number of related domain services (`BackgroundCommandServiceJdo`, `BackgroundCommandJdoRepository` and `BackgroundCommandServiceJdoContributions`).
This module also provides service implementations of the xref:rg:svc:application-layer-spi/CommandService.adoc[`CommandService`].
If contributions are not required in the UI, these can be suppressed either using security or by implementing a xref:ug:btb:hints-and-tips/vetoing-visibility.adoc[vetoing subscriber].
@@ -99,7 +99,7 @@ As discussed above, this service supports the xref:rg:svc:application-layer-api/
There is also a tie-up with the xref:rg:svc:application-layer-api/CommandContext.adoc[`CommandContext`] and its supporting xref:rg:svc:application-layer-spi/CommandService.adoc[`CommandService`] domain service. The `CommandContext` service is responsible for providing a parent `Command` with which the background `Command`s can then be associated as children, while the `CommandService` is responsible for persisting those parent `Command`s (analogous to the way in which the `BackgroundComm [...]
-What that means is that the implementations of `CommandService` and `BackgroundCommandService` go together, hence both implemented in the (non-ASF) link:http://platform.incode.org[Incode Platform^]'s command module.).
+What that means is that the implementations of `CommandService` and `BackgroundCommandService` go together, hence both implemented in the (non-ASF) link:https://platform.incode.org[Incode Platform^]'s command module.).
diff --git a/core/_adoc-rg/modules/svc/pages/application-layer-spi/CommandService.adoc b/core/_adoc-rg/modules/svc/pages/application-layer-spi/CommandService.adoc
index 62bfd7f..0f4bc08 100644
--- a/core/_adoc-rg/modules/svc/pages/application-layer-spi/CommandService.adoc
+++ b/core/_adoc-rg/modules/svc/pages/application-layer-spi/CommandService.adoc
@@ -23,7 +23,7 @@ better traceability as the `Command` is also correlated with any published event
information, since the `Command` (the 'cause' of an action) can be correlated to the audit records (the "effect" of
the action) through the `transactionId` GUID
-However, while persistent ``Command``s _can_ be used for these use cases, it is recommended instead to use the xref:rg:svc:application-layer-api/InteractionContext.adoc[`InteractionContext`] service and persistent implementations of the ``Interaction`` object, eg as provided by the (non-ASF) link:http://platform.incode.org[Incode Platform^]'s publishmq module.
+However, while persistent ``Command``s _can_ be used for these use cases, it is recommended instead to use the xref:rg:svc:application-layer-api/InteractionContext.adoc[`InteractionContext`] service and persistent implementations of the ``Interaction`` object, eg as provided by the (non-ASF) link:https://platform.incode.org[Incode Platform^]'s publishmq module.
@@ -64,7 +64,7 @@ The framework will automatically have set the `completedAt` property of the `Com
== Implementation
-The (non-ASF) link:http://platform.incode.org[Incode Platform^]'s command module provides an implementation (`org.isisaddons.module.command.dom.CommandServiceJdo`) that persists ``Command``s using the JDO/DataNucleus object store.
+The (non-ASF) link:https://platform.incode.org[Incode Platform^]'s command module provides an implementation (`org.isisaddons.module.command.dom.CommandServiceJdo`) that persists ``Command``s using the JDO/DataNucleus object store.
It further provides a number of supporting services:
* `org.isisaddons.module.command.dom.CommandServiceJdoRepository` is a repository to search for persisted ``Command``s
@@ -82,7 +82,7 @@ If contributions are not required in the UI, these can be suppressed either usin
== Alternative Implementations
-The (non-ASF) link:http://platform.incode.org[Incode Platform^]'s command module provides an implementation of this service (`CommandService`), and also provides a number of related domain services (`CommandJdoRepository` and `CommandServiceJdoContributions`).
+The (non-ASF) link:https://platform.incode.org[Incode Platform^]'s command module provides an implementation of this service (`CommandService`), and also provides a number of related domain services (`CommandJdoRepository` and `CommandServiceJdoContributions`).
This module also provides service implementations of the xref:rg:svc:application-layer-spi/CommandService.adoc[`BackgroundCommandService`].
If contributions are not required in the UI, these can be suppressed either using security or by implementing a xref:ug:btb:hints-and-tips/vetoing-visibility.adoc[vetoing subscriber].
diff --git a/core/_adoc-rg/modules/svc/pages/bootstrapping-spi.adoc b/core/_adoc-rg/modules/svc/pages/bootstrapping-spi.adoc
index 459b192..1049bd6 100644
--- a/core/_adoc-rg/modules/svc/pages/bootstrapping-spi.adoc
+++ b/core/_adoc-rg/modules/svc/pages/bootstrapping-spi.adoc
@@ -7,7 +7,7 @@ Bootstrapping SPIs influence how the framework locates the components that make
The table below summarizes the bootstrapping SPI defined by Apache Isis.
-It also lists their corresponding implementation, either a default implementation provided by Apache Isis itself, or provided by one of the (non-ASF) link:http://platform.incode.org[Incode Platform^] modules.
+It also lists their corresponding implementation, either a default implementation provided by Apache Isis itself, or provided by one of the (non-ASF) link:https://platform.incode.org[Incode Platform^] modules.
.Bootstrapping SPI
[cols="2,4a,1,1", options="header"]
diff --git a/core/_adoc-rg/modules/svc/pages/core-domain-api.adoc b/core/_adoc-rg/modules/svc/pages/core-domain-api.adoc
index d8a24d3..95f9d90 100644
--- a/core/_adoc-rg/modules/svc/pages/core-domain-api.adoc
+++ b/core/_adoc-rg/modules/svc/pages/core-domain-api.adoc
@@ -7,7 +7,7 @@ The core/domain APIs provide general-purpose services to the domain objects, for
The table below summarizes the core/domain APIs defined by Apache Isis.
-It also lists their corresponding implementation, either a default implementation provided by Apache Isis itself, or provided by one of the (non-ASF) link:http://platform.incode.org[Incode Platform^] modules.
+It also lists their corresponding implementation, either a default implementation provided by Apache Isis itself, or provided by one of the (non-ASF) link:https://platform.incode.org[Incode Platform^] modules.
.Core/Domain Layer API
diff --git a/core/_adoc-rg/modules/svc/pages/core-domain-api/EventBusService.adoc b/core/_adoc-rg/modules/svc/pages/core-domain-api/EventBusService.adoc
index 3ad4b09..82bceac 100644
--- a/core/_adoc-rg/modules/svc/pages/core-domain-api/EventBusService.adoc
+++ b/core/_adoc-rg/modules/svc/pages/core-domain-api/EventBusService.adoc
@@ -82,7 +82,7 @@ public class MySubscribingDomainService {
----
<1> subscribers are typically not visible in the UI, so specify a `DOMAIN` nature
<2> It's important that subscribers register before any domain services that might emit events on the event bus service.
-For example, the (non-ASF) link:http://platform.incode.org[Incode Platform^]'s security module provides a domain service that automatically seeds certain domain entities; these will generate xref:rg:cms:classes/lifecycleevent.adoc[lifecycle events] and so any subscribers must be registered before such seed services.
+For example, the (non-ASF) link:https://platform.incode.org[Incode Platform^]'s security module provides a domain service that automatically seeds certain domain entities; these will generate xref:rg:cms:classes/lifecycleevent.adoc[lifecycle events] and so any subscribers must be registered before such seed services.
The easiest way to do this is to use the xref:rg:ant:DomainServiceLayout/menuOrder.adoc[`@DomainServiceLayout#menuOrder()`] attribute.
<3> register with the event bus service during xref:rg:ant:PostConstruct.adoc[`@PostConstruct`]
initialization
diff --git a/core/_adoc-rg/modules/svc/pages/integration-api.adoc b/core/_adoc-rg/modules/svc/pages/integration-api.adoc
index 5549e67..c6b7bfa 100644
--- a/core/_adoc-rg/modules/svc/pages/integration-api.adoc
+++ b/core/_adoc-rg/modules/svc/pages/integration-api.adoc
@@ -7,7 +7,7 @@ The integration APIs provide functionality to the domain objects to integrate wi
The table below summarizes the integration APIs defined by Apache Isis.
-It also lists their corresponding implementation, either a default implementation provided by Apache Isis itself, or provided by one of the (non-ASF) link:http://platform.incode.org[Incode Platform^] modules.
+It also lists their corresponding implementation, either a default implementation provided by Apache Isis itself, or provided by one of the (non-ASF) link:https://platform.incode.org[Incode Platform^] modules.
.Integration API
diff --git a/core/_adoc-rg/modules/svc/pages/integration-api/BookmarkService.adoc b/core/_adoc-rg/modules/svc/pages/integration-api/BookmarkService.adoc
index 1fbade0..d8d553f 100644
--- a/core/_adoc-rg/modules/svc/pages/integration-api/BookmarkService.adoc
+++ b/core/_adoc-rg/modules/svc/pages/integration-api/BookmarkService.adoc
@@ -20,12 +20,12 @@ For example, a `Bookmark` could be converted into a barcode, and then this used
====
``Bookmark``s are used by several other domain services as a means of storing a reference to an arbitrary object
-(a polymorphic relationship). For example, the (non-ASF) link:http://platform.incode.org[Incode Platform^]'s auditing module's implementation of xref:rg:svc:persistence-layer-spi/AuditerService.adoc[`AuditerService`] uses bookmarks to capture the object that is being audited.
+(a polymorphic relationship). For example, the (non-ASF) link:https://platform.incode.org[Incode Platform^]'s auditing module's implementation of xref:rg:svc:persistence-layer-spi/AuditerService.adoc[`AuditerService`] uses bookmarks to capture the object that is being audited.
[TIP]
====
One downside of using ``Bookmark``s is that there is no way for the JDO/DataNucleus objectstore to enforce any kind of referental integrity.
-However, the (non-ASF) link:http://platform.incode.org[Incode Platform^]'s poly module describes and supports a design pattern to address this requirement.
+However, the (non-ASF) link:https://platform.incode.org[Incode Platform^]'s poly module describes and supports a design pattern to address this requirement.
====
@@ -102,9 +102,9 @@ A more sophisticated implementation could look inside the passed `ev` argument a
== Usage by other services
-Bookmarks are used by the (non-ASF) link:http://platform.incode.org[Incode Platform^]'s command module's implementation of xref:rg:svc:application-layer-spi/BackgroundCommandService.adoc[`BackgroundCommandService`], which uses a bookmark to capture the target object on which an action will be invoked subsequently.
+Bookmarks are used by the (non-ASF) link:https://platform.incode.org[Incode Platform^]'s command module's implementation of xref:rg:svc:application-layer-spi/BackgroundCommandService.adoc[`BackgroundCommandService`], which uses a bookmark to capture the target object on which an action will be invoked subsequently.
-Bookmarks are also used by the (non-ASF) link:http://platform.incode.org[Incode Platform^]'s auditing module's implementation of
+Bookmarks are also used by the (non-ASF) link:https://platform.incode.org[Incode Platform^]'s auditing module's implementation of
xref:rg:svc:persistence-layer-spi/AuditerService.adoc[`AuditerService`].
diff --git a/core/_adoc-rg/modules/svc/pages/intro.adoc b/core/_adoc-rg/modules/svc/pages/intro.adoc
index 4d4cae6..7c789b3 100644
--- a/core/_adoc-rg/modules/svc/pages/intro.adoc
+++ b/core/_adoc-rg/modules/svc/pages/intro.adoc
@@ -199,6 +199,6 @@ Likewise, the `PublishedObjects` class passed to the `PublisherService` at the e
This can be converted into XML using the `ChangesDtoUtils` utility class.
One final point: multiple xref:rg:svc:persistence-layer-spi/PublisherService.adoc[`PublisherService`] implementations are supported because different implementations may have different responsibilities.
-For example, the (non-ASF) link:http://platform.incode.org[Incode Platform^]'s publishmq module is responsible for publishing messages onto an ActiveMQ event bus, for inter-system communication.
+For example, the (non-ASF) link:https://platform.incode.org[Incode Platform^]'s publishmq module is responsible for publishing messages onto an ActiveMQ event bus, for inter-system communication.
However, the SPI can also be used for profiling; each execution within the call-graph contains metrics of the number of objects loaded or modified as a result of that execution, and thus could be used for application profiling.
The framework provides a default `PublisherServiceLogging` implementation that logs this using SLF4J.
\ No newline at end of file
diff --git a/core/_adoc-rg/modules/svc/pages/metadata-api.adoc b/core/_adoc-rg/modules/svc/pages/metadata-api.adoc
index 10af1a0..2bf74ce 100644
--- a/core/_adoc-rg/modules/svc/pages/metadata-api.adoc
+++ b/core/_adoc-rg/modules/svc/pages/metadata-api.adoc
@@ -6,7 +6,7 @@ include::_attributes.adoc[]
The metadata APIs provide access to the framework's internal metamodel. These are generally of use to support development-time activities, for example creating custom UIs through Swagger.
The table below summarizes the metadata APIs defined by Apache Isis.
-It also lists their corresponding implementation, either a default implementation provided by Apache Isis itself, or provided by one of the (non-ASF) link:http://platform.incode.org[Incode Platform^] modules.
+It also lists their corresponding implementation, either a default implementation provided by Apache Isis itself, or provided by one of the (non-ASF) link:https://platform.incode.org[Incode Platform^] modules.
.Metadata API
diff --git a/core/_adoc-rg/modules/svc/pages/metadata-api/ApplicationFeatureRepository.adoc b/core/_adoc-rg/modules/svc/pages/metadata-api/ApplicationFeatureRepository.adoc
index 9e6bde2..bb6c469 100644
--- a/core/_adoc-rg/modules/svc/pages/metadata-api/ApplicationFeatureRepository.adoc
+++ b/core/_adoc-rg/modules/svc/pages/metadata-api/ApplicationFeatureRepository.adoc
@@ -9,7 +9,7 @@ class members (collectively: "application features") of the domain classes withi
[TIP]
====
-This functionality was originally implemented as part of (non-ASF) link:http://platform.incode.org[Incode Platform^] security module, where the string representations of the various features are used to represent permissions.
+This functionality was originally implemented as part of (non-ASF) link:https://platform.incode.org[Incode Platform^] security module, where the string representations of the various features are used to represent permissions.
====
diff --git a/core/_adoc-rg/modules/svc/pages/persistence-layer-api.adoc b/core/_adoc-rg/modules/svc/pages/persistence-layer-api.adoc
index 44cd0ed..1f9a54e 100644
--- a/core/_adoc-rg/modules/svc/pages/persistence-layer-api.adoc
+++ b/core/_adoc-rg/modules/svc/pages/persistence-layer-api.adoc
@@ -8,7 +8,7 @@ The persistence layer APIs provide domain objects with tools to manage the inter
The table below summarizes the persistence layer APIs defined by Apache Isis.
-It also lists their corresponding implementation, either a default implementation provided by Apache Isis itself, or provided by one of the (non-ASF) link:http://platform.incode.org[Incode Platform^] modules.
+It also lists their corresponding implementation, either a default implementation provided by Apache Isis itself, or provided by one of the (non-ASF) link:https://platform.incode.org[Incode Platform^] modules.
.Persistence Layer API
diff --git a/core/_adoc-rg/modules/svc/pages/persistence-layer-spi.adoc b/core/_adoc-rg/modules/svc/pages/persistence-layer-spi.adoc
index 666c183..6318729 100644
--- a/core/_adoc-rg/modules/svc/pages/persistence-layer-spi.adoc
+++ b/core/_adoc-rg/modules/svc/pages/persistence-layer-spi.adoc
@@ -8,7 +8,7 @@ The persistence layer SPIs influence how the framework persists domain objects,
The table below summarizes the persistence layer SPIs defined by Apache Isis.
-It also lists their corresponding implementation, either a default implementation provided by Apache Isis itself, or provided by one of the (non-ASF) link:http://platform.incode.org[Incode Platform^] modules.
+It also lists their corresponding implementation, either a default implementation provided by Apache Isis itself, or provided by one of the (non-ASF) link:https://platform.incode.org[Incode Platform^] modules.
.Persistence Layer SPI
diff --git a/core/_adoc-rg/modules/svc/pages/persistence-layer-spi/AuditerService.adoc b/core/_adoc-rg/modules/svc/pages/persistence-layer-spi/AuditerService.adoc
index 84aeed3..7b593a0 100644
--- a/core/_adoc-rg/modules/svc/pages/persistence-layer-spi/AuditerService.adoc
+++ b/core/_adoc-rg/modules/svc/pages/persistence-layer-spi/AuditerService.adoc
@@ -74,9 +74,9 @@ The typical way to indicate that an object should be audited is to annotate it w
== Alternative Implementations
-The (non-ASF) link:http://platform.incode.org[Incode Platform^]'s audit module provides an implementation of this service (`AuditerService`), and also provides a number of related domain services (`AuditingServiceMenu`, `AuditingServiceRepository` and `AuditingServiceContributions`).
+The (non-ASF) link:https://platform.incode.org[Incode Platform^]'s audit module provides an implementation of this service (`AuditerService`), and also provides a number of related domain services (`AuditingServiceMenu`, `AuditingServiceRepository` and `AuditingServiceContributions`).
-The (non-ASF) link:http://platform.incode.org[Incode Platform^]'s audit module also provides an implementation, `org.isisaddons.module.audit.dom.AuditerServiceUsingJdo`.
+The (non-ASF) link:https://platform.incode.org[Incode Platform^]'s audit module also provides an implementation, `org.isisaddons.module.audit.dom.AuditerServiceUsingJdo`.
This creates an audit record for each changed property (ie every time that `AuditerService#audit(...)` is called.
The module also provides:
diff --git a/core/_adoc-rg/modules/svc/pages/persistence-layer-spi/PublisherService.adoc b/core/_adoc-rg/modules/svc/pages/persistence-layer-spi/PublisherService.adoc
index 0732efa..460070b 100644
--- a/core/_adoc-rg/modules/svc/pages/persistence-layer-spi/PublisherService.adoc
+++ b/core/_adoc-rg/modules/svc/pages/persistence-layer-spi/PublisherService.adoc
@@ -91,7 +91,7 @@ To indicate that:
== Alternative Implementations
-The (non-ASF) link:http://platform.incode.org[Incode Platform^]'s publishmq module also provides an implementation (`o.ia.m.publishmq.dom.servicespi.PublisherServiceUsingActiveMq`).
+The (non-ASF) link:https://platform.incode.org[Incode Platform^]'s publishmq module also provides an implementation (`o.ia.m.publishmq.dom.servicespi.PublisherServiceUsingActiveMq`).
This implementation:
* publishes each member execution as an event on an link:http://activemq.apache.org[ActiveMQ] message queue.
diff --git a/core/_adoc-rg/modules/svc/pages/presentation-layer-spi.adoc b/core/_adoc-rg/modules/svc/pages/presentation-layer-spi.adoc
index 151eb6d..773a1dd 100644
--- a/core/_adoc-rg/modules/svc/pages/presentation-layer-spi.adoc
+++ b/core/_adoc-rg/modules/svc/pages/presentation-layer-spi.adoc
@@ -7,7 +7,7 @@ include::_attributes.adoc[]
Domain service SPIs for the presentation layer influence how the Apache Isis viewers behave.
The table below summarizes the presentation layer SPIs defined by Apache Isis.
-It also lists their corresponding implementation, either a default implementation provided by Apache Isis itself, or provided by one of the (non-ASF) link:http://platform.incode.org[Incode Platform^] modules.
+It also lists their corresponding implementation, either a default implementation provided by Apache Isis itself, or provided by one of the (non-ASF) link:https://platform.incode.org[Incode Platform^] modules.
.Presentation Layer SPI
diff --git a/core/_adoc-rg/modules/svc/pages/presentation-layer-spi/ContentMappingService.adoc b/core/_adoc-rg/modules/svc/pages/presentation-layer-spi/ContentMappingService.adoc
index a45ce10..a426fd7 100644
--- a/core/_adoc-rg/modules/svc/pages/presentation-layer-spi/ContentMappingService.adoc
+++ b/core/_adoc-rg/modules/svc/pages/presentation-layer-spi/ContentMappingService.adoc
@@ -44,7 +44,7 @@ The framework provides two implementations of this service, both in support of t
By way of background: implementations of the SPI `CommandService` work with custom implementations of the `Command` interface, typically being persisted to a datastore.
The `CommandWithDto` interface is a subtype of `Command` for implementations that can be reified into xref:rg:cms:schema/cmd.adoc[`CommandDto`] XML instances.
-One implementation that does this is the (non-ASF) link:http://platform.incode.org[Incode Platform^]'s command module.
+One implementation that does this is the (non-ASF) link:https://platform.incode.org[Incode Platform^]'s command module.
For framework implementations of `ContentMappingService` allow domain service actions that return ``CommandDto``s (either singularly or in a list) to be converted into XML documents:
diff --git a/core/_adoc-rg/modules/svc/pages/presentation-layer-spi/SessionLoggingService.adoc b/core/_adoc-rg/modules/svc/pages/presentation-layer-spi/SessionLoggingService.adoc
index ed988c4..13abd13 100644
--- a/core/_adoc-rg/modules/svc/pages/presentation-layer-spi/SessionLoggingService.adoc
+++ b/core/_adoc-rg/modules/svc/pages/presentation-layer-spi/SessionLoggingService.adoc
@@ -35,5 +35,5 @@ public interface SessionLoggingService {
The framework provides an implementation, `SessionLoggingService.Stderr` that just prints out to standard error.
This is not registered by default, but can be easily registered manually using `AppManifestAbstract.Builder#withAdditionalServices(...)`.
-The (non-ASF) link:http://platform.incode.org[Incode Platform^]'s sessionlogger module provides an implementation that logs each session as a JDO entity.
+The (non-ASF) link:https://platform.incode.org[Incode Platform^]'s sessionlogger module provides an implementation that logs each session as a JDO entity.
diff --git a/core/_adoc-rg/modules/svc/pages/testing.adoc b/core/_adoc-rg/modules/svc/pages/testing.adoc
index 93c9bcf..87a8427 100644
--- a/core/_adoc-rg/modules/svc/pages/testing.adoc
+++ b/core/_adoc-rg/modules/svc/pages/testing.adoc
@@ -10,7 +10,7 @@ The testing SPIs allow the framework to provide supporting functionality for use
The table below summarizes the testing APIs defined by Apache Isis.
-It also lists their corresponding implementation, either a default implementation provided by Apache Isis itself, or provided by one of the (non-ASF) link:http://platform.incode.org[Incode Platform^] modules.
+It also lists their corresponding implementation, either a default implementation provided by Apache Isis itself, or provided by one of the (non-ASF) link:https://platform.incode.org[Incode Platform^] modules.
.Testing API
@@ -83,7 +83,7 @@ SpecificationProvider`].
The table below summarizes the testing SPIs defined by Apache Isis.
-It also lists their corresponding implementation, either a default implementation provided by Apache Isis itself, or provided by one of the (non-ASF) link:http://platform.incode.org[Incode Platform^] modules.
+It also lists their corresponding implementation, either a default implementation provided by Apache Isis itself, or provided by one of the (non-ASF) link:https://platform.incode.org[Incode Platform^] modules.
.Testing SPI
diff --git a/core/_adoc-ug/modules/btb/pages/deployment/externalized-configuration.adoc b/core/_adoc-ug/modules/btb/pages/deployment/externalized-configuration.adoc
index 515755e..1f44e9c 100644
--- a/core/_adoc-ug/modules/btb/pages/deployment/externalized-configuration.adoc
+++ b/core/_adoc-ug/modules/btb/pages/deployment/externalized-configuration.adoc
@@ -123,7 +123,7 @@ Further details an be found in the link:https://logging.apache.org/log4j/1.2/man
== Spring Config
Although Apache Isis does not use Spring, it's possible that your app may use other components that do use Spring.
-For example, the (non-ASF) link:http://platform.incode.org[Incode Platform^]'s publishmq module uses ActiveMQ and Camel to support publishing; both of these leverage Spring.
+For example, the (non-ASF) link:https://platform.incode.org[Incode Platform^]'s publishmq module uses ActiveMQ and Camel to support publishing; both of these leverage Spring.
There are several ways to externalized Spring config, but the mechanism described here is similar in nature to those that we use for externalizing Apache Isis' and Shiro's configuration.
In your `web.xml`, you will probably load the Spring application context using code such as:
diff --git a/core/_adoc-ug/modules/btb/pages/headless-access/BackgroundCommandExecution.adoc b/core/_adoc-ug/modules/btb/pages/headless-access/BackgroundCommandExecution.adoc
index 8755b5e..6dcf3c3 100644
--- a/core/_adoc-ug/modules/btb/pages/headless-access/BackgroundCommandExecution.adoc
+++ b/core/_adoc-ug/modules/btb/pages/headless-access/BackgroundCommandExecution.adoc
@@ -34,7 +34,7 @@ image::headless-access/BackgroundCommandExecution.png[width="400px",link="{image
The `BackgroundCommandExecutionFromBackgroundCommandServiceJdo` is a concrete subclass of `BackgroundCommandExecution` (see the xref:rg:svc:application-layer-api/BackgroundService.adoc[`BackgroundCommandService`]), the intended use being for the class to be instantiated regularly (eg every 10 seconds) by a scheduler such as http://quartz-scheduler.org[Quartz]) to poll for ``Command``s to be executed, and then execute them.
-This implementation queries for ``Command``s persisted by the (non-ASF) link:http://platform.incode.org[Incode Platform^]'s command module's implementations of xref:rg:svc:application-layer-spi/CommandService.adoc[`CommandService`] and xref:rg:svc:application-layer-spi/BackgroundCommandService.adoc[`BackgroundCommandService`] using the `BackgroundCommandServiceJdoRepository`.
+This implementation queries for ``Command``s persisted by the (non-ASF) link:https://platform.incode.org[Incode Platform^]'s command module's implementations of xref:rg:svc:application-layer-spi/CommandService.adoc[`CommandService`] and xref:rg:svc:application-layer-spi/BackgroundCommandService.adoc[`BackgroundCommandService`] using the `BackgroundCommandServiceJdoRepository`.
The diagram below (link:http://yuml.me/edit/25343da1[yuml.me/25343da1]) shows the inheritance hierarchy for this class:
diff --git a/core/_adoc-ug/modules/btb/pages/hints-and-tips/multi-tenancy.adoc b/core/_adoc-ug/modules/btb/pages/hints-and-tips/multi-tenancy.adoc
index b803723..f0b153e 100644
--- a/core/_adoc-ug/modules/btb/pages/hints-and-tips/multi-tenancy.adoc
+++ b/core/_adoc-ug/modules/btb/pages/hints-and-tips/multi-tenancy.adoc
@@ -3,10 +3,10 @@ include::_attributes.adoc[]
: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 ag [...]
-Of the various modules provided by the (non-ASF) link:http://platform.incode.org[Incode Platform^], the security module has the most features.
+Of the various modules provided by the (non-ASF) link:https://platform.incode.org[Incode Platform^], the security module has the most features.
One significant feature is the ability to associate users and objects with a "tenancy".
-For more details, see the link:http://platform.incode.org[Incode Platform^]'s security module README.
+For more details, see the link:https://platform.incode.org[Incode Platform^]'s security module README.
diff --git a/core/_adoc-ug/modules/fun/pages/building-blocks/modules.adoc b/core/_adoc-ug/modules/fun/pages/building-blocks/modules.adoc
index 7b61f2c..dc54319 100644
--- a/core/_adoc-ug/modules/fun/pages/building-blocks/modules.adoc
+++ b/core/_adoc-ug/modules/fun/pages/building-blocks/modules.adoc
@@ -7,7 +7,7 @@ include::_attributes.adoc[]
We tend to use Maven modules as a way to group related domain objects together; we can then reason about all the classes in that module as a single unit.
By convention there will be a single top-level package corresponding to the module.
-For example, the (non-ASF) link:http://platform.incode.org[Incode Platform^]'s http://platform.incode.org/modules/lib/excel/lib-excel.html[Excel] module has a top-level package of `org.incode.module.excel`.
+For example, the (non-ASF) link:https://platform.incode.org[Incode Platform^]'s http://platform.incode.org/modules/lib/excel/lib-excel.html[Excel] module has a top-level package of `org.incode.module.excel`.
Within the module there may be various subpackages, but it's the module that defines the namespace.
[NOTE]
diff --git a/core/plugins/jdo/_adoc/modules/ROOT/pages/db-schemas.adoc b/core/plugins/jdo/_adoc/modules/ROOT/pages/db-schemas.adoc
index a08c724..4f47f6d 100644
--- a/core/plugins/jdo/_adoc/modules/ROOT/pages/db-schemas.adoc
+++ b/core/plugins/jdo/_adoc/modules/ROOT/pages/db-schemas.adoc
@@ -5,7 +5,7 @@ include::_attributes.adoc[]
In the same way that Java packages act as a namespace for domain objects, it's good practice to map domain entities to their own (database) schemas.
-All the (non-ASF) link:http://platform.incode.org[Incode Platform^] modules do this.
+All the (non-ASF) link:https://platform.incode.org[Incode Platform^] modules do this.
For example:
diff --git a/core/plugins/jdo/_adoc/modules/ROOT/pages/hints-and-tips/jdoql-and-timestamps.adoc b/core/plugins/jdo/_adoc/modules/ROOT/pages/hints-and-tips/jdoql-and-timestamps.adoc
index 1e6f5b6..af55fb5 100644
--- a/core/plugins/jdo/_adoc/modules/ROOT/pages/hints-and-tips/jdoql-and-timestamps.adoc
+++ b/core/plugins/jdo/_adoc/modules/ROOT/pages/hints-and-tips/jdoql-and-timestamps.adoc
@@ -5,7 +5,7 @@ include::_attributes.adoc[]
Beware of entities with a property called "timestamp": you run the risk of "timestamp" being treated as a keyword in certain contexts, probably not as you intended.
-By way of example, the (non-ASF) link:http://platform.incode.org[Incode Platform]'s command module has an entity called `CommandJdo`.
+By way of example, the (non-ASF) link:https://platform.incode.org[Incode Platform]'s command module has an entity called `CommandJdo`.
This has a property called "timestamp", of type `java.sql.Timestamp`.
This defines a query using JDOQL:
diff --git a/core/plugins/jdo/_adoc/modules/ROOT/pages/hints-and-tips/overriding-jdo-annotations.adoc b/core/plugins/jdo/_adoc/modules/ROOT/pages/hints-and-tips/overriding-jdo-annotations.adoc
index 1e698fc..a7bb2ac 100644
--- a/core/plugins/jdo/_adoc/modules/ROOT/pages/hints-and-tips/overriding-jdo-annotations.adoc
+++ b/core/plugins/jdo/_adoc/modules/ROOT/pages/hints-and-tips/overriding-jdo-annotations.adoc
@@ -26,7 +26,7 @@ However, using this first approach does create a maintenance effort; if the doma
The second approach (using an `.orm` file) is therefore often more useful than the first, because the metadata provided overrides rather than replaces the annotations (and annotations not overridden continue to be honoured).
A typical use case is to change the database schema for an entity.
-For example, the various (non-ASF) link:http://platform.incode.org[Incode Platform^] modules use schemas for each entity. For example, the `AuditEntry` entity in the (non-ASF) link:http://platform.incode.org[Incode Platform^]'s audit module is annotated as:
+For example, the various (non-ASF) link:https://platform.incode.org[Incode Platform^] modules use schemas for each entity. For example, the `AuditEntry` entity in the (non-ASF) link:https://platform.incode.org[Incode Platform^]'s audit module is annotated as:
[source,java]
----
diff --git a/core/security/_adoc/modules/ROOT/pages/about.adoc b/core/security/_adoc/modules/ROOT/pages/about.adoc
index 61099bd..26a2e2c 100644
--- a/core/security/_adoc/modules/ROOT/pages/about.adoc
+++ b/core/security/_adoc/modules/ROOT/pages/about.adoc
@@ -30,7 +30,7 @@ The xref:helloworld:ROOT:about.adoc[HelloWorld] and xref:simpleapp:ROOT:about.ad
Shiro also ships with an implementation of an LDAP-based realm; LDAP is often used to manage user/passwords and corresponding user groups.
Apache Isis in turn extends this with its `IsisLdapRealm`, which provides more flexibility for both group/role and role/permissions management.
-In addition, the (non-ASF) link:http://platform.incode.org[Incode Platform^] modules provides the security module, which also provides an implementation of the Shiro `Realm` API.
+In addition, the (non-ASF) link:https://platform.incode.org[Incode Platform^] modules provides the security module, which also provides an implementation of the Shiro `Realm` API.
However, the security module also represents users, roles and permissions as domain objects, allowing them to be administered through Apache Isis itself.
Moreover, the security module can optionally delegate password management to a subsidiary (delegate) realm (usually LDAP as discussed above).
@@ -44,9 +44,9 @@ A further aspect of security is auditing: recording what data was modified by wh
Apache Isis provides the xref:rg:svc:application-layer-api/InteractionContext.adoc[`InteractionContext`]
can be used to track the actions being invoked, and the xref:rg:svc:persistence-layer-spi/AuditerService.adoc[`AuditerService`]
captures what data was modified as a result (auditing).
-When ``Interaction``s are persisted (eg by way of (non-ASF) link:http://platform.incode.org[Incode Platform^]'s publishmq module) this provides excellent
+When ``Interaction``s are persisted (eg by way of (non-ASF) link:https://platform.incode.org[Incode Platform^]'s publishmq module) this provides excellent
traceability.
-The (non-ASF) link:http://platform.incode.org[Incode Platform^]'s audit module provides an implementation of the `AuditerService`.
+The (non-ASF) link:https://platform.incode.org[Incode Platform^]'s audit module provides an implementation of the `AuditerService`.
For xref:rg:svc:application-layer-spi/CommandService.adoc[`CommandService`] can be also be used to capture actions.
====
diff --git a/core/security/_adoc/modules/ROOT/pages/api-for-applications.adoc b/core/security/_adoc/modules/ROOT/pages/api-for-applications.adoc
index 5510eea..d57d6ca 100644
--- a/core/security/_adoc/modules/ROOT/pages/api-for-applications.adoc
+++ b/core/security/_adoc/modules/ROOT/pages/api-for-applications.adoc
@@ -43,11 +43,11 @@ If using the Wicket viewer, then note there will also be another role which is u
== Servlet API
On occasion you may find it necessary to reach below Apache Isis and to the underlying servlet API.
-For example, the (non-ASF) link:http://platform.incode.org[Incode Platform^]'s togglz module (non-ASF) has a requirement to do this in order to expose its embedded togglz web console. (
+For example, the (non-ASF) link:https://platform.incode.org[Incode Platform^]'s togglz module (non-ASF) has a requirement to do this in order to expose its embedded togglz web console. (
[TIP]
====
-If you do need to access the servlet API and are running within the context of Wicket viewer, the (non-ASF) link:http://platform.incode.org[Incode Platform^]'s servletapi module can provide access to the `HttpServletRequest`, `HttpServletResponse` and `ServletContext`.
+If you do need to access the servlet API and are running within the context of Wicket viewer, the (non-ASF) link:https://platform.incode.org[Incode Platform^]'s servletapi module can provide access to the `HttpServletRequest`, `HttpServletResponse` and `ServletContext`.
====
In this situation, you can still obtain some information about the user and its roles:
diff --git a/core/security/_adoc/modules/ROOT/pages/shiro-realm-implementations/isisaddons-security-module-realm.adoc b/core/security/_adoc/modules/ROOT/pages/shiro-realm-implementations/isisaddons-security-module-realm.adoc
index facc6b8..49618e5 100644
--- a/core/security/_adoc/modules/ROOT/pages/shiro-realm-implementations/isisaddons-security-module-realm.adoc
+++ b/core/security/_adoc/modules/ROOT/pages/shiro-realm-implementations/isisaddons-security-module-realm.adoc
@@ -4,7 +4,7 @@ include::_attributes.adoc[]
-The (non-ASF) link:http://platform.incode.org[Incode Platform^]'s security module provides a complete security subdomain for users, roles, permissions; all are persisted as domain entities.
+The (non-ASF) link:https://platform.incode.org[Incode Platform^]'s security module provides a complete security subdomain for users, roles, permissions; all are persisted as domain entities.
What that means, of course, that they can also be administered through your Apache Isis application.
Moreover, the set of permissions (to features) is derived completely from your application's metamodel; in essence the permissions are "type-safe".
diff --git a/core/security/_adoc/modules/ROOT/pages/shiro-realm-implementations/jdbc-realm.adoc b/core/security/_adoc/modules/ROOT/pages/shiro-realm-implementations/jdbc-realm.adoc
index 7e86d62..e180f34 100644
--- a/core/security/_adoc/modules/ROOT/pages/shiro-realm-implementations/jdbc-realm.adoc
+++ b/core/security/_adoc/modules/ROOT/pages/shiro-realm-implementations/jdbc-realm.adoc
@@ -8,7 +8,7 @@ There is nothing to stop you from using some other `Realm` implementation (or in
[WARNING]
====
-If you are happy to use a database then we strongly recommend you use the (non-ASF) link:http://platform.incode.org[Incode Platform^]'s security module instead of a vanilla JDBC; it is far more sophisticated and moreover gives you the ability to administer the system from within your Apache Isis application.
+If you are happy to use a database then we strongly recommend you use the (non-ASF) link:https://platform.incode.org[Incode Platform^]'s security module instead of a vanilla JDBC; it is far more sophisticated and moreover gives you the ability to administer the system from within your Apache Isis application.
====
If you go down this route, then the architecture is as follows:
diff --git a/core/security/_adoc/modules/ROOT/pages/usage-by-isis-viewers.adoc b/core/security/_adoc/modules/ROOT/pages/usage-by-isis-viewers.adoc
index 1053cf4..bf5c8f3 100644
--- a/core/security/_adoc/modules/ROOT/pages/usage-by-isis-viewers.adoc
+++ b/core/security/_adoc/modules/ROOT/pages/usage-by-isis-viewers.adoc
@@ -57,7 +57,7 @@ The sign-in verification page to render is pluggable; see xref:vw:ROOT:extending
User registration is only available if the xref:rg:svc:persistence-layer-spi/UserRegistrationService.adoc[`UserRegistrationService`] is configured; this is used by the framework to actually create new instances of the user as accessed by the corresponding (Shiro) realm.
-Because Shiro realms are pluggable, the Apache Isis framework does not provide default implementations of this service. However, if you are using the (non-ASF) link:http://platform.incode.org[Incode Platform^]'s security module, then this module _does_ provide an implementation (that, as you might expect, creates new "user" domain entities).
+Because Shiro realms are pluggable, the Apache Isis framework does not provide default implementations of this service. However, if you are using the (non-ASF) link:https://platform.incode.org[Incode Platform^]'s security module, then this module _does_ provide an implementation (that, as you might expect, creates new "user" domain entities).
If you are using an LDAP realm and want to enable user-self registration then you'll need to write your own implementation of this service.
diff --git a/core/testsupport/_adoc/modules/ROOT/pages/fixture-scripts/api-and-usage.adoc b/core/testsupport/_adoc/modules/ROOT/pages/fixture-scripts/api-and-usage.adoc
index c994cd6..b93809e 100644
--- a/core/testsupport/_adoc/modules/ROOT/pages/fixture-scripts/api-and-usage.adoc
+++ b/core/testsupport/_adoc/modules/ROOT/pages/fixture-scripts/api-and-usage.adoc
@@ -141,7 +141,7 @@ public class RecreateSimpleObjects extends FixtureScript { //
----
<1> inherit from `org.apache.isis.applib.fixturescripts.FixtureScript`
<2> a hard-coded list of values for the names.
-Note that the (non-ASF) link:http://platform.incode.org[Incode Platform^]'s fakedata module could also have been used
+Note that the (non-ASF) link:https://platform.incode.org[Incode Platform^]'s fakedata module could also have been used
<3> whether the script is "discoverable"; in other words whether it should be rendered in the drop-down by the `FixtureScripts` service
<4> input property: the number of objects to create, up to 10; for the calling test to specify, but note this is optional and has a default (see below).
It's important that a wrapper class is used (ie `java.lang.Integer`, not `int`)
@@ -347,7 +347,7 @@ And for more complex entity -where there might be many potential values that nee
- the builder script can automatically default some or even all of these values.
For example, for a customer's date of birth, the buider could default to a date making the customer an adult, aged between 18 and 65, say.
-For an email address or postal address, or an image, or some "lorem ipsum" text, the (non-ASF) link:http://platform.incode.org[Incode Platform^]'s fakedata module could provide randomised values.
+For an email address or postal address, or an image, or some "lorem ipsum" text, the (non-ASF) link:https://platform.incode.org[Incode Platform^]'s fakedata module could provide randomised values.
The benefit of an intelligent builder is that it further simplifies the test.
The developer reading the test then knows that everything that has been specified exactly is of significance.
diff --git a/core/testsupport/_adoc/modules/ROOT/pages/overview.adoc b/core/testsupport/_adoc/modules/ROOT/pages/overview.adoc
index 5c22c00..da90a6b 100644
--- a/core/testsupport/_adoc/modules/ROOT/pages/overview.adoc
+++ b/core/testsupport/_adoc/modules/ROOT/pages/overview.adoc
@@ -137,7 +137,7 @@ We want our tests to be easily understood, and we want the reader's eye to be dr
One way to do this is to use random (or fake) values for any insignificant data. This in effect tells the reader that "any value will do". Moreover, if it turns out that any data won't do, and that there's some behaviour that is sensitive to the value, then the test will start to flicker, passing and then failing depending on inputs. This is A Good Thing™.
-Apache Isis does not, itself, ship with a fake data library. However, the (non-ASF) link:http://platform.incode.org[Incode Platform^]'s fakedata module (non-ASF) does provide exactly this capability.
+Apache Isis does not, itself, ship with a fake data library. However, the (non-ASF) link:https://platform.incode.org[Incode Platform^]'s fakedata module (non-ASF) does provide exactly this capability.
[TIP]
====
@@ -153,7 +153,7 @@ Writing automated tests is just good development practice. Also good practice i
Sometimes, though, a feature will take longer to implement than your iteration cycle. In such a case, how do you use continuous integration to keep everyone working on the mainline without revealing a half-implemented feature on your releases? One option is to use link:http://martinfowler.com/bliki/FeatureToggle.html[feature toggle]s.
-Apache Isis does not, itself, ship with a feature toggle library. However, the (non-ASF) link:http://platform.incode.org[Incode Platform^]'s togglz module does provide exactly this capability.
+Apache Isis does not, itself, ship with a feature toggle library. However, the (non-ASF) link:https://platform.incode.org[Incode Platform^]'s togglz module does provide exactly this capability.
diff --git a/core/testsupport/_adoc/modules/ROOT/pages/unit-test-support/soap-fake-server-junit-rule.adoc b/core/testsupport/_adoc/modules/ROOT/pages/unit-test-support/soap-fake-server-junit-rule.adoc
index a7369f6..791f088 100644
--- a/core/testsupport/_adoc/modules/ROOT/pages/unit-test-support/soap-fake-server-junit-rule.adoc
+++ b/core/testsupport/_adoc/modules/ROOT/pages/unit-test-support/soap-fake-server-junit-rule.adoc
@@ -12,7 +12,7 @@ The `SoapEndpointPublishingRule` is a simple JUnit rule that allows you to run a
[TIP]
====
-The (non-ASF) link:http://platform.incode.org[Incode Platform^]'s publishmq module provides a full example of how to integrate and test an Apache Isis application with a (faked out) external system.
+The (non-ASF) link:https://platform.incode.org[Incode Platform^]'s publishmq module provides a full example of how to integrate and test an Apache Isis application with a (faked out) external system.
====
diff --git a/core/viewer-wicket/_adoc/modules/ROOT/pages/about.adoc b/core/viewer-wicket/_adoc/modules/ROOT/pages/about.adoc
index 59e79eb..6d085cd 100644
--- a/core/viewer-wicket/_adoc/modules/ROOT/pages/about.adoc
+++ b/core/viewer-wicket/_adoc/modules/ROOT/pages/about.adoc
@@ -6,6 +6,6 @@ implemented using link:http://wicket.apache.org[Apache Wicket].
This user guide discuss end-user features, configuration and customization of the Wicket viewer.
-It also discusses how to extend the viewer, and the (non-ASF) link:http://platform.incode.org[Incode Platform^] wicket components.
+It also discusses how to extend the viewer, and the (non-ASF) link:https://platform.incode.org[Incode Platform^] wicket components.
diff --git a/core/viewer-wicket/_adoc/modules/ROOT/pages/extending/login-via-query-args-prototyping.adoc b/core/viewer-wicket/_adoc/modules/ROOT/pages/extending/login-via-query-args-prototyping.adoc
index 6a13cb5..441aff3 100644
--- a/core/viewer-wicket/_adoc/modules/ROOT/pages/extending/login-via-query-args-prototyping.adoc
+++ b/core/viewer-wicket/_adoc/modules/ROOT/pages/extending/login-via-query-args-prototyping.adoc
@@ -44,4 +44,4 @@ public WebRequest newWebRequest(HttpServletRequest servletRequest, String filter
}
----
-Rather than using the static `DEMO_MODE_USING_CREDENTIALS_AS_QUERYARGS`, you might also explore using the feature toggle library provided by the (non-ASF) link:http://platform.incode.org[Incode Platform^]'s togglz module.
\ No newline at end of file
+Rather than using the static `DEMO_MODE_USING_CREDENTIALS_AS_QUERYARGS`, you might also explore using the feature toggle library provided by the (non-ASF) link:https://platform.incode.org[Incode Platform^]'s togglz module.
\ No newline at end of file
diff --git a/core/viewer-wicket/_adoc/modules/ROOT/pages/extending/replacing-page-elements.adoc b/core/viewer-wicket/_adoc/modules/ROOT/pages/extending/replacing-page-elements.adoc
index 4c68ac0..4489541 100644
--- a/core/viewer-wicket/_adoc/modules/ROOT/pages/extending/replacing-page-elements.adoc
+++ b/core/viewer-wicket/_adoc/modules/ROOT/pages/extending/replacing-page-elements.adoc
@@ -5,7 +5,7 @@ include::_attributes.adoc[]
Replacing elements of the page is the most powerful general-purpose way to customize the look-n-feel of the viewer.
-Examples in the (non-ASF) link:http://platform.incode.org[Incode Platform^] include the gmap3, fullcalendar2, excel, pdfjs and wickedcharts components.
+Examples in the (non-ASF) link:https://platform.incode.org[Incode Platform^] include the gmap3, fullcalendar2, excel, pdfjs and wickedcharts components.
The pages generated by Apache Isis' Wicket viewer are built up of numerous elements, from fine-grained widgets for property/parameter fields, to much larger components that take responsibility for rendering an entire entity, or a collection of entities.
Under the covers these are all implementations of the the Apache Wicket `Component` API.
@@ -136,7 +136,7 @@ For example, out-of-the-box Apache Isis provides a table view, a summary view (t
These are selected by clicking on the toolbar by each collection.
Additional views though could render the objects in the collection as a variety of ways.
-Indeed, some third-party implementations in the (non-ASF) link:http://platform.incode.org[Incode Platform^] already exist, including:
+Indeed, some third-party implementations in the (non-ASF) link:https://platform.incode.org[Incode Platform^] already exist, including:
* excel component - collection as a downloadable excel spreadsheet
* gmap3 component - render any objects with a location on a map
diff --git a/core/viewer-wicket/_adoc/modules/ROOT/pages/features/user-registration.adoc b/core/viewer-wicket/_adoc/modules/ROOT/pages/features/user-registration.adoc
index 70ac9f6..5ed31f0 100644
--- a/core/viewer-wicket/_adoc/modules/ROOT/pages/features/user-registration.adoc
+++ b/core/viewer-wicket/_adoc/modules/ROOT/pages/features/user-registration.adoc
@@ -66,7 +66,7 @@ image::user-registration/sign-up-after-registration.png[width="800px",link="{ima
There are two prerequisites:
-* register an implementation of the xref:rg:svc:persistence-layer-spi/UserRegistrationService.adoc[user registration service] (eg by using the (non-ASF) link:http://platform.incode.org[Incode Platform^]'s security module)
+* register an implementation of the xref:rg:svc:persistence-layer-spi/UserRegistrationService.adoc[user registration service] (eg by using the (non-ASF) link:https://platform.incode.org[Incode Platform^]'s security module)
* configure the xref:rg:svc:integration-api/EmailService.adoc[email service]
diff --git a/core/viewer-wicket/_adoc/modules/ROOT/pages/incode-platform.adoc b/core/viewer-wicket/_adoc/modules/ROOT/pages/incode-platform.adoc
index 2481b6e..5bf4e69 100644
--- a/core/viewer-wicket/_adoc/modules/ROOT/pages/incode-platform.adoc
+++ b/core/viewer-wicket/_adoc/modules/ROOT/pages/incode-platform.adoc
@@ -3,7 +3,7 @@
include::_attributes.adoc[]
-The (non-ASF) link:http://platform.incode.org[Incode Platform^] provides a number of extensions to the Wicket viewer (leveraging the APIs described in xref:vw:ROOT:extending.adoc[Extending the Wicket viewer] section, later.
+The (non-ASF) link:https://platform.incode.org[Incode Platform^] provides a number of extensions to the Wicket viewer (leveraging the APIs described in xref:vw:ROOT:extending.adoc[Extending the Wicket viewer] section, later.
While you are free to fork and adapt any of them to your needs, they are also intended for use "out-of-the-box".
At the time of writing the addons available are:
@@ -25,7 +25,7 @@ At the time of writing the addons available are:
* Wickedcharts Wicket component - low-level integration with Highcharts charting library
-Check the link:http://platform.incode.org[website^] for the most up-to-date list.
+Check the link:https://platform.incode.org[website^] for the most up-to-date list.
NOTE: The Incode Platform, although maintained by Apache Isis committers, is not part of the ASF.
diff --git a/core/viewer-wicket/_adoc/modules/ROOT/pages/layout/file-based.adoc b/core/viewer-wicket/_adoc/modules/ROOT/pages/layout/file-based.adoc
index ca27960..71720b4 100644
--- a/core/viewer-wicket/_adoc/modules/ROOT/pages/layout/file-based.adoc
+++ b/core/viewer-wicket/_adoc/modules/ROOT/pages/layout/file-based.adoc
@@ -48,7 +48,7 @@ If no layout has been specified (or if the specified layout cannot be found), th
Finally, if this can't be found, then the framework will search for a file named `Xxx.layout.fallback.xml`.
If present, this will be used instead.
-The "fallback" layout this therefore allows libraries that provide a domain entities/view models (for example, the (non-ASF) link:http://platform.incode.org[Incode Platform] modules) to define the UI of these objects using a layout file, while still allowing the consuming application to override that layout if it so requires.
+The "fallback" layout this therefore allows libraries that provide a domain entities/view models (for example, the (non-ASF) link:https://platform.incode.org[Incode Platform] modules) to define the UI of these objects using a layout file, while still allowing the consuming application to override that layout if it so requires.
diff --git a/core/viewer-wicket/_adoc/modules/ROOT/pages/menubars-layout.adoc b/core/viewer-wicket/_adoc/modules/ROOT/pages/menubars-layout.adoc
index 9658ae2..f65692c 100644
--- a/core/viewer-wicket/_adoc/modules/ROOT/pages/menubars-layout.adoc
+++ b/core/viewer-wicket/_adoc/modules/ROOT/pages/menubars-layout.adoc
@@ -8,7 +8,7 @@ The actions of domain services are made available as menu items on menus.
By default each domain service corresponds to a single menu on this menu bar, with its actions as the drop-down menu items.
This is rarely exactly what is required, however; it often makes sense to group menu items for similar domain services together.
-For example, the (non-ASF) link:http://platform.incode.org[Incode Platform^] modules provides services whose actions appear into two top-level menus:
+For example, the (non-ASF) link:https://platform.incode.org[Incode Platform^] modules provides services whose actions appear into two top-level menus:
* its `ApplicationUsers`, `ApplicationRoles`, `ApplicationPermission`, `ApplicationFeatureViewModels` and `ApplicationTenancies` domain services are all grouped together in a single "Security" top-level menu, on the SECONDARY menu bar
diff --git a/examples/apps/simpleapp/_adoc/modules/ROOT/pages/about.adoc b/examples/apps/simpleapp/_adoc/modules/ROOT/pages/about.adoc
index 1a14e77..a3fd0c1 100644
--- a/examples/apps/simpleapp/_adoc/modules/ROOT/pages/about.adoc
+++ b/examples/apps/simpleapp/_adoc/modules/ROOT/pages/about.adoc
@@ -12,7 +12,7 @@ We'll talk more about the structure of the generated app xref:about.adoc#structu
[TIP]
====
-The (non-ASF) Incode Platform's link:http://platform.incode.org/quickstart/quickstart.html[quickstart archetype] builds upon the simpleapp archetype, but also adds in support for various Incode Platform modules such as security, auditing, commands and publishing.
+The (non-ASF) Incode Platform's link:https://platform.incode.org/quickstart/quickstart.html[quickstart archetype] builds upon the simpleapp archetype, but also adds in support for various Incode Platform modules such as security, auditing, commands and publishing.
====