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 2022/10/23 14:01:11 UTC
[isis] 03/18: ISIS-3260: renames 'Isis' -> 'Causeway' in all .adoc files (except mignotes and relnotes)
This is an automated email from the ASF dual-hosted git repository.
danhaywood pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/isis.git
commit 80899546522ebe74b8f61eb3f8da987ae9d12bad
Author: Dan Haywood <da...@haywood-associates.co.uk>
AuthorDate: Sun Oct 23 12:37:18 2022 +0100
ISIS-3260: renames 'Isis' -> 'Causeway' in all .adoc files (except mignotes and relnotes)
---
CONTRIBUTING.adoc | 2 +-
README.adoc | 42 +++++++++++-----------
.../comguide/modules/ROOT/pages/about.adoc | 2 +-
.../ROOT/pages/antora-publish-procedure.adoc | 4 +--
.../modules/ROOT/pages/cutting-a-release.adoc | 14 ++++----
.../modules/ROOT/pages/key-generation.adoc | 2 +-
.../comguide/modules/ROOT/pages/pmc-notes.adoc | 20 +++++------
.../comguide/modules/ROOT/pages/policies.adoc | 2 +-
.../modules/ROOT/pages/policies/git-policy.adoc | 2 +-
.../ROOT/pages/policies/versioning-policy.adoc | 4 +--
.../ROOT/pages/post-release-successful.adoc | 20 +++++------
.../ROOT/pages/post-release-unsuccessful.adoc | 6 ++--
.../modules/ROOT/pages/verifying-releases.adoc | 8 ++---
antora/components/conguide/modules/ROOT/nav.adoc | 2 +-
.../conguide/modules/ROOT/pages/about.adoc | 2 +-
.../modules/ROOT/pages/building-apache-isis.adoc | 26 +++++++-------
.../conguide/modules/ROOT/pages/contributing.adoc | 16 ++++-----
.../conguide/modules/agilej/pages/about.adoc | 2 +-
.../modules/documentation/pages/about.adoc | 2 +-
.../pages/building-docs-and-website.adoc | 2 +-
.../conguide/modules/eclipse/pages/about.adoc | 4 +--
.../conguide/modules/git/pages/about.adoc | 6 ++--
.../conguide/modules/intellij/pages/about.adoc | 2 +-
.../components/docs/modules/ROOT/pages/about.adoc | 6 ++--
.../docs/modules/ROOT/pages/downloads/how-to.adoc | 10 +++---
.../going-deeper/articles-and-presentations.adoc | 20 +++++------
.../modules/ROOT/pages/going-deeper/books.adoc | 4 +--
.../ROOT/pages/landing-page/components.adoc | 2 +-
.../modules/ROOT/pages/landing-page/guides.adoc | 2 +-
.../ROOT/pages/more-thanks/more-thanks.adoc | 4 +--
.../what-is-apache-isis/isis-in-pictures.adoc | 34 +++++++++---------
.../what-is-apache-isis/screencasts-older.adoc | 16 ++++-----
.../pages/what-is-apache-isis/screencasts.adoc | 20 +++++------
.../partials/module-nav/what-is-apache-isis.adoc | 4 +--
.../docs/modules/resources/pages/about.adoc | 2 +-
.../docs/modules/resources/pages/cheatsheet.adoc | 2 +-
.../docs/modules/resources/pages/icons.adoc | 2 +-
.../docs/modules/support/pages/mailing-list.adoc | 2 +-
.../hooks/Action_025-execution-publishing.adoc | 2 +-
.../hooks/DomainObjectLayout_024-named.adoc | 2 +-
.../annotation/hooks/DomainObject_022-nature.adoc | 4 +--
.../hooks/Facets_010-examples-and-usage.adoc | 2 +-
.../hooks/Programmatic_010-examples-and-usage.adoc | 2 +-
.../annotation/hooks/Property_021-optionality.adoc | 16 ++++-----
.../annotation/hooks/Property_023-maxLength.adoc | 2 +-
.../hooks/Property_027-execution-publishing.adoc | 2 +-
.../pages/index/mixins/dto/hooks/Dto_see-also.adoc | 2 +-
.../hooks/ClockService_020-examples-and-usage.adoc | 2 +-
...gurationViewService_020-examples-and-usage.adoc | 2 +-
.../EventBusService_020-examples-and-usage.adoc | 6 ++--
.../hooks/GridService_020-examples-and-usage.adoc | 4 +--
.../TranslationService_010-implementation.adoc | 2 +-
...ranslationsResolver_020-examples-and-usage.adoc | 2 +-
.../jaxb/hooks/JaxbService_010-implementation.adoc | 2 +-
...ExecutionSubscriber_020-examples-and-usage.adoc | 2 +-
.../SwaggerService_020-examples-and-usage.adoc | 2 +-
...NotificationService_020-examples-and-usage.adoc | 6 ++--
.../hooks/WrapperFactory_010-implementation.adoc | 2 +-
.../JdoSupportService_010-examples-and-usage.adoc | 4 +--
...onServiceForRestfulObjectsV1_0_usage-notes.adoc | 2 +-
.../refguide/modules/applib-ant/pages/Column.adoc | 26 +++++++-------
.../refguide/modules/applib-ant/pages/Digits.adoc | 2 +-
.../modules/applib-ant/pages/Discriminator.adoc | 6 ++--
.../modules/applib-ant/pages/NotPersistent.adoc | 4 +--
.../modules/applib-ant/pages/Nullable.adoc | 8 ++---
.../refguide/modules/applib-ant/pages/Pattern.adoc | 2 +-
.../applib-ant/pages/PersistenceCapable.adoc | 8 ++---
.../modules/applib-ant/pages/PrimaryKey.adoc | 6 ++--
.../modules/applib-ant/pages/XmlRootElement.adoc | 4 +--
.../refguide/modules/applib-ant/pages/about.adoc | 6 ++--
.../modules/applib-ant/pages/about/jdo.adoc | 12 +++----
.../modules/applib-ant/pages/about/jee.adoc | 4 +--
.../modules/applib-ant/pages/about/jpa.adoc | 2 +-
.../modules/applib-ant/pages/about/main.adoc | 4 +--
.../modules/applib-ant/pages/about/other.adoc | 8 ++---
.../modules/applib-ant/pages/about/partial.adoc | 2 +-
.../applib-classes/pages/layout/object-layout.adoc | 4 +--
.../modules/applib-classes/pages/spec.adoc | 2 +-
.../modules/applib-classes/pages/value-types.adoc | 2 +-
.../modules/applib-methods/pages/about.adoc | 2 +-
.../modules/applib-methods/pages/lifecycle.adoc | 2 +-
.../modules/applib-methods/pages/prefixes.adoc | 4 +--
.../applib-methods/pages/prefixes/disable.adoc | 2 +-
.../modules/applib-methods/pages/prefixes/get.adoc | 6 ++--
.../applib-methods/pages/ui-hints/title.adoc | 4 +--
.../refguide/modules/applib-svc/pages/about.adoc | 8 ++---
.../partials/_application-layer-spi.adoc | 2 +-
.../applib-svc/partials/_core-domain-api.adoc | 2 +-
.../modules/applib-svc/partials/_metadata-api.adoc | 2 +-
.../relnotes/modules/ROOT/pages/about.adoc | 22 ++++++------
.../setupguide/modules/ROOT/pages/about.adoc | 4 +--
.../setupguide/modules/eclipse/pages/about.adoc | 6 ++--
.../intellij/partials/UNUSED/coding-standards.adoc | 2 +-
.../partials/UNUSED/faster-turnaround-times.adoc | 6 ++--
.../intellij/partials/UNUSED/live-templates.adoc | 2 +-
.../tutorials/modules/ROOT/pages/about.adoc | 2 +-
.../petclinic/pages/010-getting-started.adoc | 16 ++++-----
.../petclinic/pages/020-the-petclinic-domain.adoc | 2 +-
.../userguide/modules/ROOT/pages/about.adoc | 4 +--
.../userguide/modules/btb/pages/about.adoc | 2 +-
.../modules/btb/pages/headless-access.adoc | 12 +++----
.../modules/btb/pages/hints-and-tips.adoc | 2 +-
.../how-to-handle-void-and-null-results.adoc | 6 ++--
.../how-to-implement-a-spellchecker.adoc | 2 +-
.../replacing-default-service-implementations.adoc | 2 +-
.../simulating-collections-of-values.adoc | 4 +--
.../hints-and-tips/transactions-and-errors.adoc | 6 ++--
.../userguide/modules/btb/pages/i18n.adoc | 10 +++---
.../modules/btb/pages/other-techniques.adoc | 2 +-
.../modules/btb/pages/programming-model.adoc | 2 +-
.../pages/programming-model/custom-validator.adoc | 4 +--
.../btb/pages/programming-model/finetuning.adoc | 6 ++--
.../modules/fun/pages/concepts-patterns.adoc | 2 +-
.../apache-isis-vs-cqrs-and-event-sourcing.adoc | 36 +++++++++----------
.../fun/pages/concepts-patterns/architecture.adoc | 32 ++++++++---------
.../fun/pages/concepts-patterns/core-values.adoc | 28 +++++++--------
.../concepts-patterns/deployment-options.adoc | 4 +--
.../fun/pages/concepts-patterns/metamodel.adoc | 8 ++---
.../concepts-patterns/naked-objects-pattern.adoc | 4 +--
.../pages/domain-entities-and-services/crud.adoc | 2 +-
.../domain-entities.adoc | 4 +--
.../domain-services.adoc | 10 +++---
.../inject-services.adoc | 6 ++--
.../modules/fun/pages/meta-annotations.adoc | 4 +--
.../userguide/modules/fun/pages/modules.adoc | 4 +--
.../modules/fun/pages/object-members/actions.adoc | 2 +-
.../fun/pages/object-members/collections.adoc | 18 +++++-----
.../fun/pages/object-members/properties.adoc | 32 ++++++++---------
.../userguide/modules/fun/pages/overview.adoc | 2 +-
.../modules/fun/pages/overview/events.adoc | 2 +-
.../modules/fun/pages/overview/identifiers.adoc | 6 ++--
.../modules/fun/pages/overview/modules.adoc | 8 ++---
.../modules/fun/pages/overview/object-members.adoc | 6 ++--
.../fun/pages/overview/programming-model.adoc | 8 ++---
.../pages/overview/types-of-domain-objects.adoc | 26 +++++++-------
.../components/userguide/modules/fun/pages/ui.adoc | 4 +--
.../modules/fun/pages/ui/action-icons-and-css.adoc | 2 +-
.../modules/fun/pages/ui/menubars-layout.adoc | 2 +-
.../modules/fun/pages/ui/object-layout.adoc | 2 +-
.../fun/pages/ui/object-titles-and-icons.adoc | 2 +-
.../userguide/modules/fun/pages/view-models.adoc | 10 +++---
.../modules/fun/partials/_deployment-options.adoc | 26 +++++++-------
.../src/main/adoc/modules/schema/pages/about.adoc | 2 +-
.../src/main/adoc/modules/schema/pages/common.adoc | 2 +-
.../src/main/adoc/modules/commons/pages/about.adoc | 2 +-
.../commons/pages/concurrent-task-list-UNUSED.adoc | 4 +--
.../src/main/adoc/modules/config/pages/about.adoc | 16 ++++-----
.../pages/section-hooks/datanucleus~pre.adoc | 2 +-
.../pages/section-hooks/eclipselink~pre.adoc | 2 +-
.../pages/section-hooks/isis.core.config~pre.adoc | 2 +-
.../pages/sections/isis.security.keycloak.adoc | 2 +-
.../main/adoc/modules/metamodel/pages/about.adoc | 6 ++--
.../modules/metamodel/pages/class-diagram.adoc | 2 +-
.../flyway/adoc/modules/flyway/pages/about.adoc | 2 +-
.../secman/adoc/modules/secman/pages/about.adoc | 8 ++---
.../secman/pages/setting-up-with-shiro.adoc | 4 +--
.../adoc/modules/secman/pages/setting-up.adoc | 2 +-
.../adoc/modules/shiro-realm-ldap/pages/about.adoc | 2 +-
.../modules/shiro-realm-ldap/pages/ldap-realm.adoc | 6 ++--
.../modules/kroviz/pages/DevelopmentGuide.adoc | 8 ++---
.../kroviz/adoc/modules/kroviz/pages/about.adoc | 2 +-
.../kroviz/adoc/modules/kroviz/pages/credits.adoc | 2 +-
.../adoc/modules/kroviz/pages/regression-test.adoc | 2 +-
mavendeps/adoc/modules/mavendeps/pages/about.adoc | 4 +--
.../setup-and-configure-dependencyManagement.adoc | 2 +-
.../disabling-persistence-by-reachability.adoc | 4 +--
.../modules/ROOT/pages/dependency-injection.adoc | 2 +-
.../adoc/modules/ROOT/pages/hints-and-tips.adoc | 2 +-
.../subtype-entity-not-fully-populated.adoc | 4 +--
.../mandatory-properties-in-subtypes.adoc | 2 +-
.../ROOT/pages/setup-and-configuration.adoc | 2 +-
.../modules/ROOT/pages/dependency-injection.adoc | 2 +-
.../adoc/modules/ROOT/pages/hints-and-tips.adoc | 2 +-
.../jpa/adoc/modules/ROOT/pages/mapping-guide.adoc | 4 +--
.../ROOT/pages/setup-and-configuration.adoc | 2 +-
.../jpa/adoc/modules/ROOT/pages/weaving.adoc | 2 +-
security/adoc/modules/ROOT/pages/about.adoc | 10 +++---
.../modules/ROOT/pages/usage-by-isis-viewers.adoc | 4 +--
.../adoc/modules/ROOT/partials/module-nav-end.adoc | 2 +-
.../main/adoc/modules/keycloak/pages/about.adoc | 6 ++--
.../src/main/adoc/modules/shiro/pages/about.adoc | 14 ++++----
.../src/main/adoc/modules/spring/pages/about.adoc | 6 ++--
starters/adoc/modules/parent-pom/pages/about.adoc | 6 ++--
.../adoc/modules/starters/pages/helloworld.adoc | 26 +++++++-------
.../adoc/modules/starters/pages/simpleapp.adoc | 30 ++++++++--------
testing/adoc/modules/ROOT/pages/about.adoc | 22 ++++++------
.../adoc/modules/archtestsupport/pages/about.adoc | 4 +--
.../adoc/modules/fixtures/pages/about.adoc | 4 +--
.../adoc/modules/integtestsupport/pages/about.adoc | 12 +++----
.../adoc/modules/specsupport/pages/about.adoc | 2 +-
.../adoc/modules/unittestsupport/pages/about.adoc | 6 ++--
.../cli/adoc/modules/tooling-cli/pages/about.adoc | 4 +--
.../adoc/modules/ROOT/pages/about.adoc | 4 +--
.../adoc/modules/ROOT/pages/client.adoc | 2 +-
.../modules/ROOT/pages/content-negotiation.adoc | 6 ++--
.../apache-isis-v2-profile.adoc | 4 +--
.../content-negotiation/other-representations.adoc | 4 +--
.../simplified-representations/accept-header.adoc | 2 +-
.../configuration-properties.adoc | 4 +--
.../simplified-representations/domain-object.adoc | 2 +-
.../adoc/modules/ROOT/pages/hints-and-tips.adoc | 2 +-
.../hints-and-tips/restful-image-property.adoc | 4 +--
.../adoc/modules/ROOT/pages/layout-resources.adoc | 2 +-
.../adoc/modules/ROOT/pages/ro-spec.adoc | 16 ++++-----
.../ROOT/pages/setup-and-configuration.adoc | 4 +--
.../adoc/modules/ROOT/partials/module-nav.adoc | 2 +-
viewers/wicket/adoc/modules/ROOT/pages/about.adoc | 2 +-
.../ROOT/pages/customisation/about-page.adoc | 2 +-
.../pages/customisation/custom-javascript.adoc | 2 +-
.../ROOT/pages/customisation/embedded-view.adoc | 2 +-
.../pages/extending/custom-bootstrap-theme.adoc | 2 +-
.../modules/ROOT/pages/extending/custom-pages.adoc | 2 +-
.../pages/extending/replacing-page-elements.adoc | 14 ++++----
.../wicket/adoc/modules/ROOT/pages/features.adoc | 2 +-
.../ROOT/pages/features/titles-in-tables.adoc | 2 +-
.../ROOT/pages/features/user-registration.adoc | 2 +-
.../i18n-label-in-wicket-viewer.adoc | 2 +-
.../ROOT/pages/hints-and-tips/per-user-themes.adoc | 4 +--
.../ROOT/pages/setup-and-configuration.adoc | 2 +-
.../adoc/modules/ROOT/partials/security/pages.adoc | 2 +-
.../ROOT/partials/security/user-registration.adoc | 6 ++--
221 files changed, 673 insertions(+), 673 deletions(-)
diff --git a/CONTRIBUTING.adoc b/CONTRIBUTING.adoc
index d7c88743f4..15cbaaac8f 100644
--- a/CONTRIBUTING.adoc
+++ b/CONTRIBUTING.adoc
@@ -1,3 +1,3 @@
= Contributing
-You can find full details of how to contribute back to Isis at our https://causeway.apache.org/conguide/2.0.0-M8/contributing.html[main website].
+You can find full details of how to contribute back to Causeway at our https://causeway.apache.org/conguide/2.0.0-M8/contributing.html[main website].
diff --git a/README.adoc b/README.adoc
index e0b7e493a0..999085d159 100644
--- a/README.adoc
+++ b/README.adoc
@@ -1,4 +1,4 @@
-= Apache Isis
+= Apache Causeway
:toc:
:toc-title: pass:[<h3>Contents</h3>]
:toc-placement!:
@@ -8,9 +8,9 @@ image:https://github.com/apache/causeway/workflows/Build%20and%20Test%20(w/%20Ma
image:https://sonarcloud.io/api/project_badges/measure?project=apache_isis&metric=alert_status[link="https://sonarcloud.io/dashboard?id=apache_isis"]
image:https://github.com/apache-causeway-committers/causeway-nightly/workflows/Nightly/badge.svg[link="https://github.com/apache-causeway-committers/causeway-nightly/actions?query=workflow%3A%22Nightly%22"]
-_http://causeway.apache.org[Apache Isis] software is a framework for rapidly developing domain-driven apps in Java. Write your business logic in entities, domain services and repositories, and the framework dynamically generates a representation of that domain model as a webapp or a RESTful API._
+_http://causeway.apache.org[Apache Causeway] software is a framework for rapidly developing domain-driven apps in Java. Write your business logic in entities, domain services and repositories, and the framework dynamically generates a representation of that domain model as a webapp or a RESTful API._
-Start learning about Apache Isis using the https://github.com/apache/causeway-app-helloworld["Hello World"] starter app.
+Start learning about Apache Causeway using the https://github.com/apache/causeway-app-helloworld["Hello World"] starter app.
Explore features with our daily built demo docker image https://github.com/apache/causeway/blob/master/examples/demo/domain/src/main/adoc/modules/demo/pages/about.adoc["DemoApp"].
Build your own apps using our https://github.com/apache/causeway-app-simpleapp["SimpleApp"] starter app.
@@ -67,19 +67,19 @@ You can find the latest version by browsing the link:https://github.com/apache/c
== Core Features
-Apache Isis automatically generates the UI from the domain classes.
+Apache Causeway automatically generates the UI from the domain classes.
=== Sign-in
-Apache Isis integrates with http://shiro.apache.org[Apache Shiro] as well as link:https://spring.io/projects/spring-security[Spring Security] and link:https://www.keycloak.org/[Keycloak].
-When using Shiro, the core framework supports file-based realms, while the __SecMan__ extension provides a well-featured subdomain of users, roles and permissions against features derived from the Apache Isis metamodel.
+Apache Causeway integrates with http://shiro.apache.org[Apache Shiro] as well as link:https://spring.io/projects/spring-security[Spring Security] and link:https://www.keycloak.org/[Keycloak].
+When using Shiro, the core framework supports file-based realms, while the __SecMan__ extension provides a well-featured subdomain of users, roles and permissions against features derived from the Apache Causeway metamodel.
image::https://raw.githubusercontent.com/apache/causeway/master/antora/components/docs/modules/ROOT/images/what-is-apache-causeway/causeway-in-pictures/010-login.png[link="https://raw.githubusercontent.com/apache/causeway/master/antora/components/docs/modules/ROOT/images/what-is-apache-causeway/causeway-in-pictures/010-login.png"]
=== Install Fixtures
-Apache Isis has lots of features to help you prototype and then fully test your application.
+Apache Causeway has lots of features to help you prototype and then fully test your application.
One such are fixture scripts, which allow pre-canned data to be installed in the running application.
This is great to act as the starting point for identifying new stories; later on when the feature is being implemented, the same fixture script can be re-used within that feature's integration tests.
(More on tests later).
@@ -88,7 +88,7 @@ image::https://raw.githubusercontent.com/apache/causeway/master/antora/component
=== Dashboard and View Models
-Most of the time the end-user interacts with representations of persistent domain entities, but Isis also supports view models which can aggregate data from multiple sources.
+Most of the time the end-user interacts with representations of persistent domain entities, but Causeway also supports view models which can aggregate data from multiple sources.
The todoapp example uses a "dashboard" view model to list todo items not yet done vs those completed.
image::https://raw.githubusercontent.com/apache/causeway/master/antora/components/docs/modules/ROOT/images/what-is-apache-causeway/causeway-in-pictures/030-dashboard-view-model.png[link="https://raw.githubusercontent.com/apache/causeway/master/antora/components/docs/modules/ROOT/images/what-is-apache-causeway/causeway-in-pictures/030-dashboard-view-model.png"]
@@ -104,7 +104,7 @@ There are no controllers or HTML to write.
image::https://raw.githubusercontent.com/apache/causeway/master/antora/components/docs/modules/ROOT/images/what-is-apache-causeway/causeway-in-pictures/040-domain-entity.png[link="https://raw.githubusercontent.com/apache/causeway/master/antora/components/docs/modules/ROOT/images/what-is-apache-causeway/causeway-in-pictures/"]
-In addition to the domain entity, Apache Isis allows layout metadata hints to be provided, for example to specify the grouping of properties, the positioning of those groups into columns, the association of actions (the buttons) with properties or collections, the icons on the buttons, and so on.
+In addition to the domain entity, Apache Causeway allows layout metadata hints to be provided, for example to specify the grouping of properties, the positioning of those groups into columns, the association of actions (the buttons) with properties or collections, the icons on the buttons, and so on.
This metadata can be specified either as annotations or in JSON form; the benefit of the latter is that it can be updated (and the UI redrawn) without restarting the app.
Any production-ready app will require this metadata but (like the view models discussed above) this metadata can be added gradually on top of the core domain model.
@@ -135,7 +135,7 @@ We sometimes use the term "behaviourally complete" for such domain objects.
=== Mixins
As an alternative to placing actions (business logic) on a domain object, it can instead be placed inside a mixin object.
-When an object is rendered by Apache Isis, the mixin "contributes" its behaviour to the domain object (similar to aspect-oriented traits).
+When an object is rendered by Apache Causeway, the mixin "contributes" its behaviour to the domain object (similar to aspect-oriented traits).
In the screenshot below the highlighted "export as xml" action, the "relative priority" property (and "previous" and "next" actions) the "similar to" collection and the two "as DTO" actions are all contributed by mixins:
@@ -150,7 +150,7 @@ image::https://raw.githubusercontent.com/apache/causeway/master/antora/component
== Extensible Views
-The Apache Isis viewer is implemented using http://wicket.apache.org[Apache Wicket], and has been architected to be extensible.
+The Apache Causeway viewer is implemented using http://wicket.apache.org[Apache Wicket], and has been architected to be extensible.
For example, when a collection of objects is rendered, this is just one several views, as shown in the selector drop-down:
image::https://raw.githubusercontent.com/apache/causeway/master/antora/components/docs/modules/ROOT/images/what-is-apache-causeway/causeway-in-pictures/070-pluggable-views.png[link="https://raw.githubusercontent.com/apache/causeway/master/antora/components/docs/modules/ROOT/images/what-is-apache-causeway/causeway-in-pictures/070-pluggable-views.png"]
@@ -190,7 +190,7 @@ In the security menu is access to the rich set of functionality provided by the
image::https://raw.githubusercontent.com/apache/causeway/master/antora/components/docs/modules/ROOT/images/what-is-apache-causeway/causeway-in-pictures/130-security.png[link="https://raw.githubusercontent.com/apache/causeway/master/antora/components/docs/modules/ROOT/images/what-is-apache-causeway/causeway-in-pictures/130-security.png"]
In the prototyping menu is the ability to download a GNU gettext `.po` file for translation.
-This file can then be translated into multiple languages so that your app can support different locales. Note that this feature is part of Apache Isis core:
+This file can then be translated into multiple languages so that your app can support different locales. Note that this feature is part of Apache Causeway core:
image::https://raw.githubusercontent.com/apache/causeway/master/antora/components/docs/modules/ROOT/images/what-is-apache-causeway/causeway-in-pictures/140-i18n.png[link="https://raw.githubusercontent.com/apache/causeway/master/antora/components/docs/modules/ROOT/images/what-is-apache-causeway/causeway-in-pictures/140-i18n.png"]
@@ -221,12 +221,12 @@ Assuming they have been granted permissions, this allows a user to access an ent
image::https://raw.githubusercontent.com/apache/causeway/master/antora/components/docs/modules/ROOT/images/what-is-apache-causeway/causeway-in-pictures/180-app-user-entity.png[link="https://raw.githubusercontent.com/apache/causeway/master/antora/components/docs/modules/ROOT/images/what-is-apache-causeway/causeway-in-pictures/180-app-user-entity.png"]
-If not all of these properties are required, then they can be hidden either using security or though Isis' internal event bus (described below).
+If not all of these properties are required, then they can be hidden either using security or though Causeway' internal event bus (described below).
Conversely, additional properties can be "grafted onto" the user using the contributed properties/collections discussed previously.
=== Themes
-Apache Isis' Wicket viewer uses link:http://getbootstrap.com[Twitter Bootstrap], which means that it can be themed.
+Apache Causeway' Wicket viewer uses link:http://getbootstrap.com[Twitter Bootstrap], which means that it can be themed.
If more than one theme has been configured for the app, then the viewer allows the end-user to switch their theme:
image::https://raw.githubusercontent.com/apache/causeway/master/antora/components/docs/modules/ROOT/images/what-is-apache-causeway/causeway-in-pictures/190-switch-theme.png[link="https://raw.githubusercontent.com/apache/causeway/master/antora/components/docs/modules/ROOT/images/what-is-apache-causeway/causeway-in-pictures/190-switch-theme.png"]
@@ -235,7 +235,7 @@ image::https://raw.githubusercontent.com/apache/causeway/master/antora/component
== REST API
-In addition to Isis' Wicket viewer, it also provides a fully fledged REST API, as an implementation of the http://restfulobjects.org[Restful Objects] specification.
+In addition to Causeway' Wicket viewer, it also provides a fully fledged REST API, as an implementation of the http://restfulobjects.org[Restful Objects] specification.
The screenshot below shows accessing this REST API using a Chrome plugin:
image::https://raw.githubusercontent.com/apache/causeway/master/antora/components/docs/modules/ROOT/images/what-is-apache-causeway/causeway-in-pictures/200-rest-api.png[link="https://raw.githubusercontent.com/apache/causeway/master/antora/components/docs/modules/ROOT/images/what-is-apache-causeway/causeway-in-pictures/200-rest-api.png"]
@@ -246,7 +246,7 @@ Like the Wicket viewer, the REST API is generated automatically from the domain
== Integration Testing Support
-Earlier on we noted that Apache Isis allows fixtures to be installed through the UI.
+Earlier on we noted that Apache Causeway allows fixtures to be installed through the UI.
These same fixture scripts can be reused within integration tests.
For example, the code snippet below shows how the `FixtureScripts` service injected into an integration test can then be used to set up data:
@@ -258,8 +258,8 @@ While these are integration tests (so talking to a real database), they are no m
image::https://raw.githubusercontent.com/apache/causeway/master/antora/components/docs/modules/ROOT/images/what-is-apache-causeway/causeway-in-pictures/220-testing-happy-case.png[link="https://raw.githubusercontent.com/apache/causeway/master/antora/components/docs/modules/ROOT/images/what-is-apache-causeway/causeway-in-pictures/220-testing-happy-case.png"]
-To simulate the business rules enforced by Apache Isis, the domain object can be "wrapped" in a proxy.
-For example, if using the Wicket viewer then Apache Isis will enforce the rule (implemented in the `ToDoItem` class itself) that a completed item cannot have the "completed" action invoked upon it.
+To simulate the business rules enforced by Apache Causeway, the domain object can be "wrapped" in a proxy.
+For example, if using the Wicket viewer then Apache Causeway will enforce the rule (implemented in the `ToDoItem` class itself) that a completed item cannot have the "completed" action invoked upon it.
The wrapper simulates this by throwing an appropriate exception:
image::https://raw.githubusercontent.com/apache/causeway/master/antora/components/docs/modules/ROOT/images/what-is-apache-causeway/causeway-in-pictures/230-testing-wrapper-factory.png[link="https://raw.githubusercontent.com/apache/causeway/master/antora/components/docs/modules/ROOT/images/what-is-apache-causeway/causeway-in-pictures/230-testing-wrapper-factory.png"]
@@ -269,9 +269,9 @@ image::https://raw.githubusercontent.com/apache/causeway/master/antora/component
== Internal Event Bus
-Contributions, discussed earlier, are an important tool in ensuring that the packages within your Apache Isis application are decoupled; by extracting out actions the order of dependency between packages can effectively be reversed.
+Contributions, discussed earlier, are an important tool in ensuring that the packages within your Apache Causeway application are decoupled; by extracting out actions the order of dependency between packages can effectively be reversed.
-Another important tool to ensure your codebase remains maintainable is Isis' internal event bus.
+Another important tool to ensure your codebase remains maintainable is Causeway' internal event bus.
It is probably best explained by example; the code below says that the "complete" action should emit a `ToDoItem.Completed` event:
image::https://raw.githubusercontent.com/apache/causeway/master/antora/components/docs/modules/ROOT/images/what-is-apache-causeway/causeway-in-pictures/240-domain-events.png[link="https://raw.githubusercontent.com/apache/causeway/master/antora/components/docs/modules/ROOT/images/what-is-apache-causeway/causeway-in-pictures/240-domain-events.png"]
@@ -298,7 +298,7 @@ Indeed, the example todoapp demonstrates this.
== Learning More
-The Apache Isis http://causeway.apache.org[website] has lots of useful information and is being continually updated.
+The Apache Causeway http://causeway.apache.org[website] has lots of useful information and is being continually updated.
Or, you can just start coding using the https://github.com/apache/causeway-app-simpleapp[SimpleApp] starter app.
diff --git a/antora/components/comguide/modules/ROOT/pages/about.adoc b/antora/components/comguide/modules/ROOT/pages/about.adoc
index 0cd55b99ac..fa1a80e0b5 100644
--- a/antora/components/comguide/modules/ROOT/pages/about.adoc
+++ b/antora/components/comguide/modules/ROOT/pages/about.adoc
@@ -3,7 +3,7 @@
: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 [...]
-This committers' guide is for committers of Apache Isis itself who want guidance on release process, publishing documents and other related procedures.
+This committers' guide is for committers of Apache Causeway itself who want guidance on release process, publishing documents and other related procedures.
//include::applying-patches.adoc[leveloffset=+1]
diff --git a/antora/components/comguide/modules/ROOT/pages/antora-publish-procedure.adoc b/antora/components/comguide/modules/ROOT/pages/antora-publish-procedure.adoc
index 3c5cff8006..5d2e601f32 100644
--- a/antora/components/comguide/modules/ROOT/pages/antora-publish-procedure.adoc
+++ b/antora/components/comguide/modules/ROOT/pages/antora-publish-procedure.adoc
@@ -12,7 +12,7 @@ There is relevant material in xref:post-release-successful.adoc[Post Release (Su
-Apache Isis' documentation (meaning the website and the users' guide, the reference guide and this contributors' guide) is written using link:https://asciidoctor.org/[Asciidoctor] syntax, and organized to be published as an link:https://antora.org[Antora] website.
+Apache Causeway' documentation (meaning the website and the users' guide, the reference guide and this contributors' guide) is written using link:https://asciidoctor.org/[Asciidoctor] syntax, and organized to be published as an link:https://antora.org[Antora] website.
The website and guides are created by running build tools (documented below) which create the HTML version of the site and guides.
You can therefore easily check the documentation before raising a pull request (as a contributor) or publishing the site (if a committer).
@@ -21,7 +21,7 @@ For details of authoring/updating the documents and website, see the xref:congui
Publishing is performed by copying the generated HTML to a different git repository (link:https://github.com/apache/causeway-site.git[causeway-site]).
This is synced by ASF infrastructure over to link:http://causeway.apache.org[causeway.apache.org].
-This can only be done by Apache Isis committers, and is discussed below.
+This can only be done by Apache Causeway committers, and is discussed below.
== One-time setup
diff --git a/antora/components/comguide/modules/ROOT/pages/cutting-a-release.adoc b/antora/components/comguide/modules/ROOT/pages/cutting-a-release.adoc
index dd19f5cbde..0ee050a800 100644
--- a/antora/components/comguide/modules/ROOT/pages/cutting-a-release.adoc
+++ b/antora/components/comguide/modules/ROOT/pages/cutting-a-release.adoc
@@ -7,10 +7,10 @@
The release process consists of:
* the release manager cutting the release (documented below)
-* Members of the Apache Isis PMC xref:comguide:ROOT:verifying-releases.adoc[verifying] and voting on the release
+* Members of the Apache Causeway PMC xref:comguide:ROOT:verifying-releases.adoc[verifying] and voting on the release
* the release manager performing post-release tasks, for either a xref:comguide:ROOT:post-release-successful.adoc[successful] or an xref:comguide:ROOT:post-release-unsuccessful.adoc[unsuccessful] vote.
-Apache Isis itself is released in one go, everything is ultimately a child of `bom/pom.xml` (relative to the link:https://github.com/apache/causeway[source code root]).
+Apache Causeway itself is released in one go, everything is ultimately a child of `bom/pom.xml` (relative to the link:https://github.com/apache/causeway[source code root]).
This section details the process for formally releasing this module.
The subsequent sections describe how other committers can xref:comguide:ROOT:verifying-releases.adoc[verify a release] and how the release manager can then perform xref:comguide:ROOT:post-release-successful.adoc[post-release] activities and set up for the next development iteration.
@@ -97,7 +97,7 @@ Once you've fixed all issues, run the script again to confirm that all license v
=== Missing License Check
-Although Apache Isis has no dependencies on artifacts with incompatible licenses, the POMs for some of these dependencies (in the Maven central repo) do not necessarily contain the required license information.
+Although Apache Causeway has no dependencies on artifacts with incompatible licenses, the POMs for some of these dependencies (in the Maven central repo) do not necessarily contain the required license information.
Without appropriate additional configuration, this would result in the generated `DEPENDENCIES` file and generated Maven site indicating dependencies as having "unknown" licenses.
Fortunately, Maven allows the missing information to be provided by configuring the `maven-remote-resources-plugin`.
@@ -315,7 +315,7 @@ git commit -m "$ISISJIRA: bumps version to $ISISREL"
=== Sanity check
Perform one last sanity check on the codebase.
-Delete all Isis artifacts from your local Maven repo, then build using the `-o` offline flag.
+Delete all Causeway artifacts from your local Maven repo, then build using the `-o` offline flag.
Still in the `bom` directory:
@@ -856,21 +856,21 @@ In all cases, votes last for 72 hours and require a +3 (binding) vote from membe
That is, link:mailto:dev@apache.causeway.org[]
-The following boilerplate is for a release of the Apache Isis Core.
+The following boilerplate is for a release of the Apache Causeway Core.
Adapt as required:
Use the following subject, eg:
[source,subs="attributes+"]
----
-[VOTE] Apache Isis Core release {page-isisrel} RC1
+[VOTE] Apache Causeway Core release {page-isisrel} RC1
----
And use the following body:
[source,subs="attributes+"]
----
-I've just cut a new release of the Apache Isis Framework.
+I've just cut a new release of the Apache Causeway Framework.
The source code zip artifact has been uploaded to a staging repository on
https://repository.apache.org, along with its corresponding .asc signature.
diff --git a/antora/components/comguide/modules/ROOT/pages/key-generation.adoc b/antora/components/comguide/modules/ROOT/pages/key-generation.adoc
index 45064c7c79..861c095361 100644
--- a/antora/components/comguide/modules/ROOT/pages/key-generation.adoc
+++ b/antora/components/comguide/modules/ROOT/pages/key-generation.adoc
@@ -513,7 +513,7 @@ Finally, commit your changes.
=== Save to `KEYS`
-The armored representation of the public key should be saved to Apache Isis' `KEYS` file, http://www.apache.org/dist/causeway/KEYS[http://www.apache.org/dist/causeway/KEYS] (that is, in the ASF distribution directory for Apache Isis).
+The armored representation of the public key should be saved to Apache Causeway' `KEYS` file, http://www.apache.org/dist/causeway/KEYS[http://www.apache.org/dist/causeway/KEYS] (that is, in the ASF distribution directory for Apache Causeway).
First, in a new directory, checkout this file:
diff --git a/antora/components/comguide/modules/ROOT/pages/pmc-notes.adoc b/antora/components/comguide/modules/ROOT/pages/pmc-notes.adoc
index 3f8ca625d9..5fafb25916 100644
--- a/antora/components/comguide/modules/ROOT/pages/pmc-notes.adoc
+++ b/antora/components/comguide/modules/ROOT/pages/pmc-notes.adoc
@@ -11,7 +11,7 @@ Every ASF project has a Project Management Committee, or PMC.
This committee is ultimately responsible for the long-term management of the framework.
More information about PMCs can be found link:http://www.apache.org/dev/pmc.html[here]
-In Apache Isis, every committer is a member of the PMC.
+In Apache Causeway, every committer is a member of the PMC.
This page contains some general notes on maintenance activities required by PMC members.
@@ -54,13 +54,13 @@ with body:
[source]
----
-I'd like to nominate Joe Bloggs as a committer and also a PMC member for Apache Isis. <1>
+I'd like to nominate Joe Bloggs as a committer and also a PMC member for Apache Causeway. <1>
Joe this ... <1>
Joe that ... <1>
-Overall, I think Joe would be a great addition to Isis' committers and PMC; ...
+Overall, I think Joe would be a great addition to Causeway' committers and PMC; ...
Voting ends in one week's time, i.e. midnight UTC on YYYY-MM-DD <1>
http://www.timeanddate.com/countdown/to?year=YYYY&month=MM&day=DD
@@ -118,7 +118,7 @@ More info can be found in the https://www.apache.org/dev/new-committers-guide.ht
=== Update the `causeway` unix group
All committers must be added to the `causeway` UNIX group.
-This will give them commit access to the Apache Isis git repo.
+This will give them commit access to the Apache Causeway git repo.
To do this, log onto `minotaur.apache.org`, then eg:
@@ -169,7 +169,7 @@ For example:
[source]
----
-[NOTICE] Joe Bloggs to join Apache Isis as committer and member of the PMC <1>
+[NOTICE] Joe Bloggs to join Apache Causeway as committer and member of the PMC <1>
----
<1> update as required
@@ -177,7 +177,7 @@ with body:
[source]
----
-The Apache Isis PMC has voted Joe Bloggs as a committer and also member of the PMC. <1>
+The Apache Causeway PMC has voted Joe Bloggs as a committer and also member of the PMC. <1>
Voting thread:
https://mail-search.apache.org/members/private-arch/causeway-private/xxx <1>
@@ -196,7 +196,7 @@ update the private threads above
=== Update project metadata
-Update the `STATUS` file (in the root directory of the Apache Isis git repo) with the new committer details.
+Update the `STATUS` file (in the root directory of the Apache Causeway git repo) with the new committer details.
=== Announce to the world
@@ -214,16 +214,16 @@ with body:
[source]
----
-I'm delighted to announce that Joe Bloggs has been voted in as a committer on Isis, and also as a member of the Isis PMC. The first gives Joe the right to commit changes directly to Isis' codebase, the second gives him the right to be involved in future votes.
+I'm delighted to announce that Joe Bloggs has been voted in as a committer on Causeway, and also as a member of the Causeway PMC. The first gives Joe the right to commit changes directly to Causeway' codebase, the second gives him the right to be involved in future votes.
Joe this ... <1>
Joe that ...
-I'm looking forward to working with Joe in the future; another great addition to Isis' committers. So please join me in welcoming him to our happy band!
+I'm looking forward to working with Joe in the future; another great addition to Causeway' committers. So please join me in welcoming him to our happy band!
Dan Haywood
-Apache Isis PMC Chair
+Apache Causeway PMC Chair
----
<1> update as required
diff --git a/antora/components/comguide/modules/ROOT/pages/policies.adoc b/antora/components/comguide/modules/ROOT/pages/policies.adoc
index 5bc0546783..8c459a2442 100644
--- a/antora/components/comguide/modules/ROOT/pages/policies.adoc
+++ b/antora/components/comguide/modules/ROOT/pages/policies.adoc
@@ -8,7 +8,7 @@
-This chapter pulls together various policy documents relating to the development of Apache Isis'.
+This chapter pulls together various policy documents relating to the development of Apache Causeway'.
include::policies/versioning-policy.adoc[leveloffset=+1]
diff --git a/antora/components/comguide/modules/ROOT/pages/policies/git-policy.adoc b/antora/components/comguide/modules/ROOT/pages/policies/git-policy.adoc
index 147b28258a..914acfc3f0 100644
--- a/antora/components/comguide/modules/ROOT/pages/policies/git-policy.adoc
+++ b/antora/components/comguide/modules/ROOT/pages/policies/git-policy.adoc
@@ -25,7 +25,7 @@ And, of course, there is loads of good advice on http://stackoverflow.com/questi
== Workflow
-There are many ways of using Git, but the Apache Isis committers have adopted the following workflow:
+There are many ways of using Git, but the Apache Causeway committers have adopted the following workflow:
* create a topic branch for a feature +
+
diff --git a/antora/components/comguide/modules/ROOT/pages/policies/versioning-policy.adoc b/antora/components/comguide/modules/ROOT/pages/policies/versioning-policy.adoc
index f8dc517db0..831ae6e4cb 100644
--- a/antora/components/comguide/modules/ROOT/pages/policies/versioning-policy.adoc
+++ b/antora/components/comguide/modules/ROOT/pages/policies/versioning-policy.adoc
@@ -6,7 +6,7 @@
[#semantic-versioning]
== Semantic Versioning
-Starting from v1.0.0, Apache Isis has adopted link:http://semver.org[semantic versioning] for its versioning policy.
+Starting from v1.0.0, Apache Causeway has adopted link:http://semver.org[semantic versioning] for its versioning policy.
Version numbers are in the form `x.y.z`:
@@ -24,4 +24,4 @@ If necessary, end-users can use `<dependencyManagement>` elements to have combin
That said, this can introduce instability and so generally we recommend that end-users configure the `maven-enforcer-plugin` and its link:http://maven.apache.org/enforcer/enforcer-rules/dependencyConvergence.html[DependencyConvergence] rule.
This will help avoid "jar hell" (components having conflicting dependencies of core).
-If there is a conflict, we would ask that end-users engage with Apache Isis committers to have an updated version of the component(s) pushed out.
+If there is a conflict, we would ask that end-users engage with Apache Causeway committers to have an updated version of the component(s) pushed out.
diff --git a/antora/components/comguide/modules/ROOT/pages/post-release-successful.adoc b/antora/components/comguide/modules/ROOT/pages/post-release-successful.adoc
index 5a5544d2c7..0c9c8ccdc4 100644
--- a/antora/components/comguide/modules/ROOT/pages/post-release-successful.adoc
+++ b/antora/components/comguide/modules/ROOT/pages/post-release-successful.adoc
@@ -7,7 +7,7 @@ The release process consists of:
* the release manager xref:comguide:ROOT:cutting-a-release.adoc[cutting the release]
-* members of the Apache Isis PMC xref:comguide:ROOT:verifying-releases.adoc[verifying] and voting on the release
+* members of the Apache Causeway PMC xref:comguide:ROOT:verifying-releases.adoc[verifying] and voting on the release
* the release manager performing post-release tasks, for either a successful or an xref:comguide:ROOT:post-release-unsuccessful.adoc[unsuccessful] vote (former documented below)
@@ -22,7 +22,7 @@ Post the results to the `dev@causeway.a.o` mailing list:
[source,subs="attributes+"]
----
-[RESULT] [VOTE] Apache Isis Core release {page-isisrel}
+[RESULT] [VOTE] Apache Causeway Core release {page-isisrel}
----
using the body (alter last line as appropriate):
@@ -103,7 +103,7 @@ Any tickets that were partially implemented should be closed, and new tickets cr
=== Mark the version as released
-In JIRA, go to the link:https://issues.apache.org/jira/plugins/servlet/project-config/ISIS/versions[administration section] for the Apache Isis project and update the version as being released.
+In JIRA, go to the link:https://issues.apache.org/jira/plugins/servlet/project-config/ISIS/versions[administration section] for the Apache Causeway project and update the version as being released.
In the link:https://issues.apache.org/jira/secure/RapidBoard.jspa?rapidView=87[Kanban view] this will have the effect of marking all tickets as released (clearing the "done" column).
@@ -167,7 +167,7 @@ Validate using the http://www.w3.org/RDF/Validator/[W3C RDF Validator] service.
+
TIP: For more on DOAP files, see these link:http://projects.apache.org/doap.html[Apache policy docs].
-* Update the link:https://github.com/apache/causeway/blob/master/STATUS[STATUS] file (in root of Apache Isis' source) should be updated with details of the new release.
+* Update the link:https://github.com/apache/causeway/blob/master/STATUS[STATUS] file (in root of Apache Causeway' source) should be updated with details of the new release.
* commit the changes
+
@@ -185,7 +185,7 @@ The release is then automatically pushed to http://www.apache.org/dist/[http://w
Only the most recent release of each supported release line should be contained here, old versions should be deleted.
Each project is responsible for the structure of its directory.
-The directory structure of Apache Isis reflects the directory structure in our git source code repo:
+The directory structure of Apache Causeway reflects the directory structure in our git source code repo:
[source]
----
@@ -453,31 +453,31 @@ Log the new release in the link:https://reporter.apache.org/addrelease.html?caus
Announce the release to link:mailto:users@causeway.apache.org[users mailing list].
-For example, for a release of Apache Isis Core, use the following subject:
+For example, for a release of Apache Causeway Core, use the following subject:
[source,subs="attributes+"]
----
-[ANN] Apache Isis version {page-isisrel} Released
+[ANN] Apache Causeway version {page-isisrel} Released
----
And use the following body (summarizing the main points as required):
[source,subs="attributes+"]
----
-The Apache Isis team is pleased to announce the release of Apache Isis {page-isisrel}.
+The Apache Causeway team is pleased to announce the release of Apache Causeway {page-isisrel}.
New features in this release include:
* ...
-Full release notes are available on the Apache Isis website at [1].
+Full release notes are available on the Apache Causeway website at [1].
You can access this release directly from the Maven central repo [2].
Alternatively, download the release and build it from source [3].
Enjoy!
---The Apache Isis team
+--The Apache Causeway team
[1] https://causeway.apache.org/relnotes/{page-isisrel}/about.html
[2] https://search.maven.org
diff --git a/antora/components/comguide/modules/ROOT/pages/post-release-unsuccessful.adoc b/antora/components/comguide/modules/ROOT/pages/post-release-unsuccessful.adoc
index 77b04ec203..8a7ce3139d 100644
--- a/antora/components/comguide/modules/ROOT/pages/post-release-unsuccessful.adoc
+++ b/antora/components/comguide/modules/ROOT/pages/post-release-unsuccessful.adoc
@@ -6,7 +6,7 @@
The release process consists of:
* the release manager xref:comguide:ROOT:cutting-a-release.adoc[cutting the release]
-* members of the Apache Isis PMC xref:comguide:ROOT:verifying-releases.adoc[verifying] and voting on the release
+* members of the Apache Causeway PMC xref:comguide:ROOT:verifying-releases.adoc[verifying] and voting on the release
* the release manager performing post-release tasks, for either a xref:comguide:ROOT:post-release-successful.adoc[successful] or an unsuccessful vote (latter documented below).
If the vote did not succeed (did not achieve +3 votes after 72 hours and/or is unlikely to do so), then the vote should be closed and the following steps performed.
@@ -18,11 +18,11 @@ Note that a release manager may also decide to cancel a vote before 72 hours has
Post the results to the `dev@causeway.a.o` mailing list.
-For example, use the following subject for a vote on Apache Isis Core:
+For example, use the following subject for a vote on Apache Causeway Core:
[source,bash,subs="attributes+"]
----
-[RESULT] [VOTE] Apache Isis Core release {page-isisrel}
+[RESULT] [VOTE] Apache Causeway Core release {page-isisrel}
----
using the body (alter last line as appropriate):
diff --git a/antora/components/comguide/modules/ROOT/pages/verifying-releases.adoc b/antora/components/comguide/modules/ROOT/pages/verifying-releases.adoc
index f60101920e..d89ff15713 100644
--- a/antora/components/comguide/modules/ROOT/pages/verifying-releases.adoc
+++ b/antora/components/comguide/modules/ROOT/pages/verifying-releases.adoc
@@ -9,15 +9,15 @@
The release process consists of:
* the release manager xref:comguide:ROOT:cutting-a-release.adoc[cutting the release]
-* members of the Apache Isis PMC verifying and voting on the release (documented below)
+* members of the Apache Causeway PMC verifying and voting on the release (documented below)
* the release manager performing post-release tasks, for either a xref:comguide:ROOT:post-release-successful.adoc[successful] or an xref:comguide:ROOT:post-release-unsuccessful.adoc[unsuccessful] vote.
-This section describes some guidance on what a voter (members of the Apache Isis PMC and anyone else who wishes) is expected to do before casting their vote in order to verify a release.
+This section describes some guidance on what a voter (members of the Apache Causeway PMC and anyone else who wishes) is expected to do before casting their vote in order to verify a release.
== Background
Whenever a release manager announces a vote on a release (as per the xref:comguide:ROOT:cutting-a-release.adoc#start-voting-thread-on-dev-mailing-list[release process]) on the xref:docs:support:mailing-list.adoc#mailing-lists[dev mailing list], it is the responsibility of the project's PMC to cast their vote on the release.
-Anyone else can also vote, but only members of the Apache Isis PMC's vote are binding.
+Anyone else can also vote, but only members of the Apache Causeway PMC's vote are binding.
Per this http://www.apache.org/dev/release.html[ASF documentation], the legal requirements for an ASF release are:
@@ -57,7 +57,7 @@ The `verify-causeway-release.sh` script performs these steps:
* verifies that the `.asc` signature is correct
+
-in other words, to confirm that the release was created by an Apache Isis committer
+in other words, to confirm that the release was created by an Apache Causeway committer
* builds the framework code from source
diff --git a/antora/components/conguide/modules/ROOT/nav.adoc b/antora/components/conguide/modules/ROOT/nav.adoc
index a945666bfe..b3aace8d1e 100644
--- a/antora/components/conguide/modules/ROOT/nav.adoc
+++ b/antora/components/conguide/modules/ROOT/nav.adoc
@@ -1,6 +1,6 @@
: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 [...]
-* xref:building-apache-causeway.adoc[Building Apache Isis]
+* xref:building-apache-causeway.adoc[Building Apache Causeway]
* xref:contributing.adoc[Contributing]
diff --git a/antora/components/conguide/modules/ROOT/pages/about.adoc b/antora/components/conguide/modules/ROOT/pages/about.adoc
index 591a3dd297..90a0649899 100644
--- a/antora/components/conguide/modules/ROOT/pages/about.adoc
+++ b/antora/components/conguide/modules/ROOT/pages/about.adoc
@@ -3,5 +3,5 @@
: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 [...]
-This guide provides guidance to anyone in the community wanting to contribute to Apache Isis' ongoing development.
+This guide provides guidance to anyone in the community wanting to contribute to Apache Causeway' ongoing development.
diff --git a/antora/components/conguide/modules/ROOT/pages/building-apache-isis.adoc b/antora/components/conguide/modules/ROOT/pages/building-apache-isis.adoc
index 79e1f3ae4f..35a3189487 100644
--- a/antora/components/conguide/modules/ROOT/pages/building-apache-isis.adoc
+++ b/antora/components/conguide/modules/ROOT/pages/building-apache-isis.adoc
@@ -1,5 +1,5 @@
[[building-apache-causeway]]
-= Building Apache Isis
+= Building Apache Causeway
: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 [...]
:page-partial:
@@ -15,7 +15,7 @@ mvn clean install
== Git
-The Apache Isis source code lives in a git repo.
+The Apache Causeway source code lives in a git repo.
=== Installation
@@ -39,9 +39,9 @@ If using Mac, you might also want to check out Atlassian's http://www.atlassian.
-==== Cloning the Apache Isis repo
+==== Cloning the Apache Causeway repo
-First, clone the Apache Isis repo:
+First, clone the Apache Causeway repo:
[source,bash]
----
@@ -130,21 +130,21 @@ For further reading, see:
== Installing Java
-Apache Isis v2 is compatible with Java 11 and above, and releases are xref:comguide:ROOT:cutting-a-release.adoc[cut] using Java 11, leveraging the link:http://maven.apache.org/plugins/maven-toolchains-plugin/[Maven toolchains plugin]).
+Apache Causeway v2 is compatible with Java 11 and above, and releases are xref:comguide:ROOT:cutting-a-release.adoc[cut] using Java 11, leveraging the link:http://maven.apache.org/plugins/maven-toolchains-plugin/[Maven toolchains plugin]).
Therefore install Java 11 JDK or newer.
Note that the JRE is _not_ sufficient.
[TIP]
====
-If you intend to contribute back patches to Apache Isis, note that while you can develop using Java 11 or above within your IDE, be sure not to use any APIs more recent than Java 11.
+If you intend to contribute back patches to Apache Causeway, note that while you can develop using Java 11 or above within your IDE, be sure not to use any APIs more recent than Java 11.
====
// no longer required, I believe.
//
//=== Configure Maven toolchains plugin
//
-//If you are a committer that will be performing releases of Apache Isis, then you _must_ configure the
+//If you are a committer that will be performing releases of Apache Causeway, then you _must_ configure the
//link:http://maven.apache.org/plugins/maven-toolchains-plugin/[toolchains] plugin so that releases can be built using Java 11.
//
//This is done by placing the `toolchains.xml` file in `~/.m2` directory.
@@ -166,10 +166,10 @@ If you intend to contribute back patches to Apache Isis, note that while you can
// </toolchain>
//</toolchains>
//----
-//<.> The Apache Isis build is configured to search for the (`1.8, openjdk`) JDK toolchain.
+//<.> The Apache Causeway build is configured to search for the (`1.8, openjdk`) JDK toolchain.
//<.> adjust as necessary
//
-//The Apache Isis parent `pom.xml` activates this plugin whenever the `apache-release` profile is enabled.
+//The Apache Causeway parent `pom.xml` activates this plugin whenever the `apache-release` profile is enabled.
== Installing Maven
@@ -182,7 +182,7 @@ Set `MAVEN_OPTS` environment variable:
export MAVEN_OPTS="-Xms512m -Xmx1024m"
----
-== Building Apache Isis
+== Building Apache Causeway
To build the source code from the command line, simply go to the root directory and type:
@@ -191,7 +191,7 @@ To build the source code from the command line, simply go to the root directory
mvn clean install
----
-The first time you do this, you'll find it takes a while since Maven needs to download all of the Apache Isis prerequisites.
+The first time you do this, you'll find it takes a while since Maven needs to download all of the Apache Causeway prerequisites.
Thereafter you can speed up the build by adding the `-o` (offline flag).
To save more time still, we also recommend that you build in parallel.
@@ -229,7 +229,7 @@ where `module-xxx` and `module-yyy` correspond to profile names, as provided wit
| Description
| module-all
-| All Apache Isis Modules
+| All Apache Causeway Modules
| module-antora
| Official Project Documentation
@@ -280,7 +280,7 @@ mvn clean install -Dmodule-tooling -Dskip.essential
== Checking for Vulnerabilities
-Apache Isis configures the link:https://www.owasp.org/index.php/Main_Page[OWASP] link:https://www.owasp.org/index.php/OWASP_Dependency_Check[dependency check] link:http://jeremylong.github.io/DependencyCheck/dependency-check-maven/index.html[Maven plugin] to determine whether the framework uses libraries that are known to have security vulnerabilities.
+Apache Causeway configures the link:https://www.owasp.org/index.php/Main_Page[OWASP] link:https://www.owasp.org/index.php/OWASP_Dependency_Check[dependency check] link:http://jeremylong.github.io/DependencyCheck/dependency-check-maven/index.html[Maven plugin] to determine whether the framework uses libraries that are known to have security vulnerabilities.
To check, run:
diff --git a/antora/components/conguide/modules/ROOT/pages/contributing.adoc b/antora/components/conguide/modules/ROOT/pages/contributing.adoc
index 7a4fb2a406..3ae3d3a4fa 100644
--- a/antora/components/conguide/modules/ROOT/pages/contributing.adoc
+++ b/antora/components/conguide/modules/ROOT/pages/contributing.adoc
@@ -7,17 +7,17 @@
-This page explains how you can contribute to Apache Isis.
-You'll probably also want xref:setupguide:ROOT:about.adoc[set up your IDE] and learn xref:conguide:ROOT:building-apache-causeway.adoc[how to build Apache Isis].
+This page explains how you can contribute to Apache Causeway.
+You'll probably also want xref:setupguide:ROOT:about.adoc[set up your IDE] and learn xref:conguide:ROOT:building-apache-causeway.adoc[how to build Apache Causeway].
Thanks for considering to help out, your contributions are appreciated!
== Recommended Workflow (GitHub)
-Apache Isis' source code is hosted in at GitHub (https://github.com/apache/causeway.git[https], or ssh: `git@github.com:apache/causeway.git`).
+Apache Causeway' source code is hosted in at GitHub (https://github.com/apache/causeway.git[https], or ssh: `git@github.com:apache/causeway.git`).
As you might imagine, only committers are permitted to push changes to the GitHub repo.
-As a contributor, we recommend that you fork the https://github.com/apache/causeway.git[apache/causeway] GitHub repo, and then use your fork as a way of publishing your patches for the Apache Isis committers to apply.
+As a contributor, we recommend that you fork the https://github.com/apache/causeway.git[apache/causeway] GitHub repo, and then use your fork as a way of publishing your patches for the Apache Causeway committers to apply.
The diagram below illustrates the process:
@@ -32,9 +32,9 @@ That is:
* note the asymmetry here: the `upstream` repo (the Apache GitHub repo) is *not* the same as the `origin` repo (your fork).
. you work on your changes locally; when done, you push them to your GitHub fork
. to contribute back a change, raise a https://issues.apache.org/jira/browse/ISIS[JIRA] ticket (you will need to log in or create a new account first), and ensure your commit message is in the form: `ISIS-nnnn: ...` so that changes can be tracked (more discussion on this point below).
-In any case, before you decide to start hacking with Apache Isis, it's always worth creating a ticket in JIRA and then have a discussion about it on the xref:docs:support:mailing-list.adoc[mailing lists].
+In any case, before you decide to start hacking with Apache Causeway, it's always worth creating a ticket in JIRA and then have a discussion about it on the xref:docs:support:mailing-list.adoc[mailing lists].
. Use GitHub to raise a https://help.github.com/articles/using-pull-requests/[pull request] for your feature
-. An Apache Isis committer will review your change, and apply it if suitable.
+. An Apache Causeway committer will review your change, and apply it if suitable.
== Setting up your fork/clone
@@ -76,7 +76,7 @@ For more info on tracking branches http://git-scm.com/book/en/Git-Branching-Remo
== Commit messages
-Although with git your commits are always performed on your local repo, those commit messages become public when the patch is applied by an Apache Isis committer.
+Although with git your commits are always performed on your local repo, those commit messages become public when the patch is applied by an Apache Causeway committer.
You should take time to write a meaningful commit message that helps explain what the patch refers to; if you don't then there's a chance that your patch may be rejected and not applied.
No-one likes hard work to go to waste!
@@ -195,7 +195,7 @@ The process to raise the pull request, broadly speaking:
* Open a web browser to your GitHub fork of causeway
* Select your topic branch (pushed in the previous step) so that the pull request references the topic branch.
* Click the `Pull Request` button.
-* Check that the Apache Isis mailing list email came through.
+* Check that the Apache Causeway mailing list email came through.
== If your pull request is accepted
diff --git a/antora/components/conguide/modules/agilej/pages/about.adoc b/antora/components/conguide/modules/agilej/pages/about.adoc
index cb5e984f79..f53bc6b6d1 100644
--- a/antora/components/conguide/modules/agilej/pages/about.adoc
+++ b/antora/components/conguide/modules/agilej/pages/about.adoc
@@ -14,7 +14,7 @@ This material does not constitute an endorsement; AgileJ Structure Views is not
====
The key to using the tool is in developing a suitable filter script, a DSL.
-You can use the following script as a starting point for visualizing Apache Isis domain models:
+You can use the following script as a starting point for visualizing Apache Causeway domain models:
[source,AgileJ]
----
diff --git a/antora/components/conguide/modules/documentation/pages/about.adoc b/antora/components/conguide/modules/documentation/pages/about.adoc
index 46d1d4fc18..eb8f0e2a1f 100644
--- a/antora/components/conguide/modules/documentation/pages/about.adoc
+++ b/antora/components/conguide/modules/documentation/pages/about.adoc
@@ -3,7 +3,7 @@
: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 [...]
-The Apache Isis website and documentation are written using link:https://antora.org/[Antora] and link:https://asciidoctor.org/[Asciidoc(tor)]:
+The Apache Causeway website and documentation are written using link:https://antora.org/[Antora] and link:https://asciidoctor.org/[Asciidoc(tor)]:
* Antora is the static website generator
diff --git a/antora/components/conguide/modules/documentation/pages/building-docs-and-website.adoc b/antora/components/conguide/modules/documentation/pages/building-docs-and-website.adoc
index 994e77d53f..6bbc24d16c 100644
--- a/antora/components/conguide/modules/documentation/pages/building-docs-and-website.adoc
+++ b/antora/components/conguide/modules/documentation/pages/building-docs-and-website.adoc
@@ -2,7 +2,7 @@
: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 [...]
-The Apache Isis website and documentation are written in link:https://asciidoctor.org/[Asciidoc], using link:https://antora.org/[Antora] as a static website generator.
+The Apache Causeway website and documentation are written in link:https://asciidoctor.org/[Asciidoc], using link:https://antora.org/[Antora] as a static website generator.
== Prerequisites:
diff --git a/antora/components/conguide/modules/eclipse/pages/about.adoc b/antora/components/conguide/modules/eclipse/pages/about.adoc
index ba21339279..7ae1faea1d 100644
--- a/antora/components/conguide/modules/eclipse/pages/about.adoc
+++ b/antora/components/conguide/modules/eclipse/pages/about.adoc
@@ -6,13 +6,13 @@
Additional configuration of Eclipse for contributors (and committers):
-* Set up the link:{attachmentsdir}/Apache-Isis.importorder[import order]
+* Set up the link:{attachmentsdir}/Apache-Causeway.importorder[import order]
Also:
* set up link:{attachmentsdir}/Apache-code-style-formatting.xml[code formatting]
* set up the link:{attachmentsdir}/Apache-code-style-template.xml[code style templates]
-* set up link:{attachmentsdir}/Apache-Isis-code-style-cleanup.xml[code style cleanup]
+* set up link:{attachmentsdir}/Apache-Causeway-code-style-cleanup.xml[code style cleanup]
== Prepare for Build
diff --git a/antora/components/conguide/modules/git/pages/about.adoc b/antora/components/conguide/modules/git/pages/about.adoc
index 398de9266b..71e97d6ab4 100644
--- a/antora/components/conguide/modules/git/pages/about.adoc
+++ b/antora/components/conguide/modules/git/pages/about.adoc
@@ -7,7 +7,7 @@
This chapter describes the commands often used while working with git.
In addition to these basic commands, please make sure you have read:
-* xref:conguide:ROOT:building-apache-causeway.adoc[building Apache Isis]
+* xref:conguide:ROOT:building-apache-causeway.adoc[building Apache Causeway]
* xref:conguide:ROOT:contributing.adoc[Contributing]
* xref:comguide:ROOT:policies/git-policy.adoc[Git policy]
@@ -25,7 +25,7 @@ The `git add` command adds the changes to the file(s) to the git index (aka stag
If you were to make subsequent changes to the file these would not be committed.
The `git commit` takes all the staged changes and commits them locally.
-Note that these changes are not shared public with Apache Isis' central git repo.
+Note that these changes are not shared public with Apache Causeway' central git repo.
You can combine these two commands using `-am` flag to git commit:
@@ -70,7 +70,7 @@ git commit -m "ISIS-nnn: yada yada"
== Common Workflows
The xref:conguide:ROOT:contributing.adoc[contributing] page describes the workflow for non-committers.
-The xref:comguide:ROOT:policies/git-policy.adoc[Git policy] page describes a workflow for Apache Isis **committers**.
+The xref:comguide:ROOT:policies/git-policy.adoc[Git policy] page describes a workflow for Apache Causeway **committers**.
== Backing up a local branch
diff --git a/antora/components/conguide/modules/intellij/pages/about.adoc b/antora/components/conguide/modules/intellij/pages/about.adoc
index 48b37813c7..df42d99130 100644
--- a/antora/components/conguide/modules/intellij/pages/about.adoc
+++ b/antora/components/conguide/modules/intellij/pages/about.adoc
@@ -6,7 +6,7 @@
Additional configuration of IntelliJ for contributors (and committers).
-* Set up the link:{attachmentsdir}/Apache-Isis-importorder.xml[import order].
+* Set up the link:{attachmentsdir}/Apache-Causeway-importorder.xml[import order].
== Prepare for Build
diff --git a/antora/components/docs/modules/ROOT/pages/about.adoc b/antora/components/docs/modules/ROOT/pages/about.adoc
index e38c420540..2dfec722d0 100644
--- a/antora/components/docs/modules/ROOT/pages/about.adoc
+++ b/antora/components/docs/modules/ROOT/pages/about.adoc
@@ -10,9 +10,9 @@
|
[discrete]
-== What is Apache Isis?
+== What is Apache Causeway?
-* *xref:what-is-apache-causeway/causeway-in-pictures.adoc[Apache Isis in pictures]*
+* *xref:what-is-apache-causeway/causeway-in-pictures.adoc[Apache Causeway in pictures]*
* xref:what-is-apache-causeway/common-use-cases.adoc[Common Use Cases]
* xref:what-is-apache-causeway/screencasts.adoc[Screencasts]
@@ -186,7 +186,7 @@ _Academia_
//_Experiments_
//
//* https://github.com/isisaddons/causeway-app-neoapp[Neo4J Example]
-//* https://github.com/isisaddons/causeway-app-simpledsl[Isis DSL Example]
+//* https://github.com/isisaddons/causeway-app-simpledsl[Causeway DSL Example]
//|
diff --git a/antora/components/docs/modules/ROOT/pages/downloads/how-to.adoc b/antora/components/docs/modules/ROOT/pages/downloads/how-to.adoc
index 685497bcd1..68e3110962 100644
--- a/antora/components/docs/modules/ROOT/pages/downloads/how-to.adoc
+++ b/antora/components/docs/modules/ROOT/pages/downloads/how-to.adoc
@@ -4,7 +4,7 @@
-Apache Isis™ software is a framework for rapidly developing domain-driven apps in Java.
+Apache Causeway™ software is a framework for rapidly developing domain-driven apps in Java.
Write your business logic in entities, domain services and repositories, and the framework dynamically generates a representation of that domain model as a webapp or RESTful API.
Use for prototyping or production.
@@ -19,7 +19,7 @@ If you just want to get going quickly, we suggest using our xref:docs:starters:h
== Formal Releases
-If you want to build Apache Isis from formally released source tarballs, you can download from here:
+If you want to build Apache Causeway from formally released source tarballs, you can download from here:
* https://www.apache.org/dyn/closer.cgi/causeway/causeway-core/causeway-{page-isisrel}-source-release.zip[causeway-{page-isisrel}] (https://www.apache.org/dist/causeway/causeway-core/causeway-{page-isisrel}-source-release.zip.asc[asc], https://www.apache.org/dist/causeway/causeway-core/causeway-{page-isisrel}-source-release.zip.md5[md5])
@@ -73,8 +73,8 @@ Windows users can get binary md5 programs from these (and likely other) places:
== Source Code
-The Apache Isis source is hosted on github.
-You can download the Apache Isis source code using:
+The Apache Causeway source is hosted on github.
+You can download the Apache Causeway source code using:
[source,bash]
----
@@ -90,7 +90,7 @@ See link:https://gitbox.apache.org/setup/[gitbox setup] for more details on how
== DOAP RDF File
-The http://projects.apache.org/doap.html[description of a project] RDF file for Apache Isis can be downloaded link:https://causeway.apache.org/doap_isis.rdf[here].
+The http://projects.apache.org/doap.html[description of a project] RDF file for Apache Causeway can be downloaded link:https://causeway.apache.org/doap_isis.rdf[here].
diff --git a/antora/components/docs/modules/ROOT/pages/going-deeper/articles-and-presentations.adoc b/antora/components/docs/modules/ROOT/pages/going-deeper/articles-and-presentations.adoc
index 0bb8b34797..a712602eef 100644
--- a/antora/components/docs/modules/ROOT/pages/going-deeper/articles-and-presentations.adoc
+++ b/antora/components/docs/modules/ROOT/pages/going-deeper/articles-and-presentations.adoc
@@ -3,7 +3,7 @@
: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 [...]
-Some articles and recorded material relating to either Apache Isis (or its predecessor, the Naked Objects framework), or its 'sister' open source project on the .NET platform, Naked Objects .NET. We've *highlighted* some of the better ones…
+Some articles and recorded material relating to either Apache Causeway (or its predecessor, the Naked Objects framework), or its 'sister' open source project on the .NET platform, Naked Objects .NET. We've *highlighted* some of the better ones…
@@ -25,10 +25,10 @@ Some articles and recorded material relating to either Apache Isis (or its prede
== 2016
-* presentation, JAX London: link:https://jaxlondon.com/software-architecture-design/apache-causeway-closing-the-architecturecode-gap/[Apache Isis: closing the architecture/code gap].
+* presentation, JAX London: link:https://jaxlondon.com/software-architecture-design/apache-causeway-closing-the-architecturecode-gap/[Apache Causeway: closing the architecture/code gap].
Not videotaped, but slides/demos available *link:http://www.danhaywood.com/jaxlondon2016/[here]*.
-* presentation/live coding, Skillsmatter: link:https://skillsmatter.com/skillscasts/7892-closing-the-feedback-loop-with-apache-causeway[Closing the Feedback loop with Apache Isis]
+* presentation/live coding, Skillsmatter: link:https://skillsmatter.com/skillscasts/7892-closing-the-feedback-loop-with-apache-causeway[Closing the Feedback loop with Apache Causeway]
* tutorial, SPA 2016: "Naked Objects, 14 years on".
Slides available *link:http://www.danhaywood.com/spa2016/#/[here]*
@@ -37,17 +37,17 @@ Slides available *link:http://www.danhaywood.com/spa2016/#/[here]*
== 2014
* Presentation, BDD Exchange: link:https://skillsmatter.com/skillscasts/5638-to-those-whom-much-is-given-much-is-expected[To those whom much is given, much is expected… ] (45 min. video)
-* Presentation, JEEConf: link:https://www.youtube.com/watch?v=BNGUqZ6YE-M[Extremely rapid application development with Apache Isis] (50 min. video)
+* Presentation, JEEConf: link:https://www.youtube.com/watch?v=BNGUqZ6YE-M[Extremely rapid application development with Apache Causeway] (50 min. video)
== 2013
-* Presentation, Oredev: link:http://oredev.org/oredev2013/2013/wed-fri-conference/rrraddd-ridiculously-rapid-domain-driven-and-restful-apps-with-apache-causeway.html[RRRADDD! Ridiculously Rapid Domain-driven (and Restful) Apps With Apache Isis] (50 min. video)
-* *Article, Methods and Tools : link:http://www.methodsandtools.com/PDF/mt201302.pdf[Introducing Apache Isis]*
-* Article, SDJournal : link:http://sdjournal.org[Introducing Apache Isis]
-* Article, SDJournal: link:http://sdjournal.org[Restful Objects on Apache Isis]
-* A Prezi link:http://prezi.com/cunfhjsf8dqg/braiv-apache-causeway/[presentation on Naked Objects and Apache Isis], mixed by Thomas Eck
-* Article, Linux Magzin (german): link:http://www.linux-magazin.de/Ausgaben/2013/07/Apache-Isis[Domain-Driven Design mit Apache Isis] by Frank Pientka
+* Presentation, Oredev: link:http://oredev.org/oredev2013/2013/wed-fri-conference/rrraddd-ridiculously-rapid-domain-driven-and-restful-apps-with-apache-causeway.html[RRRADDD! Ridiculously Rapid Domain-driven (and Restful) Apps With Apache Causeway] (50 min. video)
+* *Article, Methods and Tools : link:http://www.methodsandtools.com/PDF/mt201302.pdf[Introducing Apache Causeway]*
+* Article, SDJournal : link:http://sdjournal.org[Introducing Apache Causeway]
+* Article, SDJournal: link:http://sdjournal.org[Restful Objects on Apache Causeway]
+* A Prezi link:http://prezi.com/cunfhjsf8dqg/braiv-apache-causeway/[presentation on Naked Objects and Apache Causeway], mixed by Thomas Eck
+* Article, Linux Magzin (german): link:http://www.linux-magazin.de/Ausgaben/2013/07/Apache-Causeway[Domain-Driven Design mit Apache Causeway] by Frank Pientka
== 2012
diff --git a/antora/components/docs/modules/ROOT/pages/going-deeper/books.adoc b/antora/components/docs/modules/ROOT/pages/going-deeper/books.adoc
index d5f5c46276..8ed04057ad 100644
--- a/antora/components/docs/modules/ROOT/pages/going-deeper/books.adoc
+++ b/antora/components/docs/modules/ROOT/pages/going-deeper/books.adoc
@@ -6,7 +6,7 @@
Although it has evolved since, the _Apache Isis_ framework started out as an open source implementation of the naked objects pattern.
-Indeed, the generic user interfaces provided by Apache Isis xref:vw:ROOT:about.adoc[Wicket] viewer and the xref:vro:ROOT:about.adoc[Restful Objects] viewer are both "just" naked objects implementations; the first serves up a default generic representation of domain objects for human interaction, the latter serving up representation intended for machine consumption rather than human beings.
+Indeed, the generic user interfaces provided by Apache Causeway xref:vw:ROOT:about.adoc[Wicket] viewer and the xref:vro:ROOT:about.adoc[Restful Objects] viewer are both "just" naked objects implementations; the first serves up a default generic representation of domain objects for human interaction, the latter serving up representation intended for machine consumption rather than human beings.
If the idea of naked objects is of interest, then there are a couple of books on the topic that you might want to read.
@@ -63,4 +63,4 @@ Dan Haywood
The http://restfulobjects.org[Restful Objects specification] defines a set of RESTful resources, and corresponding JSON representations, for accessing and manipulating a domain object model.
This is a comprehensive specification, running to over 200 pages in length.
-It is implemented by Apache Isis' xref:vro:ROOT:about.adoc[Restful Objects] viewer, and is also implemented by another (non-Apache) open source project, link:https://github.com/NakedObjectsGroup/NakedObjectsFramework[Naked Objects Framework].
+It is implemented by Apache Causeway' xref:vro:ROOT:about.adoc[Restful Objects] viewer, and is also implemented by another (non-Apache) open source project, link:https://github.com/NakedObjectsGroup/NakedObjectsFramework[Naked Objects Framework].
diff --git a/antora/components/docs/modules/ROOT/pages/landing-page/components.adoc b/antora/components/docs/modules/ROOT/pages/landing-page/components.adoc
index 7ede95793d..f7a819b5dc 100644
--- a/antora/components/docs/modules/ROOT/pages/landing-page/components.adoc
+++ b/antora/components/docs/modules/ROOT/pages/landing-page/components.adoc
@@ -39,6 +39,6 @@ Alternatively, you can "roll your own" (by implementing the xref:refguide:applib
== Security
-The xref:security:ROOT:about.adoc[Security Guide] describes how to configure each of the various security implementations that integrate with Apache Isis.
+The xref:security:ROOT:about.adoc[Security Guide] describes how to configure each of the various security implementations that integrate with Apache Causeway.
diff --git a/antora/components/docs/modules/ROOT/pages/landing-page/guides.adoc b/antora/components/docs/modules/ROOT/pages/landing-page/guides.adoc
index 32b6daf2b2..f51f0ddf35 100644
--- a/antora/components/docs/modules/ROOT/pages/landing-page/guides.adoc
+++ b/antora/components/docs/modules/ROOT/pages/landing-page/guides.adoc
@@ -34,4 +34,4 @@ In addition:
* *xref:security:ROOT:about.adoc[Security Guide]*
+
-Describes how to configure each of the various security implementations that integrate with Apache Isis.
+Describes how to configure each of the various security implementations that integrate with Apache Causeway.
diff --git a/antora/components/docs/modules/ROOT/pages/more-thanks/more-thanks.adoc b/antora/components/docs/modules/ROOT/pages/more-thanks/more-thanks.adoc
index b435eb6c7e..baead3065d 100644
--- a/antora/components/docs/modules/ROOT/pages/more-thanks/more-thanks.adoc
+++ b/antora/components/docs/modules/ROOT/pages/more-thanks/more-thanks.adoc
@@ -5,14 +5,14 @@
-In addition to the http://www.apache.org/foundation/thanks.html[support given to Apache Foundation as a whole], we in the Apache Isis community would also like to extend our thanks to:
+In addition to the http://www.apache.org/foundation/thanks.html[support given to Apache Foundation as a whole], we in the Apache Causeway community would also like to extend our thanks to:
[cols="1a,2a"]
|===
|image::more-thanks/ecp.png[link="http://www.eurocommercialproperties.com"]
-|Eurocommercial Properties, for sponsoring the development of Apache Isis in support of their in-house ERM.
+|Eurocommercial Properties, for sponsoring the development of Apache Causeway in support of their in-house ERM.
|image::more-thanks/s101_170.png[link="http://structure101.com"]
diff --git a/antora/components/docs/modules/ROOT/pages/what-is-apache-isis/isis-in-pictures.adoc b/antora/components/docs/modules/ROOT/pages/what-is-apache-isis/isis-in-pictures.adoc
index 9346b4a282..fd3d031aa6 100644
--- a/antora/components/docs/modules/ROOT/pages/what-is-apache-isis/isis-in-pictures.adoc
+++ b/antora/components/docs/modules/ROOT/pages/what-is-apache-isis/isis-in-pictures.adoc
@@ -1,10 +1,10 @@
-= Apache Isis in Pictures
+= Apache Causeway in Pictures
: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 [...]
// TODO: v2: NICE-TO-HAVE: these screenshots should be updated, but first need to port the todoapp over first (which also means the various modules from incode-platform)
-On this page we want to show you what an Apache Isis application looks like, running on the xref:vw:ROOT:about.adoc[Web UI (Wicket viewer)].
+On this page we want to show you what an Apache Causeway application looks like, running on the xref:vw:ROOT:about.adoc[Web UI (Wicket viewer)].
The screenshots below are taken from a "Todo" application.
NOTE: these screenshots are based on an app running against v1.13 and v1.10 of the framework.
@@ -16,9 +16,9 @@ Let's start with the basics...
=== Sign-in
-Apache Isis integrates with a variety of authentication mechanisms, including link:http://shiro.apache.org[Apache Shiro], link:https://spring.io/projects/spring-security[Spring Security] and link:https://www.keycloak.org/[Keycloak].
+Apache Causeway integrates with a variety of authentication mechanisms, including link:http://shiro.apache.org[Apache Shiro], link:https://spring.io/projects/spring-security[Spring Security] and link:https://www.keycloak.org/[Keycloak].
-The xref:security:ROOT:about.adoc[SecMan extension] provides a well-features subdomain of users, roles and permissions against features derived from the Apache Isis metamodel.
+The xref:security:ROOT:about.adoc[SecMan extension] provides a well-features subdomain of users, roles and permissions against features derived from the Apache Causeway metamodel.
@@ -26,7 +26,7 @@ image::what-is-apache-causeway/causeway-in-pictures/010-login.png[width="800px"]
=== Install Fixtures
-Apache Isis has lots of features to help you prototype and then fully test your application.
+Apache Causeway has lots of features to help you prototype and then fully test your application.
One such are fixture scripts, which allow pre-canned data to be installed in the running application.
This is great to act as the starting point for identifying new stories; later on when the feature is being implemented, the same fixture script can be re-used within that feature's integration tests.
(More on tests later).
@@ -36,7 +36,7 @@ image::what-is-apache-causeway/causeway-in-pictures/020-install-fixtures.png[wid
=== Dashboard and View Models
-Most of the time the end-user interacts with representations of persistent domain entities, but Apache Isis also supports view models which can aggregate data from multiple sources.
+Most of the time the end-user interacts with representations of persistent domain entities, but Apache Causeway also supports view models which can aggregate data from multiple sources.
The todoapp example uses a "dashboard" view model to list todo items not yet done vs those completed.
image::what-is-apache-causeway/causeway-in-pictures/030-dashboard-view-model.png[width="800px"]
@@ -54,7 +54,7 @@ There are no controllers or HTML to write.
image::what-is-apache-causeway/causeway-in-pictures/040-domain-entity.png[width="800px"]
-In addition to the domain entity, Apache Isis allows layout metadata hints to be provided, for example to specify the grouping of properties, the positioning of those groups into columns, the association of actions (the buttons) with properties or collections, the icons on the buttons, and so on.
+In addition to the domain entity, Apache Causeway allows layout metadata hints to be provided, for example to specify the grouping of properties, the positioning of those groups into columns, the association of actions (the buttons) with properties or collections, the icons on the buttons, and so on.
This metadata can be specified either as annotations or in XML form.
The benefit of the latter is that it can be updated (and the UI redrawn) without restarting the app.
@@ -88,7 +88,7 @@ We sometimes use the term "behaviourally complete" for such domain objects.
=== Mixins
As an alternative to placing actions (business logic) on a domain object, it can instead be placed inside a mixin object.
-When an object is rendered by Apache Isis, the mixin "contributes" its behaviour to the domain object (similar to aspect-oriented traits).
+When an object is rendered by Apache Causeway, the mixin "contributes" its behaviour to the domain object (similar to aspect-oriented traits).
In the screenshot below the highlighted "export as xml" action, the "relative priority" property (and "previous" and "next" actions) the "similar to" collection and the two "as DTO" actions are all contributed by mixins:
@@ -97,7 +97,7 @@ image::what-is-apache-causeway/causeway-in-pictures/065-contributions.png[width=
== Extensible Views
-The Apache Isis viewer is implemented using http://wicket.apache.org[Apache Wicket], and has been designed to be extensible.
+The Apache Causeway viewer is implemented using http://wicket.apache.org[Apache Wicket], and has been designed to be extensible.
For example, when a collection of objects is rendered, this is just one of several views, as shown in the selector drop-down:
image::what-is-apache-causeway/causeway-in-pictures/070-pluggable-views.png[width="800px"]
@@ -174,19 +174,19 @@ image::what-is-apache-causeway/causeway-in-pictures/180-app-user-entity.png[widt
-If not all of these properties are required, then they can be hidden either using security or though Apache Isis' internal event bus (described below).
+If not all of these properties are required, then they can be hidden either using security or though Apache Causeway' internal event bus (described below).
Conversely, additional properties can be "grafted onto" the user using the contributed properties/collections discussed previously.
=== Themes
-Apache Isis' Wicket viewer uses http://getbootstrap.com[Twitter Bootstrap], which means that it can be themed.
+Apache Causeway' Wicket viewer uses http://getbootstrap.com[Twitter Bootstrap], which means that it can be themed.
If more than one theme has been configured for the app, then the viewer allows the end-user to switch their theme:
image::what-is-apache-causeway/causeway-in-pictures/190-switch-theme.png[width="800px"]
== REST API
-In addition to Apache Isis' Wicket viewer, it also provides a rich REST API with a full set of hypermedia controls, generated automatically from the domain objects (entities and view models).
+In addition to Apache Causeway' Wicket viewer, it also provides a rich REST API with a full set of hypermedia controls, generated automatically from the domain objects (entities and view models).
The framework provides two default representations, one an implementation of the http://restfulobjects.org[Restful Objects] spec, the other a simplified representation suitable for custom JavaScript apps.
Other representations can be plugged in.
@@ -203,7 +203,7 @@ image::what-is-apache-causeway/causeway-in-pictures/205-swagger-ui.png[width="80
== Integration Testing Support
-Earlier on we noted that Apache Isis allows fixtures to be installed through the UI.
+Earlier on we noted that Apache Causeway allows fixtures to be installed through the UI.
These same fixture scripts can be reused within integration tests.
For example, the code snippet below shows how the `FixtureScripts` service injected into an integration test can then be used to set up data:
@@ -218,17 +218,17 @@ image::what-is-apache-causeway/causeway-in-pictures/220-testing-happy-case.png[w
-To simulate the business rules enforced by Apache Isis, the domain object can be "wrapped" in a proxy.
-For example, if using the Wicket viewer then Apache Isis will enforce the rule (implemented in the `ToDoItem` class itself) that a completed item cannot have the "completed" action invoked upon it.
+To simulate the business rules enforced by Apache Causeway, the domain object can be "wrapped" in a proxy.
+For example, if using the Wicket viewer then Apache Causeway will enforce the rule (implemented in the `ToDoItem` class itself) that a completed item cannot have the "completed" action invoked upon it.
The wrapper simulates this by throwing an appropriate exception:
image::what-is-apache-causeway/causeway-in-pictures/230-testing-wrapper-factory.png[width="550px"]
== Internal Event Bus
-Contributions, discussed earlier, are an important tool in ensuring that the packages within your Apache Isis application are decoupled; by extracting out actions the order of dependency between packages can effectively be reversed.
+Contributions, discussed earlier, are an important tool in ensuring that the packages within your Apache Causeway application are decoupled; by extracting out actions the order of dependency between packages can effectively be reversed.
-Another important tool to ensure your codebase remains maintainable is Apache Isis' internal event bus.
+Another important tool to ensure your codebase remains maintainable is Apache Causeway' internal event bus.
It is probably best explained by example; the code below says that the "complete" action should emit a `ToDoItem.Completed` event:
image::what-is-apache-causeway/causeway-in-pictures/240-domain-events.png[width="400px"]
diff --git a/antora/components/docs/modules/ROOT/pages/what-is-apache-isis/screencasts-older.adoc b/antora/components/docs/modules/ROOT/pages/what-is-apache-isis/screencasts-older.adoc
index acc4125176..46599329cc 100644
--- a/antora/components/docs/modules/ROOT/pages/what-is-apache-isis/screencasts-older.adoc
+++ b/antora/components/docs/modules/ROOT/pages/what-is-apache-isis/screencasts-older.adoc
@@ -17,9 +17,9 @@ More recent screencasts can be found link:./screencasts.html[here].
|How it works (v1.1.0)+
-_How Apache Isis builds a webapp from the underlying domain object model_
+_How Apache Causeway builds a webapp from the underlying domain object model_
-_This screencast is for Apache Isis v1.1.0 (ie very out of date)_
+_This screencast is for Apache Causeway v1.1.0 (ie very out of date)_
|video::ludOLyi6VyY[youtube,width="420px",height="315px"]
@@ -47,7 +47,7 @@ _A run-through of the main features of the http://github.com/apache/causeway-app
|Setting up Eclipse +
-_How to import an Apache Isis maven-based application into Eclipse and configure to use with JDO/DataNucleus_ +
+_How to import an Apache Causeway maven-based application into Eclipse and configure to use with JDO/DataNucleus_ +
NB: when configuring DataNucleus for the *dom* project, make sure you are in the 'Java perspective', not the 'Java EE perspective'). +
@@ -59,7 +59,7 @@ Learn more xref:setupguide:eclipse:about.adoc[here]
|Setting up IntelliJ +
-_How to import an Apache Isis maven-based application into IntelliJ and run the app._ +
+_How to import an Apache Causeway maven-based application into IntelliJ and run the app._ +
Learn more xref:setupguide:intellij:about.adoc[here]
@@ -72,7 +72,7 @@ Learn more xref:setupguide:intellij:about.adoc[here]
-== Isis Add-on Modules
+== Causeway Add-on Modules
[cols="2a,2a"]
|===
@@ -107,7 +107,7 @@ Learn more at the (non-ASF) link:https://platform.incode.org[Incode Platform^]'s
-|Bulk updates in Apache Isis (v1.5.0) +
+|Bulk updates in Apache Causeway (v1.5.0) +
_Using the (non-ASF) link:https://platform.incode.org[Incode Platform^]'s excel module and view models to perform bulk updates)._
@@ -120,7 +120,7 @@ _Using the (non-ASF) link:https://platform.incode.org[Incode Platform^]'s excel
-== Wicket Viewer and Isis Add-ons
+== Wicket Viewer and Causeway Add-ons
[cols="2a,2a"]
|===
@@ -168,7 +168,7 @@ _Posting to the "Objects of Type" resource"_
== JRebel Integration
-_Develop your app without having to redeploy using link:http://zeroturnaround.com/software/jrebel/[JRebel] and an link:https://github.com/danhaywood/causeway-jrebel-plugin[Isis plugin] for JRebel._
+_Develop your app without having to redeploy using link:http://zeroturnaround.com/software/jrebel/[JRebel] and an link:https://github.com/danhaywood/causeway-jrebel-plugin[Causeway plugin] for JRebel._
[cols="2a,2a"]
|===
diff --git a/antora/components/docs/modules/ROOT/pages/what-is-apache-isis/screencasts.adoc b/antora/components/docs/modules/ROOT/pages/what-is-apache-isis/screencasts.adoc
index 4d9de386e0..98f958f45f 100644
--- a/antora/components/docs/modules/ROOT/pages/what-is-apache-isis/screencasts.adoc
+++ b/antora/components/docs/modules/ROOT/pages/what-is-apache-isis/screencasts.adoc
@@ -6,7 +6,7 @@
// TODO: v2: NICE-TO-HAVE: update these screenshots for v2
-We've prepared a number of screencasts to help you see what Apache Isis has to offer.
+We've prepared a number of screencasts to help you see what Apache Causeway has to offer.
While these each follow on from each other, you should be able to watch them in any order; the typical duration is
3 minutes.
@@ -45,7 +45,7 @@ include::screencasts/playlists.adoc[]
//|https://www.youtube.com/watch?v=RQ_FFYd7npU[000^] +
-//Searching and using the Apache Isis docs
+//Searching and using the Apache Causeway docs
//|X||||||||||
@@ -120,7 +120,7 @@ Using the Swagger UI to access the xref:vro:ROOT:about.adoc[REST API] automatica
// FIXME: currently removed in v2, may reinstate
//|link:https://www.youtube.com/watch?v=yOh3WphhR1E[010^].
-//Using the xref:refguide:mvn:about.adoc[Apache Isis maven plugin] to validate domain object models during the build process (rather than at runtime).
+//Using the xref:refguide:mvn:about.adoc[Apache Causeway maven plugin] to validate domain object models during the build process (rather than at runtime).
//||||||||X|||
@@ -207,20 +207,20 @@ Using xref:userguide:fun:ui.adoc#object-layout[dynamic (XML) layouts] to specify
include::screencasts/playlists.adoc[]
|link:https://www.youtube.com/watch?v=0d713-V4vrg[019^] +
-Demonstrates how Apache Isis' xref:vw:ROOT:about.adoc[Web UI (Wicket viewer)] remembers the state of rendered domain objects, and how the end-user of the
+Demonstrates how Apache Causeway' xref:vw:ROOT:about.adoc[Web UI (Wicket viewer)] remembers the state of rendered domain objects, and how the end-user of the
application can clear these UI hints using the (framework-provided) xref:refguide:viewer:index/wicket/viewer/mixins/Object_clearHints.adoc["clear hints"] mixin action.
|||X||||||||
|link:https://www.youtube.com/watch?v=Kqch-XNlBMA[020^] +
-Demonstrates how the end-user can copy and share URLs for domain objects - including UI hints - using Apache Isis' xref:vw:ROOT:about.adoc[Web UI (Wicket viewer)].
+Demonstrates how the end-user can copy and share URLs for domain objects - including UI hints - using Apache Causeway' xref:vw:ROOT:about.adoc[Web UI (Wicket viewer)].
|||X||||||||
|link:https://www.youtube.com/watch?v=a0QQLT_16To[021^] +
-Demonstrates how the end-user can use bookmarks and breadcrumbs within Apache Isis' xref:vw:ROOT:about.adoc[Web UI (Wicket viewer)], and how the developer can ensure that xref:refguide:applib:index/annotation/DomainObjectLayout.adoc#bookmarking[domain objects] and (xref:refguide:applib:index/annotation/Action.adoc#semantics[query-only]) xref:refguide:applib:index/annotation/ActionLayout.adoc#bookmarking[actions] can be bookmarked.
+Demonstrates how the end-user can use bookmarks and breadcrumbs within Apache Causeway' xref:vw:ROOT:about.adoc[Web UI (Wicket viewer)], and how the developer can ensure that xref:refguide:applib:index/annotation/DomainObjectLayout.adoc#bookmarking[domain objects] and (xref:refguide:applib:index/annotation/Action.adoc#semantics[query-only]) xref:refguide:applib:index/annotation/ActionLayout.adoc#bookmarking[actions] can be bookmarked.
|||X||||||||
@@ -466,12 +466,12 @@ include::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:https://platform.incode.org[Incode Platform^]'s excel wicket component.
+Configuring an Apache Causeway 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
+Configuring an Apache Causeway app to allow tables of domain objects with date information to be rendered on a full-page
calendar, using the (non-ASF) link:https://platform.incode.org[Incode Platform^]'s fullcalendar2 wicket
component.
|||||X||||||
@@ -480,12 +480,12 @@ component.
|link:https://www.youtube.com/watch?v=0YoFa44Xr6M[049^] +
Using the xref:refguide:applib:index/annotation/Programmatic.adoc[@Programmatic] annotation to exclude methods from a domain object
(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).
+otherwise be part of the Apache Causeway 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,
+Configuring an Apache Causeway app to allow tables of domain objects with location information to be rendered on map,
using the (non-ASF) link:https://platform.incode.org[Incode Platform^]'s gmap3 wicket component.
|||||X||||||
diff --git a/antora/components/docs/modules/ROOT/partials/module-nav/what-is-apache-isis.adoc b/antora/components/docs/modules/ROOT/partials/module-nav/what-is-apache-isis.adoc
index 46b5a897f7..b24a987510 100644
--- a/antora/components/docs/modules/ROOT/partials/module-nav/what-is-apache-isis.adoc
+++ b/antora/components/docs/modules/ROOT/partials/module-nav/what-is-apache-isis.adoc
@@ -1,7 +1,7 @@
: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 [...]
-* What is Apache Isis?
-** xref:what-is-apache-causeway/causeway-in-pictures.adoc[Apache Isis in pictures]
+* What is Apache Causeway?
+** xref:what-is-apache-causeway/causeway-in-pictures.adoc[Apache Causeway in pictures]
** xref:what-is-apache-causeway/common-use-cases.adoc[Common Use Cases]
** xref:what-is-apache-causeway/screencasts.adoc[Screencasts]
diff --git a/antora/components/docs/modules/resources/pages/about.adoc b/antora/components/docs/modules/resources/pages/about.adoc
index 4ed1a1d42c..6c92448c5c 100644
--- a/antora/components/docs/modules/resources/pages/about.adoc
+++ b/antora/components/docs/modules/resources/pages/about.adoc
@@ -2,7 +2,7 @@
: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 [...]
-The following resources are available to help you develop your Apache Isis applications:
+The following resources are available to help you develop your Apache Causeway applications:
* xref:docs:resources:cheatsheet.adoc[cheat sheet]
* xref:docs:resources:icons.adoc[icons]
diff --git a/antora/components/docs/modules/resources/pages/cheatsheet.adoc b/antora/components/docs/modules/resources/pages/cheatsheet.adoc
index ce855f2f5e..b210297e85 100644
--- a/antora/components/docs/modules/resources/pages/cheatsheet.adoc
+++ b/antora/components/docs/modules/resources/pages/cheatsheet.adoc
@@ -3,7 +3,7 @@
: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 [...]
-This cheat sheet summarises the main programming conventions to follow when writing an Apache Isis application.
+This cheat sheet summarises the main programming conventions to follow when writing an Apache Causeway application.
pass:[<br/>]
diff --git a/antora/components/docs/modules/resources/pages/icons.adoc b/antora/components/docs/modules/resources/pages/icons.adoc
index 7cab92928c..b785cfb747 100644
--- a/antora/components/docs/modules/resources/pages/icons.adoc
+++ b/antora/components/docs/modules/resources/pages/icons.adoc
@@ -3,7 +3,7 @@
: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 [...]
-Most Apache Isis viewers use icons to help identify domain objects in the user interface.
+Most Apache Causeway viewers use icons to help identify domain objects in the user interface.
It's a good idea to ensure that these are styled consistently.
Here are some open source icon sets for both personal and commercial use (though some require a link back to the authors website):
diff --git a/antora/components/docs/modules/support/pages/mailing-list.adoc b/antora/components/docs/modules/support/pages/mailing-list.adoc
index 1eea19277d..f3ee9d69df 100644
--- a/antora/components/docs/modules/support/pages/mailing-list.adoc
+++ b/antora/components/docs/modules/support/pages/mailing-list.adoc
@@ -7,7 +7,7 @@
-Apache Isis has two public mailing lists.
+Apache Causeway has two public mailing lists.
.Table caption
[cols="2,3,2,3", options="header"]
diff --git a/antora/components/refguide-index/modules/applib/pages/index/annotation/hooks/Action_025-execution-publishing.adoc b/antora/components/refguide-index/modules/applib/pages/index/annotation/hooks/Action_025-execution-publishing.adoc
index 066b79b8b5..e4c36ba68e 100644
--- a/antora/components/refguide-index/modules/applib/pages/index/annotation/hooks/Action_025-execution-publishing.adoc
+++ b/antora/components/refguide-index/modules/applib/pages/index/annotation/hooks/Action_025-execution-publishing.adoc
@@ -6,7 +6,7 @@
The xref:refguide:applib:index/annotation/Action.adoc#executionPublishing[executionPublishing()] element determines whether and how an action invocation is published via the registered implementation of xref:refguide:applib:index/services/publishing/spi/ExecutionSubscriber.adoc[ExecutionSubscriber].
-A common use case is to notify external "downstream" systems of changes in the state of the Apache Isis application.
+A common use case is to notify external "downstream" systems of changes in the state of the Apache Causeway application.
The xref:refguide:config:sections/causeway.applib.adoc#causeway.applib.annotation.property.execution-publishing[causeway.applib.annotation.property.execution-publishing] configuration property is used to determine the whether the action invocation is published:
diff --git a/antora/components/refguide-index/modules/applib/pages/index/annotation/hooks/DomainObjectLayout_024-named.adoc b/antora/components/refguide-index/modules/applib/pages/index/annotation/hooks/DomainObjectLayout_024-named.adoc
index 3473f4ce45..4b61b7f74e 100644
--- a/antora/components/refguide-index/modules/applib/pages/index/annotation/hooks/DomainObjectLayout_024-named.adoc
+++ b/antora/components/refguide-index/modules/applib/pages/index/annotation/hooks/DomainObjectLayout_024-named.adoc
@@ -27,7 +27,7 @@ public class CustomerImpl implements Customer{
==== Plural form
-When Apache Isis displays a standalone collection of several objects, it will label the collection using the plural form of the object type.
+When Apache Causeway displays a standalone collection of several objects, it will label the collection using the plural form of the object type.
By default the plural name will be derived from the end of the singular name, with support for some basic English language defaults (eg using "ies" for names ending with a "y").
For irregular plurals it's possible to specify a plural form using the xref:refguide:applib:index/annotation/DomainObjectLayout.adoc#plural[plural] element.
diff --git a/antora/components/refguide-index/modules/applib/pages/index/annotation/hooks/DomainObject_022-nature.adoc b/antora/components/refguide-index/modules/applib/pages/index/annotation/hooks/DomainObject_022-nature.adoc
index bdd6c349fe..67ac387dde 100644
--- a/antora/components/refguide-index/modules/applib/pages/index/annotation/hooks/DomainObject_022-nature.adoc
+++ b/antora/components/refguide-index/modules/applib/pages/index/annotation/hooks/DomainObject_022-nature.adoc
@@ -24,7 +24,7 @@ Specifically, the nature must be one of:
* `ENTITY`
+
-indicates that the domain object is an entity whose persistence is managed internally by Apache Isis, using the JDO/DataNucleus objectstore.
+indicates that the domain object is an entity whose persistence is managed internally by Apache Causeway, using the JDO/DataNucleus objectstore.
* `MIXIN`
+
@@ -58,7 +58,7 @@ Those natures that indicate the domain object is an entity (of some sort or anot
====
For `VIEW_MODEL` domain objects the state of the object is encoded into its internal OID (represented ultimately as its URL), and is recreated directly from that URL.
-Because this particular implementation was originally added to Apache Isis in support of view models, the term was also used for the logically different external entities and in-memory entities.
+Because this particular implementation was originally added to Apache Causeway in support of view models, the term was also used for the logically different external entities and in-memory entities.
The benefit of `nature()` is that it allows the developer to properly characterize the layer (domain vs application) that an entity lives, thus avoiding confusion as "view model" (the implementation technique) and "view model" (the application layer concept).
====
diff --git a/antora/components/refguide-index/modules/applib/pages/index/annotation/hooks/Facets_010-examples-and-usage.adoc b/antora/components/refguide-index/modules/applib/pages/index/annotation/hooks/Facets_010-examples-and-usage.adoc
index 22c40bf81e..9dadb87871 100644
--- a/antora/components/refguide-index/modules/applib/pages/index/annotation/hooks/Facets_010-examples-and-usage.adoc
+++ b/antora/components/refguide-index/modules/applib/pages/index/annotation/hooks/Facets_010-examples-and-usage.adoc
@@ -2,4 +2,4 @@
//== Notes
//
-//`FacetFactory` is an important internal API that is used by Apache Isis to build the metamodel.
+//`FacetFactory` is an important internal API that is used by Apache Causeway to build the metamodel.
diff --git a/antora/components/refguide-index/modules/applib/pages/index/annotation/hooks/Programmatic_010-examples-and-usage.adoc b/antora/components/refguide-index/modules/applib/pages/index/annotation/hooks/Programmatic_010-examples-and-usage.adoc
index 8a1f707781..a095f55775 100644
--- a/antora/components/refguide-index/modules/applib/pages/index/annotation/hooks/Programmatic_010-examples-and-usage.adoc
+++ b/antora/components/refguide-index/modules/applib/pages/index/annotation/hooks/Programmatic_010-examples-and-usage.adoc
@@ -17,6 +17,6 @@ public class Customer implements Comparable<Customer> {
}
----
-Note that `@Programmatic` is not the same as `@Action(hidden=Where.EVERYWHERE)` or `@Property(hidden=Where.EVERYWHERE)` etc; it actually means that the class member will not be part of the Apache Isis metamodel.
+Note that `@Programmatic` is not the same as `@Action(hidden=Where.EVERYWHERE)` or `@Property(hidden=Where.EVERYWHERE)` etc; it actually means that the class member will not be part of the Apache Causeway metamodel.
diff --git a/antora/components/refguide-index/modules/applib/pages/index/annotation/hooks/Property_021-optionality.adoc b/antora/components/refguide-index/modules/applib/pages/index/annotation/hooks/Property_021-optionality.adoc
index c989d8e93f..94f5f84495 100644
--- a/antora/components/refguide-index/modules/applib/pages/index/annotation/hooks/Property_021-optionality.adoc
+++ b/antora/components/refguide-index/modules/applib/pages/index/annotation/hooks/Property_021-optionality.adoc
@@ -4,15 +4,15 @@
:page-partial:
-By default, Apache Isis assumes that all properties of an domain object or view model are required (mandatory).
+By default, Apache Causeway assumes that all properties of an domain object or view model are required (mandatory).
The xref:applib:index/annotation/Property.adoc#optionality[optionality()] attribute allows this to be relaxed.
The attribute is also supported for xref:refguide:applib:index/annotation/Parameter.adoc#optionality[parameters].
That said, properties are most commonly defined on persistent domain objects (entities), in which case the JDO xref:refguide:applib-ant:Column.adoc[@Column] should be specified.
-Apache Isis can infer the maxLength directly from the equivalent @Column#length() annotation.
+Apache Causeway can infer the maxLength directly from the equivalent @Column#length() annotation.
That said, properties are most commonly defined on persistent domain objects (entities), in which case the JDO xref:refguide:applib-ant:Column.adoc[@Column] will in any case need to be specified.
-Apache Isis can infer the `optionality` semantic directly from the equivalent `@Column#allowsNull()` annotation/attribute.
+Apache Causeway can infer the `optionality` semantic directly from the equivalent `@Column#allowsNull()` annotation/attribute.
For example:
@@ -35,10 +35,10 @@ In this case there is no need for the `@Property#optionality` attribute.
== Mismatched defaults
-If the `@Column#allowsNull` attribute is omitted and the `@Property#optionality() attribute is also omitted, then note that Isis' defaults and JDO's defaults differ.
-Specifically, Isis always assumes properties are mandatory, whereas JDO specifies that primitives are mandatory, but all reference types are optional.
+If the `@Column#allowsNull` attribute is omitted and the `@Property#optionality() attribute is also omitted, then note that Causeway' defaults and JDO's defaults differ.
+Specifically, Causeway always assumes properties are mandatory, whereas JDO specifies that primitives are mandatory, but all reference types are optional.
-When Apache Isis initializes it checks for these mismatches during its metamodel validation phase, and will fail to boot ("fail-fast") if there is a mismatch.
+When Apache Causeway initializes it checks for these mismatches during its metamodel validation phase, and will fail to boot ("fail-fast") if there is a mismatch.
The fix is usually to add the `@Column#allowsNull()` annotation/attribute.
== Superclass inheritance type
@@ -68,7 +68,7 @@ public class CreditCardPaymentMethod extends PaymentMethod {
}
----
-Alternatively, you could rely on the fact that Apache Isis never looks at fields (whereas JDO does) and move the JDO annotation to the field:
+Alternatively, you could rely on the fact that Apache Causeway never looks at fields (whereas JDO does) and move the JDO annotation to the field:
[source,java]
----
@@ -86,7 +86,7 @@ public class CreditCardPaymentMethod extends PaymentMethod {
}
----
-However this at first glance this might be read as meaning that the property is optional whereas Apache Isis' default (required) applies.
+However this at first glance this might be read as meaning that the property is optional whereas Apache Causeway' default (required) applies.
== Non-persistent properties
diff --git a/antora/components/refguide-index/modules/applib/pages/index/annotation/hooks/Property_023-maxLength.adoc b/antora/components/refguide-index/modules/applib/pages/index/annotation/hooks/Property_023-maxLength.adoc
index df9ae1aca5..64d539b6e3 100644
--- a/antora/components/refguide-index/modules/applib/pages/index/annotation/hooks/Property_023-maxLength.adoc
+++ b/antora/components/refguide-index/modules/applib/pages/index/annotation/hooks/Property_023-maxLength.adoc
@@ -9,7 +9,7 @@ The xref:applib:index/annotation/Property.adoc#maxLength[maxLength()] attribute
The attribute It is ignored if applied to properties of any other type.
That said, properties are most commonly defined on persistent domain objects (entities), in which case the JDO xref:refguide:applib-ant:Column.adoc[@Column] will in any case need to be specified.
-Apache Isis can infer the `maxLength` semantic directly from the equivalent `@Column#length()` annotation/attribute.
+Apache Causeway can infer the `maxLength` semantic directly from the equivalent `@Column#length()` annotation/attribute.
For example:
diff --git a/antora/components/refguide-index/modules/applib/pages/index/annotation/hooks/Property_027-execution-publishing.adoc b/antora/components/refguide-index/modules/applib/pages/index/annotation/hooks/Property_027-execution-publishing.adoc
index 2a59f8dad5..af2d717ffb 100644
--- a/antora/components/refguide-index/modules/applib/pages/index/annotation/hooks/Property_027-execution-publishing.adoc
+++ b/antora/components/refguide-index/modules/applib/pages/index/annotation/hooks/Property_027-execution-publishing.adoc
@@ -6,7 +6,7 @@
The xref:refguide:applib:index/annotation/Property.adoc#executionPublishing[executionPublishing()] element determines whether and how a property edit is published via the registered implementation of xref:refguide:applib:index/services/publishing/spi/ExecutionSubscriber.adoc[ExecutionSubscriber].
-A common use case is to notify external "downstream" systems of changes in the state of the Apache Isis application.
+A common use case is to notify external "downstream" systems of changes in the state of the Apache Causeway application.
The xref:refguide:config:sections/causeway.applib.adoc#causeway.applib.annotation.property.execution-publishing[causeway.applib.annotation.property.execution-publishing] configuration property is used to determine the whether the property edits are published:
diff --git a/antora/components/refguide-index/modules/applib/pages/index/mixins/dto/hooks/Dto_see-also.adoc b/antora/components/refguide-index/modules/applib/pages/index/mixins/dto/hooks/Dto_see-also.adoc
index 4da5cb755d..225d8e93e3 100644
--- a/antora/components/refguide-index/modules/applib/pages/index/mixins/dto/hooks/Dto_see-also.adoc
+++ b/antora/components/refguide-index/modules/applib/pages/index/mixins/dto/hooks/Dto_see-also.adoc
@@ -62,7 +62,7 @@ public class ToDoItemV1_1 implements Dto { // <.>
[#versioning]
=== Versioning
-The whole point of using DTOs (in Apache Isis, at least) is to define a formal contact between two inter-operating but independent applications.
+The whole point of using DTOs (in Apache Causeway, at least) is to define a formal contact between two inter-operating but independent applications.
Since the only thing we can predict about the future with any certainty is that one or both of these applications will change, we should version DTOs from the get-go.
This allows us to make changes going forward without unnecessarily breaking existing consumers of the data.
diff --git a/antora/components/refguide-index/modules/applib/pages/index/services/clock/hooks/ClockService_020-examples-and-usage.adoc b/antora/components/refguide-index/modules/applib/pages/index/services/clock/hooks/ClockService_020-examples-and-usage.adoc
index 950c8ed4e1..957183bda4 100644
--- a/antora/components/refguide-index/modules/applib/pages/index/services/clock/hooks/ClockService_020-examples-and-usage.adoc
+++ b/antora/components/refguide-index/modules/applib/pages/index/services/clock/hooks/ClockService_020-examples-and-usage.adoc
@@ -14,7 +14,7 @@ While instantiating a `java.util.Date` to current the current time is painless e
Therefore it's common to provide a domain service whose responsibility is to provide the current time.
This service can be injected into any domain object (and can be mocked out for unit testing).
-Apache Isis provides such a facade through the `ClockService`.
+Apache Causeway provides such a facade through the `ClockService`.
== See also
diff --git a/antora/components/refguide-index/modules/applib/pages/index/services/confview/hooks/ConfigurationViewService_020-examples-and-usage.adoc b/antora/components/refguide-index/modules/applib/pages/index/services/confview/hooks/ConfigurationViewService_020-examples-and-usage.adoc
index 7446bc23ad..2d09e72433 100644
--- a/antora/components/refguide-index/modules/applib/pages/index/services/confview/hooks/ConfigurationViewService_020-examples-and-usage.adoc
+++ b/antora/components/refguide-index/modules/applib/pages/index/services/confview/hooks/ConfigurationViewService_020-examples-and-usage.adoc
@@ -4,7 +4,7 @@
== Related Services
-* The configuration properties for Apache Isis can also be obtained from the xref:refguide:config:about.adoc#isisconfiguration-domain-service[IsisConfiguration] domain service.
+* The configuration properties for Apache Causeway can also be obtained from the xref:refguide:config:about.adoc#isisconfiguration-domain-service[IsisConfiguration] domain service.
These provide link:https://docs.spring.io/spring-boot/docs/current/reference/html/spring-boot-features.html#boot-features-external-config-typesafe-configuration-properties[type-safe] access to all `causeway.*` configuration properties.
+
[NOTE]
diff --git a/antora/components/refguide-index/modules/applib/pages/index/services/eventbus/hooks/EventBusService_020-examples-and-usage.adoc b/antora/components/refguide-index/modules/applib/pages/index/services/eventbus/hooks/EventBusService_020-examples-and-usage.adoc
index 2262017536..9ae9345dc1 100644
--- a/antora/components/refguide-index/modules/applib/pages/index/services/eventbus/hooks/EventBusService_020-examples-and-usage.adoc
+++ b/antora/components/refguide-index/modules/applib/pages/index/services/eventbus/hooks/EventBusService_020-examples-and-usage.adoc
@@ -105,7 +105,7 @@ By creating domain event subtypes we can be more semantically precise and in tur
We recommend that you define event classes at (up to) four scopes:
-* at the top "global" scope is the Apache Isis-defined `o.a.i.applib.event.ActionDomainEvent`
+* at the top "global" scope is the Apache Causeway-defined `o.a.i.applib.event.ActionDomainEvent`
* for the "module" scope, create a static class to represent the module itself, and creating nested classes within
* for each "class" scope, create a nested static event class in the domain object's class for all of the domain object's actions
* for each "action" scope, create a nested static event class for that action, inheriting from the "domain object" class.
@@ -249,10 +249,10 @@ public class ReserveStockSubscriber {
== Related Services
-The `EventBusService` is intended for fine-grained publish/subscribe for object-to-object interactions within an Apache Isis domain object model.
+The `EventBusService` is intended for fine-grained publish/subscribe for object-to-object interactions within an Apache Causeway domain object model.
The event propagation is strictly in-memory, and there are no restrictions on the object acting as the event (it need not be serializable, for example).
-There are several mechanisms to suport coarse-grained publish/subscribe for system-to-system interactions, from Apache Isis to some other system:
+There are several mechanisms to suport coarse-grained publish/subscribe for system-to-system interactions, from Apache Causeway to some other system:
* Command publishing, representing the _intention_ to invoke an action or edit a property.
+
diff --git a/antora/components/refguide-index/modules/applib/pages/index/services/grid/hooks/GridService_020-examples-and-usage.adoc b/antora/components/refguide-index/modules/applib/pages/index/services/grid/hooks/GridService_020-examples-and-usage.adoc
index 88bb8a23ab..0f5a026ee3 100644
--- a/antora/components/refguide-index/modules/applib/pages/index/services/grid/hooks/GridService_020-examples-and-usage.adoc
+++ b/antora/components/refguide-index/modules/applib/pages/index/services/grid/hooks/GridService_020-examples-and-usage.adoc
@@ -3,7 +3,7 @@
== Caching
-Once a grid has been loaded for a domain class, this is cached internally by Apache Isis' internal meta model (in the `GridFacet` facet).
+Once a grid has been loaded for a domain class, this is cached internally by Apache Causeway' internal meta model (in the `GridFacet` facet).
If running in prototype mode, any subsequent changes to the XML will be detected and the grid rebuilt.
This allows for dynamic reloading of layouts, providing a far faster feedback (eg if tweaking the UI while working with end-users).
@@ -19,7 +19,7 @@ This service delegates to:
* to xref:refguide:applib:index/services/grid/GridLoaderService.adoc[GridLoaderService] to load a pre-existing layout for the domain class, if possible
-* to xref:refguide:applib:index/services/grid/GridSystemService.adoc[GridSystemService] to normalize the grid with respect to Apache Isis' internal metamodel, in other words to ensure that all of the domain objects' properties, collections and actions are associated with regions of the grid.
+* to xref:refguide:applib:index/services/grid/GridSystemService.adoc[GridSystemService] to normalize the grid with respect to Apache Causeway' internal metamodel, in other words to ensure that all of the domain objects' properties, collections and actions are associated with regions of the grid.
diff --git a/antora/components/refguide-index/modules/applib/pages/index/services/i18n/hooks/TranslationService_010-implementation.adoc b/antora/components/refguide-index/modules/applib/pages/index/services/i18n/hooks/TranslationService_010-implementation.adoc
index bbfb9f0535..a79b261196 100644
--- a/antora/components/refguide-index/modules/applib/pages/index/services/i18n/hooks/TranslationService_010-implementation.adoc
+++ b/antora/components/refguide-index/modules/applib/pages/index/services/i18n/hooks/TranslationService_010-implementation.adoc
@@ -5,4 +5,4 @@
== Implementation
-The Apache Isis framework provides a default implementation (`o.a.i.core.runtimeservices.i18n.po.TranslationServicePo`) that uses the GNU `.pot` and `.po` files for translations.
+The Apache Causeway framework provides a default implementation (`o.a.i.core.runtimeservices.i18n.po.TranslationServicePo`) that uses the GNU `.pot` and `.po` files for translations.
diff --git a/antora/components/refguide-index/modules/applib/pages/index/services/i18n/hooks/TranslationsResolver_020-examples-and-usage.adoc b/antora/components/refguide-index/modules/applib/pages/index/services/i18n/hooks/TranslationsResolver_020-examples-and-usage.adoc
index 36a90e5b8d..b933824efa 100644
--- a/antora/components/refguide-index/modules/applib/pages/index/services/i18n/hooks/TranslationsResolver_020-examples-and-usage.adoc
+++ b/antora/components/refguide-index/modules/applib/pages/index/services/i18n/hooks/TranslationsResolver_020-examples-and-usage.adoc
@@ -4,7 +4,7 @@
== Usage Notes
-For the "big picture" and further details on Apache Isis' i18n support, see xref:userguide:btb:i18n.adoc[here].
+For the "big picture" and further details on Apache Causeway' i18n support, see xref:userguide:btb:i18n.adoc[here].
== See Also
diff --git a/antora/components/refguide-index/modules/applib/pages/index/services/jaxb/hooks/JaxbService_010-implementation.adoc b/antora/components/refguide-index/modules/applib/pages/index/services/jaxb/hooks/JaxbService_010-implementation.adoc
index 1221a38209..a065dcd445 100644
--- a/antora/components/refguide-index/modules/applib/pages/index/services/jaxb/hooks/JaxbService_010-implementation.adoc
+++ b/antora/components/refguide-index/modules/applib/pages/index/services/jaxb/hooks/JaxbService_010-implementation.adoc
@@ -5,5 +5,5 @@
== Implementation
-Apache Isis provides a default implementation of the service, `o.a.i.applib.services.jaxb.JaxbServiceDefault`.
+Apache Causeway provides a default implementation of the service, `o.a.i.applib.services.jaxb.JaxbServiceDefault`.
This automatically caches ``JAXBContext``s for each domain class as requested.
diff --git a/antora/components/refguide-index/modules/applib/pages/index/services/publishing/spi/hooks/ExecutionSubscriber_020-examples-and-usage.adoc b/antora/components/refguide-index/modules/applib/pages/index/services/publishing/spi/hooks/ExecutionSubscriber_020-examples-and-usage.adoc
index 3fa70c5ea4..719a03f954 100644
--- a/antora/components/refguide-index/modules/applib/pages/index/services/publishing/spi/hooks/ExecutionSubscriber_020-examples-and-usage.adoc
+++ b/antora/components/refguide-index/modules/applib/pages/index/services/publishing/spi/hooks/ExecutionSubscriber_020-examples-and-usage.adoc
@@ -29,7 +29,7 @@ All of these services collaborate implicitly by way of the xref:refguide:applib:
In contrast:
-* The xref:refguide:applib:index/services/eventbus/EventBusService.adoc[EventBusService] differs from the xref:refguide:applib:index/services/publishing/spi/ExecutionSubscriber.adoc[ExecutionSubscriber] in that the former is intended for fine-grained publish/subscribe for object-to-object interactions _within_ an Apache Isis domain object model.
+* The xref:refguide:applib:index/services/eventbus/EventBusService.adoc[EventBusService] differs from the xref:refguide:applib:index/services/publishing/spi/ExecutionSubscriber.adoc[ExecutionSubscriber] in that the former is intended for fine-grained publish/subscribe for object-to-object interactions _within_ an Apache Causeway domain object model.
+
The event propagation is strictly in-memory, and there are no restrictions on the object acting as the event; it need not be serializable, for example.
diff --git a/antora/components/refguide-index/modules/applib/pages/index/services/swagger/hooks/SwaggerService_020-examples-and-usage.adoc b/antora/components/refguide-index/modules/applib/pages/index/services/swagger/hooks/SwaggerService_020-examples-and-usage.adoc
index 84341fa7ee..f660dabfc7 100644
--- a/antora/components/refguide-index/modules/applib/pages/index/services/swagger/hooks/SwaggerService_020-examples-and-usage.adoc
+++ b/antora/components/refguide-index/modules/applib/pages/index/services/swagger/hooks/SwaggerService_020-examples-and-usage.adoc
@@ -6,7 +6,7 @@
Not all of the REST API exposed by the xref:vro:ROOT:about.adoc[REST API (Restful Objects viewer)] is included in the Swagger schema definition files; the emphasis is those REST resources that are used to develop custom apps: domain objects, domain object collections and action invocations.
-When combined with Apache Isis' own xref:vro:ROOT:content-negotiation/apache-causeway-v2-profile.adoc[simplified representations], these are pretty much all that is needed for this use case.
+When combined with Apache Causeway' own xref:vro:ROOT:content-negotiation/apache-causeway-v2-profile.adoc[simplified representations], these are pretty much all that is needed for this use case.
The service is_not_ (currently) used by the framework itself; it is provided as a convenience for developers to build REST applications.
diff --git a/antora/components/refguide-index/modules/applib/pages/index/services/userreg/hooks/EmailNotificationService_020-examples-and-usage.adoc b/antora/components/refguide-index/modules/applib/pages/index/services/userreg/hooks/EmailNotificationService_020-examples-and-usage.adoc
index fbd4c3aedb..683d8bc1c2 100644
--- a/antora/components/refguide-index/modules/applib/pages/index/services/userreg/hooks/EmailNotificationService_020-examples-and-usage.adoc
+++ b/antora/components/refguide-index/modules/applib/pages/index/services/userreg/hooks/EmailNotificationService_020-examples-and-usage.adoc
@@ -5,11 +5,11 @@
== Alternatives
The text of these email templates are hard-coded as resources, in other words baked into the core jar files.
-If you need to use different text then you can of course always write and register your own implementation to be used instead of Apache Isis' default.
+If you need to use different text then you can of course always write and register your own implementation to be used instead of Apache Causeway' default.
If you have configured an alternative email service implementation, it should process the message body as HTML.
-Be aware also that there may not be any Apache Isis session running when this service is called.
+Be aware also that there may not be any Apache Causeway session running when this service is called.
If necessary, one can be created on the fly using the `InteractionService#runAuthenticated(...)` (not API).
.
@@ -32,7 +32,7 @@ The default implementation of this service uses the xref:refguide:applib:index/s
The default implementation of this service uses xref:refguide:applib:index/services/email/EmailService.adoc[EmailService], which must have been configured/initialized correctly.
-This service is used by (Apache Isis' default implementation of) xref:refguide:applib:index/services/userreg/UserRegistrationService.adoc[UserRegistrationService].
+This service is used by (Apache Causeway' default implementation of) xref:refguide:applib:index/services/userreg/UserRegistrationService.adoc[UserRegistrationService].
== Related Event Classes
diff --git a/antora/components/refguide-index/modules/applib/pages/index/services/wrapper/hooks/WrapperFactory_010-implementation.adoc b/antora/components/refguide-index/modules/applib/pages/index/services/wrapper/hooks/WrapperFactory_010-implementation.adoc
index 41a77d2a8d..424df615d5 100644
--- a/antora/components/refguide-index/modules/applib/pages/index/services/wrapper/hooks/WrapperFactory_010-implementation.adoc
+++ b/antora/components/refguide-index/modules/applib/pages/index/services/wrapper/hooks/WrapperFactory_010-implementation.adoc
@@ -6,4 +6,4 @@
== Implementation
-The service works by returning a "wrapper" around a supplied domain object (using link:https://bytebuddy.net/[byte buddy]), and it is this wrapper that ensures that the hide/disable/validate rules implies by the Apache Isis programming model are enforced.
+The service works by returning a "wrapper" around a supplied domain object (using link:https://bytebuddy.net/[byte buddy]), and it is this wrapper that ensures that the hide/disable/validate rules implies by the Apache Causeway programming model are enforced.
diff --git a/antora/components/refguide-index/modules/persistence/pages/index/jdo/applib/services/hooks/JdoSupportService_010-examples-and-usage.adoc b/antora/components/refguide-index/modules/persistence/pages/index/jdo/applib/services/hooks/JdoSupportService_010-examples-and-usage.adoc
index 155a20f28a..a9af56c9e9 100644
--- a/antora/components/refguide-index/modules/persistence/pages/index/jdo/applib/services/hooks/JdoSupportService_010-examples-and-usage.adoc
+++ b/antora/components/refguide-index/modules/persistence/pages/index/jdo/applib/services/hooks/JdoSupportService_010-examples-and-usage.adoc
@@ -162,8 +162,8 @@ public class TearDownAll extends FixtureScriptAbstract {
[NOTE]
====
-It can occasionally be the case that Apache Isis' internal adapter for the domain object is still in memory.
-JDO/DataNucleus seems to bump up the version of the object prior to its deletion, which under normal circumstances would cause Apache Isis to throw a concurrency exception.
+It can occasionally be the case that Apache Causeway' internal adapter for the domain object is still in memory.
+JDO/DataNucleus seems to bump up the version of the object prior to its deletion, which under normal circumstances would cause Apache Causeway to throw a concurrency exception.
Therefore to prevent this from happening (ie to _force_ the deletion of all instances), concurrency checking is temporarily disabled while this method is performed.
====
diff --git a/antora/components/refguide-index/modules/viewer/pages/index/restfulobjects/rendering/service/conneg/hooks/ContentNegotiationServiceForRestfulObjectsV1_0_usage-notes.adoc b/antora/components/refguide-index/modules/viewer/pages/index/restfulobjects/rendering/service/conneg/hooks/ContentNegotiationServiceForRestfulObjectsV1_0_usage-notes.adoc
index 3c018429e4..4ad34cd629 100644
--- a/antora/components/refguide-index/modules/viewer/pages/index/restfulobjects/rendering/service/conneg/hooks/ContentNegotiationServiceForRestfulObjectsV1_0_usage-notes.adoc
+++ b/antora/components/refguide-index/modules/viewer/pages/index/restfulobjects/rendering/service/conneg/hooks/ContentNegotiationServiceForRestfulObjectsV1_0_usage-notes.adoc
@@ -4,7 +4,7 @@
== Extensions
-One extension (specific to Apache Isis, not part of the RO spec) is that actions can also be invoked with an HTTP `Accept` header of the form:
+One extension (specific to Apache Causeway, not part of the RO spec) is that actions can also be invoked with an HTTP `Accept` header of the form:
application/json;profile=urn:org.restfulobjects:repr-types/object
diff --git a/antora/components/refguide/modules/applib-ant/pages/Column.adoc b/antora/components/refguide/modules/applib-ant/pages/Column.adoc
index 8ff97a34fa..65602681f7 100644
--- a/antora/components/refguide/modules/applib-ant/pages/Column.adoc
+++ b/antora/components/refguide/modules/applib-ant/pages/Column.adoc
@@ -6,18 +6,18 @@
The JDO `@javax.jdo.annotation.Column` provides metadata describing how JDO/DataNucleus should persist the property to a database RDBMS table column (or equivalent concept for other persistence stores).
-Apache Isis also parses and interprets this annotation in order to build up aspects of its metamodel.
+Apache Causeway also parses and interprets this annotation in order to build up aspects of its metamodel.
[NOTE]
====
-Apache Isis parses the `@Column` annotation from the Java source code; it does not query the JDO metamodel.
+Apache Causeway parses the `@Column` annotation from the Java source code; it does not query the JDO metamodel.
This means that it the `@Column` annotation must be used rather than the equivalent `<column>` link:http://www.datanucleus.org/products/accessplatform_4_0/jdo/orm/schema_mapping.html[XML metadata].
-Moreover, while JDO/DataNucleus will recognize annotations on either the field or the getter method, Apache Isis (currently) only inspects the getter method.
+Moreover, while JDO/DataNucleus will recognize annotations on either the field or the getter method, Apache Causeway (currently) only inspects the getter method.
Therefore ensure that the annotation is placed there.
====
-This section identifies which attributes of `@Column` are recognized and used by Apache Isis.
+This section identifies which attributes of `@Column` are recognized and used by Apache Causeway.
[#nullability]
== Nullability
@@ -34,11 +34,11 @@ public class Customer {
public void setMiddleInitial(String middleInitial) { /* ... */ }
----
-Isis also provides xref:refguide:applib:index/annotation/Property.adoc#optionality[@Property#optionality] attribute.
-If both are specified, Apache Isis will check when it initializes for any contradictions, and will fail-fast with an appropriate error message in the log if there are.
+Causeway also provides xref:refguide:applib:index/annotation/Property.adoc#optionality[@Property#optionality] attribute.
+If both are specified, Apache Causeway will check when it initializes for any contradictions, and will fail-fast with an appropriate error message in the log if there are.
-You should also be aware that in the lack of either the `@Column#allowsNull` or the `@Property#optionality` attributes, that the JDO and Apache Isis defaults differ.
-Apache Isis rule is straight-forward: properties are assumed to be required.
+You should also be aware that in the lack of either the `@Column#allowsNull` or the `@Property#optionality` attributes, that the JDO and Apache Causeway defaults differ.
+Apache Causeway rule is straight-forward: properties are assumed to be required.
JDO on the other hand specifies that only primitive types are mandatory; everything else is assumed to be optional.
Therefore a lack of either annotation can also trigger the fail-fast validation check.
@@ -66,8 +66,8 @@ public class Customer {
public void setLastName(String lastName) { /* ... */ }
----
-Apache Isis also provides xref:refguide:applib:index/annotation/Property.adoc#maxLength[@Property#maxLength] attribute.
-If both are specified, Apache Isis will check when it initializes for any contradictions, and will fail-fast with an appropriate error message in the log if there are.
+Apache Causeway also provides xref:refguide:applib:index/annotation/Property.adoc#maxLength[@Property#maxLength] attribute.
+If both are specified, Apache Causeway will check when it initializes for any contradictions, and will fail-fast with an appropriate error message in the log if there are.
[#lengthscale-for-bigdecimals]
== Length/scale for ``BigDecimal``s
@@ -87,13 +87,13 @@ public class Customer {
For ``BigDecimal``s it is also possible to specify the xref:refguide:applib-ant:Digits.adoc[@Digits] annotation, whose form is `@Digits(integer, fraction)`.
There is a subtle difference here: while `@Column#scale()` corresponds to `@Digits#fraction()`, the value of `@Column#length()` (ie the precision) is actually the __sum__ of the `@Digits`' `integer()` and `fraction()` parts.
-If both are specified, Apache Isis will check when it initializes for any contradictions, and will fail-fast with an appropriate error message in the log if there are.
+If both are specified, Apache Causeway will check when it initializes for any contradictions, and will fail-fast with an appropriate error message in the log if there are.
[[rg-ant-hints-and-tips]]
== Hints and Tips
This seems to be a good place to describe some additional common mappings that use `@Column`.
-Unlike the sections above, the attributes specified in these hints and tips aren't actually part of Apache Isis metamodel.
+Unlike the sections above, the attributes specified in these hints and tips aren't actually part of Apache Causeway metamodel.
=== Mapping foreign keys
@@ -118,7 +118,7 @@ public class PartyRelationship {
=== Mapping ``Blob``s and ``Clob``s
-Isis provides custom value types for xref:refguide:applib:index/value/Blob.adoc[Blob]s and xref:refguide:applib:index/value/Clob.adoc[Clob]s.
+Causeway provides custom value types for xref:refguide:applib:index/value/Blob.adoc[Blob]s and xref:refguide:applib:index/value/Clob.adoc[Clob]s.
These value types have multiple internal fields, meaning that they corresponding to multiple columns in the database.
Mapping this correctly requires using `@Column` within JDO's `@Persistent` annotation.
diff --git a/antora/components/refguide/modules/applib-ant/pages/Digits.adoc b/antora/components/refguide/modules/applib-ant/pages/Digits.adoc
index b9b51d11b0..7f2bb50fe1 100644
--- a/antora/components/refguide/modules/applib-ant/pages/Digits.adoc
+++ b/antora/components/refguide/modules/applib-ant/pages/Digits.adoc
@@ -5,7 +5,7 @@
-The `@javax.validation.constraints.Digits` annotation is recognized by Apache Isis as a means to specify the precision for properties and action parameters of type `java.math.BigDecimal`.
+The `@javax.validation.constraints.Digits` annotation is recognized by Apache Causeway as a means to specify the precision for properties and action parameters of type `java.math.BigDecimal`.
For example:
diff --git a/antora/components/refguide/modules/applib-ant/pages/Discriminator.adoc b/antora/components/refguide/modules/applib-ant/pages/Discriminator.adoc
index bbe0b05453..31d43b439d 100644
--- a/antora/components/refguide/modules/applib-ant/pages/Discriminator.adoc
+++ b/antora/components/refguide/modules/applib-ant/pages/Discriminator.adoc
@@ -8,14 +8,14 @@
The `@javax.jdo.annotation.Discriminator` is used by JDO/DataNucleus to specify how to discriminate between subclasses of an inheritance hierarchy.
It is valid to add a `@Discriminator` for any class, even those not part of an explicitly mapped inheritance hierarchy.
-Apache Isis also checks for this annotation, and if present will use the `@Discriminator#value()` as the object type, a unique alias for the object's class name.
+Apache Causeway also checks for this annotation, and if present will use the `@Discriminator#value()` as the object type, a unique alias for the object's class name.
[NOTE]
====
-Isis parses the `@Discriminator` annotation from the Java source code; it does not query the JDO metamodel.
+Causeway parses the `@Discriminator` annotation from the Java source code; it does not query the JDO metamodel.
This means that it the `@Discriminator` annotation must be used rather than the equivalent `<discriminator>` link:http://www.datanucleus.org/products/accessplatform_4_0/jdo/orm/inheritance.html[XML metadata].
-Moreover, while JDO/DataNucleus will recognize annotations on either the field or the getter method, Apache Isis (currently) only inspects the getter method.
+Moreover, while JDO/DataNucleus will recognize annotations on either the field or the getter method, Apache Causeway (currently) only inspects the getter method.
Therefore ensure that the annotation is placed there.
====
diff --git a/antora/components/refguide/modules/applib-ant/pages/NotPersistent.adoc b/antora/components/refguide/modules/applib-ant/pages/NotPersistent.adoc
index ec18092ea9..cea9e5d8e9 100644
--- a/antora/components/refguide/modules/applib-ant/pages/NotPersistent.adoc
+++ b/antora/components/refguide/modules/applib-ant/pages/NotPersistent.adoc
@@ -6,14 +6,14 @@
The `@javax.jdo.annotation.NotPersistent` annotation is used by JDO/DataNucleus to indicate that a property should not be persisted to the database.
-Apache Isis also uses this annotation, though (currently) only in the very minimal way to suppress checking of inconsistent metadata between JDO and Isis annotations (eg `@Column#allowsNull()` vs `@Property#optionality()`, or `@Column#length()` and `@Property#maxLength()`).
+Apache Causeway also uses this annotation, though (currently) only in the very minimal way to suppress checking of inconsistent metadata between JDO and Causeway annotations (eg `@Column#allowsNull()` vs `@Property#optionality()`, or `@Column#length()` and `@Property#maxLength()`).
[NOTE]
====
The framework parses the `@NotPersistent` annotation from the Java source code; it does not query the JDO metamodel.
This means that it the `@NotPersistent` annotation must be used rather than the equivalent `<field>` link:http://www.datanucleus.org/products/accessplatform_4_0/jdo/fields_properties.html[XML metadata].
-Moreover, while JDO/DataNucleus will recognize annotations on either the field or the getter method, Apache Isis (currently) only inspects the getter method.
+Moreover, while JDO/DataNucleus will recognize annotations on either the field or the getter method, Apache Causeway (currently) only inspects the getter method.
Therefore ensure that the annotation is placed there.
====
diff --git a/antora/components/refguide/modules/applib-ant/pages/Nullable.adoc b/antora/components/refguide/modules/applib-ant/pages/Nullable.adoc
index f4b25f71d9..746a39b649 100644
--- a/antora/components/refguide/modules/applib-ant/pages/Nullable.adoc
+++ b/antora/components/refguide/modules/applib-ant/pages/Nullable.adoc
@@ -4,8 +4,8 @@
: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 [...]
-Apache Isis' defaults for properties and parameters is that they are mandatory unless otherwise stated.
-The `@javax.annotation.Nullable` annotation is recognized by Apache Isis for both properties and parameters as means to indicate that the property/parameter is not mandatory.
+Apache Causeway' defaults for properties and parameters is that they are mandatory unless otherwise stated.
+The `@javax.annotation.Nullable` annotation is recognized by Apache Causeway for both properties and parameters as means to indicate that the property/parameter is not mandatory.
For example:
@@ -30,7 +30,7 @@ public Customer updateName(@javax.annotation.Nullable final String name) {
}
----
-Apache Isis does provide several other ways to specify optionality: using the
+Apache Causeway does provide several other ways to specify optionality: using the
xref:refguide:applib:index/annotation/Property.adoc#optionality[@Property#optionality()] /
xref:refguide:applib:index/annotation/Parameter.adoc#optionality[@Parameter#optionality()] annotation.
For properties, the optionality can also be inferred from the xref:refguide:applib-ant:Column.adoc#nullability[@Column#allowsNull()] attribute.
@@ -38,7 +38,7 @@ For properties, the optionality can also be inferred from the xref:refguide:appl
[TIP]
====
See the
-xref:refguide:applib:index/annotation/Property.adoc#optionality[@Property#optionality()] documentation for a much fuller discussion on the relationship between using the Apache Isis annotations vs
+xref:refguide:applib:index/annotation/Property.adoc#optionality[@Property#optionality()] documentation for a much fuller discussion on the relationship between using the Apache Causeway annotations vs
xref:refguide:applib-ant:Column.adoc#nullability[@Column#allowsNull()].
====
diff --git a/antora/components/refguide/modules/applib-ant/pages/Pattern.adoc b/antora/components/refguide/modules/applib-ant/pages/Pattern.adoc
index 9582bc8d81..47d61e2b18 100644
--- a/antora/components/refguide/modules/applib-ant/pages/Pattern.adoc
+++ b/antora/components/refguide/modules/applib-ant/pages/Pattern.adoc
@@ -5,7 +5,7 @@
-The `@javax.validation.constraints.Pattern` annotation is recognized by Apache Isis as a means to specify a regular expression constraint for properties and action parameters of type `java.lang.String`.
+The `@javax.validation.constraints.Pattern` annotation is recognized by Apache Causeway as a means to specify a regular expression constraint for properties and action parameters of type `java.lang.String`.
For example, here's the annotation being used on an action parameter:
diff --git a/antora/components/refguide/modules/applib-ant/pages/PersistenceCapable.adoc b/antora/components/refguide/modules/applib-ant/pages/PersistenceCapable.adoc
index 3deb122dfb..554355164d 100644
--- a/antora/components/refguide/modules/applib-ant/pages/PersistenceCapable.adoc
+++ b/antora/components/refguide/modules/applib-ant/pages/PersistenceCapable.adoc
@@ -7,14 +7,14 @@
The `@javax.jdo.annotation.PersistenceCapable` is used by JDO/DataNucleus to indicate that a class is a domain entity to be persisted to the database.
-Apache Isis also checks for this annotation, and if the `@PersistenceCapable#schema` attribute is present will use it to form the object type.
+Apache Causeway also checks for this annotation, and if the `@PersistenceCapable#schema` attribute is present will use it to form the object type.
[NOTE]
====
-Isis parses the `@PersistenceCapable` annotation from the Java source code; it does not query the JDO metamodel.
+Causeway parses the `@PersistenceCapable` annotation from the Java source code; it does not query the JDO metamodel.
This means that it the `@PersistenceCapable` annotation must be used rather than the equivalent `<class>` link:http://www.datanucleus.org/products/accessplatform_4_0/jdo/class_mapping.html[XML metadata].
-Moreover, while JDO/DataNucleus will recognize annotations on either the field or the getter method, Apache Isis (currently) only inspects the getter method.
+Moreover, while JDO/DataNucleus will recognize annotations on either the field or the getter method, Apache Causeway (currently) only inspects the getter method.
Therefore ensure that the annotation is placed there.
====
@@ -29,7 +29,7 @@ This can appear in several contexts, including:
* in XML snapshots generated by the xref:refguide:applib:index/services/xmlsnapshot/XmlSnapshotService.adoc[XmlSnapshotService]
-The actual format of the object type used by Apache Isis for the concatenation of `schema()` and `@PersistenceCapable#table()`.
+The actual format of the object type used by Apache Causeway for the concatenation of `schema()` and `@PersistenceCapable#table()`.
If the `table()` is not present, then the class' simple name is used instead.
== Examples
diff --git a/antora/components/refguide/modules/applib-ant/pages/PrimaryKey.adoc b/antora/components/refguide/modules/applib-ant/pages/PrimaryKey.adoc
index 9f0550c1f4..5f0c991c69 100644
--- a/antora/components/refguide/modules/applib-ant/pages/PrimaryKey.adoc
+++ b/antora/components/refguide/modules/applib-ant/pages/PrimaryKey.adoc
@@ -7,14 +7,14 @@
The `@javax.jdo.annotation.PrimaryKey` annotation is used by JDO/DataNucleus to indicate that a property is used as the primary key for an entity with application-managed identity.
-Apache Isis also uses this annotation in a very minimal way: to ensure that the framework's own logic to initialize newly instantiated objects (eg using xref:refguide:applib:index/services/factory/FactoryService.adoc[FactoryService#create(...)] does not touch the primary key, and also to ensure that the primary key property is always disabled (read-only).
+Apache Causeway also uses this annotation in a very minimal way: to ensure that the framework's own logic to initialize newly instantiated objects (eg using xref:refguide:applib:index/services/factory/FactoryService.adoc[FactoryService#create(...)] does not touch the primary key, and also to ensure that the primary key property is always disabled (read-only).
[NOTE]
====
-Apache Isis parses the `@NotPersistent` annotation from the Java source code; it does not query the JDO metamodel.
+Apache Causeway parses the `@NotPersistent` annotation from the Java source code; it does not query the JDO metamodel.
This means that it the `@NotPersistent` annotation must be used rather than the equivalent `<field>` link:http://www.datanucleus.org/products/accessplatform_4_0/jdo/application_identity.html[XML metadata].
-Moreover, while JDO/DataNucleus will recognize annotations on either the field or the getter method, Apache Isis (currently) only inspects the getter method.
+Moreover, while JDO/DataNucleus will recognize annotations on either the field or the getter method, Apache Causeway (currently) only inspects the getter method.
Therefore ensure that the annotation is placed there.
====
diff --git a/antora/components/refguide/modules/applib-ant/pages/XmlRootElement.adoc b/antora/components/refguide/modules/applib-ant/pages/XmlRootElement.adoc
index 1736bf737b..9b916eef3d 100644
--- a/antora/components/refguide/modules/applib-ant/pages/XmlRootElement.adoc
+++ b/antora/components/refguide/modules/applib-ant/pages/XmlRootElement.adoc
@@ -9,7 +9,7 @@ The `@XmlRootElement` annotation provides an alternative way to define a xref:us
A view model is a non-persisted domain object whose state is converted to/from a string memento.
In the case of a JAXB-annotated object this memento is its XML representation.
JAXB generally requires that the root element of the XML representation is annotated with `@XmlRootElement`.
-Apache Isis makes this a mandatory requirement.
+Apache Causeway makes this a mandatory requirement.
In comparison to using either the xref:refguide:applib:index/ViewModel.adoc[ViewModel] interface or the
xref:refguide:applib:index/annotation/DomainObject.adoc[@DomainObject(nature=VIEW_MODEL)] annotation,
@@ -26,7 +26,7 @@ In contrast, if the `@DomainObject(nature=VIEW_MODEL)` annotation is used then o
If using `ViewModel` interface then arbitrary state (including that of collections), however the programmer must write all the code by hand
The main disadvantages of using JAXB-annotated view models is that any referenced persistent entity must be annotated with the xref:refguide:applib-ant:XmlJavaTypeAdapter.adoc[@XmlJavaTypeAdapter], using the framework-provided `PersistentEntityAdapter`.
-This adapter converts any references to such domain entities using the `oidDto` complex type (as defined by the Apache Isis xref:refguide:schema:common.adoc[common schema]): the object's type and its identifier.
+This adapter converts any references to such domain entities using the `oidDto` complex type (as defined by the Apache Causeway xref:refguide:schema:common.adoc[common schema]): the object's type and its identifier.
[TIP]
====
diff --git a/antora/components/refguide/modules/applib-ant/pages/about.adoc b/antora/components/refguide/modules/applib-ant/pages/about.adoc
index f9939c1cf5..19a466c38f 100644
--- a/antora/components/refguide/modules/applib-ant/pages/about.adoc
+++ b/antora/components/refguide/modules/applib-ant/pages/about.adoc
@@ -4,12 +4,12 @@
:page-partial:
-This guide describes the various annotations used by Apache Isis to provide additional metadata about the domain objects.
+This guide describes the various annotations used by Apache Causeway to provide additional metadata about the domain objects.
Most of these are defined by the framework itself, but some are from other libraries.
It also identifies a number of annotations that are now deprecated, and indicates their replacement.
-The annotations supported by Apache Isis break out into five categories.
+The annotations supported by Apache Causeway break out into five categories.
include::about/main.adoc[leveloffset=+1]
include::about/other.adoc[leveloffset=+1]
@@ -21,7 +21,7 @@ include::about/jee.adoc[leveloffset=+1]
== Examples
-To give just a few examples of annotations supported by Apache Isis:
+To give just a few examples of annotations supported by Apache Causeway:
* if a property is read-only, then this can be annotated with `@Property(editing=EditingDISABLED)`.
* if a class has a small fixed set of instances (eg a picklist), then it can be annotated using `@DomainObject(bounded=true)`
diff --git a/antora/components/refguide/modules/applib-ant/pages/about/jdo.adoc b/antora/components/refguide/modules/applib-ant/pages/about/jdo.adoc
index d596d59445..cc06ef95b2 100644
--- a/antora/components/refguide/modules/applib-ant/pages/about/jdo.adoc
+++ b/antora/components/refguide/modules/applib-ant/pages/about/jdo.adoc
@@ -4,7 +4,7 @@
:page-partial:
-The table below lists the xref:pjdo:ROOT:about.adoc[JDO/DataNucleus] annotations currently recognized by Apache Isis.
+The table below lists the xref:pjdo:ROOT:about.adoc[JDO/DataNucleus] annotations currently recognized by Apache Causeway.
.JDO Annotations
@@ -35,7 +35,7 @@ Note that the discriminator overrides the object type that may otherwise be infe
|xref:refguide:applib-ant:NotPersistent.adoc[@javax.jdo.annotations. +
NotPersistent]
-|Used to determine whether to enforce or skip some metamodel validation for `@Column` versus equivalent Isis annotations.
+|Used to determine whether to enforce or skip some metamodel validation for `@Column` versus equivalent Causeway annotations.
|Domain / persistence
|Property
@@ -44,7 +44,7 @@ NotPersistent]
|xref:refguide:applib-ant:PersistenceCapable.adoc[@javax.jdo.annotations. +
PersistenceCapable]
-|Used to build Apache Isis' own internal identifier for objects. +
+|Used to build Apache Causeway' own internal identifier for objects. +
If the `schema` attribute is specified (and if xref:refguide:applib-ant:Discriminator.adoc[@Discriminator] __hasn't__ been specified), is also used to derive the object type, as used in `Bookmark`s, URLs for xref:vro:ROOT:about.adoc[RestfulObjects viewer] and elsewhere.
@@ -54,7 +54,7 @@ If the `schema` attribute is specified (and if xref:refguide:applib-ant:Discrimi
|xref:refguide:applib-ant:PrimaryKey.adoc[@javax.jdo.annotations. +
PrimaryKey]
-|Used to ensure Apache Isis does not overwrite application-defined primary keys, and to ensure is read-only in the UI.
+|Used to ensure Apache Causeway does not overwrite application-defined primary keys, and to ensure is read-only in the UI.
|Domain / persistence
|Property
@@ -65,9 +65,9 @@ PrimaryKey]
-Isis also parses the following JDO annotations, but the metadata is currently unused.
+Causeway also parses the following JDO annotations, but the metadata is currently unused.
-.JDO Annotations (unused within Apache Isis)
+.JDO Annotations (unused within Apache Causeway)
[cols="2,4a,1,1", options="header"]
|===
|Annotation
diff --git a/antora/components/refguide/modules/applib-ant/pages/about/jee.adoc b/antora/components/refguide/modules/applib-ant/pages/about/jee.adoc
index 2330412431..9ab57f0e08 100644
--- a/antora/components/refguide/modules/applib-ant/pages/about/jee.adoc
+++ b/antora/components/refguide/modules/applib-ant/pages/about/jee.adoc
@@ -4,9 +4,9 @@
:page-partial:
-While Apache Isis does define many of its own annotations, the policy is to reuse standard Java/JEE annotations wherever they exist or are added to the Java platform.
+While Apache Causeway does define many of its own annotations, the policy is to reuse standard Java/JEE annotations wherever they exist or are added to the Java platform.
-The table below lists the JEE annotations currently recognized. Expect to see more added in future releases of Apache Isis.
+The table below lists the JEE annotations currently recognized. Expect to see more added in future releases of Apache Causeway.
.Java EE Annotations
diff --git a/antora/components/refguide/modules/applib-ant/pages/about/jpa.adoc b/antora/components/refguide/modules/applib-ant/pages/about/jpa.adoc
index ff812d4dcb..a441b86776 100644
--- a/antora/components/refguide/modules/applib-ant/pages/about/jpa.adoc
+++ b/antora/components/refguide/modules/applib-ant/pages/about/jpa.adoc
@@ -5,5 +5,5 @@
TODO: v2 - JPA is now also supported as an ORM.
-(As with JDO), some of JPA's annotations are recognised by Apache Isis.
+(As with JDO), some of JPA's annotations are recognised by Apache Causeway.
diff --git a/antora/components/refguide/modules/applib-ant/pages/about/main.adoc b/antora/components/refguide/modules/applib-ant/pages/about/main.adoc
index 0eb4311d0b..fde58f2243 100644
--- a/antora/components/refguide/modules/applib-ant/pages/about/main.adoc
+++ b/antora/components/refguide/modules/applib-ant/pages/about/main.adoc
@@ -4,7 +4,7 @@
:page-partial:
-In Apache Isis every domain object is either a domain entity, a view model or a domain service. And each of these are made up of properties, collections and actions (domain services only have actions).
+In Apache Causeway every domain object is either a domain entity, a view model or a domain service. And each of these are made up of properties, collections and actions (domain services only have actions).
For each of these domain types and members there are two annotations. One covers the semantics intrinsic to the domain (eg whether an action parameter is optional or not), then other (suffix `...Layout`) captures semantics relating to the UI/presentation layer.
@@ -14,7 +14,7 @@ Most UI semantics can also be specified using xref:userguide:fun:ui.adoc#object-
====
-The table below summarizes these most commonly used annotations in Apache Isis.
+The table below summarizes these most commonly used annotations in Apache Causeway.
.Core annotations for domain objects, services and members
diff --git a/antora/components/refguide/modules/applib-ant/pages/about/other.adoc b/antora/components/refguide/modules/applib-ant/pages/about/other.adoc
index 08666bb345..958f196003 100644
--- a/antora/components/refguide/modules/applib-ant/pages/about/other.adoc
+++ b/antora/components/refguide/modules/applib-ant/pages/about/other.adoc
@@ -1,12 +1,12 @@
-= Other Apache Isis Annotations
+= Other Apache Causeway Annotations
: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 [...]
:page-partial:
-These annotations are also commonly used, but relate _not_ to objects or object members but instead to other aspects of the Apache Isis metamodel.
+These annotations are also commonly used, but relate _not_ to objects or object members but instead to other aspects of the Apache Causeway metamodel.
-.Other Isis Annotations
+.Other Causeway Annotations
[cols="2,4a,1", options="header"]
|===
|Annotation
@@ -22,7 +22,7 @@ These annotations are also commonly used, but relate _not_ to objects or object
|UI
|xref:refguide:applib:index/annotation/Programmatic.adoc[@Programmatic]
-|Ignore a public method, excluded from the Apache Isis metamodel.
+|Ignore a public method, excluded from the Apache Causeway metamodel.
|Domain
|xref:refguide:applib:index/annotation/Title.adoc[@Title]
diff --git a/antora/components/refguide/modules/applib-ant/pages/about/partial.adoc b/antora/components/refguide/modules/applib-ant/pages/about/partial.adoc
index 87fc8f47d8..c77a962c9e 100644
--- a/antora/components/refguide/modules/applib-ant/pages/about/partial.adoc
+++ b/antora/components/refguide/modules/applib-ant/pages/about/partial.adoc
@@ -5,7 +5,7 @@
:page-partial:
-These annotations have only incomplete/partial support, primarily relating to the management of value types. We recommend that you do not use them for now. Future versions of Apache Isis may either formally deprecate/retire them, or we may go the other way and properly support them. This will depend in part on the interactions between the Apache Isis runtime, its two viewer implementations, and DataNucleus persistence.
+These annotations have only incomplete/partial support, primarily relating to the management of value types. We recommend that you do not use them for now. Future versions of Apache Causeway may either formally deprecate/retire them, or we may go the other way and properly support them. This will depend in part on the interactions between the Apache Causeway runtime, its two viewer implementations, and DataNucleus persistence.
.Annotations with incomplete/partial support
diff --git a/antora/components/refguide/modules/applib-classes/pages/layout/object-layout.adoc b/antora/components/refguide/modules/applib-classes/pages/layout/object-layout.adoc
index f6863d9368..f275caaad5 100644
--- a/antora/components/refguide/modules/applib-classes/pages/layout/object-layout.adoc
+++ b/antora/components/refguide/modules/applib-classes/pages/layout/object-layout.adoc
@@ -62,10 +62,10 @@ Thus, a column with a span of 12 is the full width, one with a span of 6 is half
When specifying the span of a column, Bootstrap also allows a size to be specified (`XS`, `SM`, `MD`, `LG`).
The size determines the rules for responsive design.
-Apache Isis defaults to `MD` but this can be overridden.
+Apache Causeway defaults to `MD` but this can be overridden.
It is also possible to specify multiple size/spans for a given column.
-The grid classes provided by Apache Isis reside in the `org.apache.causeway.applib.layout.grid.bootstrap3` package, and consist of:
+The grid classes provided by Apache Causeway reside in the `org.apache.causeway.applib.layout.grid.bootstrap3` package, and consist of:
* `BS3Grid` +
+
diff --git a/antora/components/refguide/modules/applib-classes/pages/spec.adoc b/antora/components/refguide/modules/applib-classes/pages/spec.adoc
index 761eb07747..e361d86666 100644
--- a/antora/components/refguide/modules/applib-classes/pages/spec.adoc
+++ b/antora/components/refguide/modules/applib-classes/pages/spec.adoc
@@ -7,7 +7,7 @@
The interfaces and classes listed in this chapter provide support for the `Specification` pattern, as described in Eric Evans' book _Domain Driven Design_, p224.
-Apache Isis will automatically apply such specifications as validation rules on properties (as per xref:refguide:applib:index/annotation/Property.adoc#mustSatisfy[@Property#mustSatisfy()]) and on action parameters (as per xref:refguide:applib:index/annotation/Parameter.adoc#mustSatisfy[@Parameter#mustSatisfy()]).
+Apache Causeway will automatically apply such specifications as validation rules on properties (as per xref:refguide:applib:index/annotation/Property.adoc#mustSatisfy[@Property#mustSatisfy()]) and on action parameters (as per xref:refguide:applib:index/annotation/Parameter.adoc#mustSatisfy[@Parameter#mustSatisfy()]).
[#specification]
== `Specification`
diff --git a/antora/components/refguide/modules/applib-classes/pages/value-types.adoc b/antora/components/refguide/modules/applib-classes/pages/value-types.adoc
index 7a0f078e67..2039158150 100644
--- a/antora/components/refguide/modules/applib-classes/pages/value-types.adoc
+++ b/antora/components/refguide/modules/applib-classes/pages/value-types.adoc
@@ -7,7 +7,7 @@
== Built-in
-Apache Isis can render and persist all of the JDK primitives and wrapper classes, and a number of other JDK (7.x) classes that represent value types.
+Apache Causeway can render and persist all of the JDK primitives and wrapper classes, and a number of other JDK (7.x) classes that represent value types.
It also supports some of the link:http://www.joda.org/joda-time/[Joda-Time] datatypes, and a number of value types that are shipped by the framework itself.
diff --git a/antora/components/refguide/modules/applib-methods/pages/about.adoc b/antora/components/refguide/modules/applib-methods/pages/about.adoc
index b9841e8983..2a50d1f5af 100644
--- a/antora/components/refguide/modules/applib-methods/pages/about.adoc
+++ b/antora/components/refguide/modules/applib-methods/pages/about.adoc
@@ -4,7 +4,7 @@
-The Apache Isis metamodel is built up from declaratively (ie, xref:refguide:applib-ant:about.adoc[annotations]) and imperatively, from "supporting" methods and other reserved methods.
+The Apache Causeway metamodel is built up from declaratively (ie, xref:refguide:applib-ant:about.adoc[annotations]) and imperatively, from "supporting" methods and other reserved methods.
This chapter documents the supporting methods and the reserved methods.
It also documents the reserved methods that act as callback hooks into the persistence lifecycle of domain entities.
diff --git a/antora/components/refguide/modules/applib-methods/pages/lifecycle.adoc b/antora/components/refguide/modules/applib-methods/pages/lifecycle.adoc
index cd015fe47e..088786c11b 100644
--- a/antora/components/refguide/modules/applib-methods/pages/lifecycle.adoc
+++ b/antora/components/refguide/modules/applib-methods/pages/lifecycle.adoc
@@ -7,7 +7,7 @@
The lifecycle callback methods notify a domain entity about its interaction within the persistence lifecycle.
For example, the entity is notified immediately prior to being persisted, or when it is about to be updated.
-The lifecycle callback methods supported by Apache Isis are:
+The lifecycle callback methods supported by Apache Causeway are:
.Lifecycle methods (partial support)
[cols="1m,3a,2m", options="header"]
diff --git a/antora/components/refguide/modules/applib-methods/pages/prefixes.adoc b/antora/components/refguide/modules/applib-methods/pages/prefixes.adoc
index 2584d33313..a29a690e98 100644
--- a/antora/components/refguide/modules/applib-methods/pages/prefixes.adoc
+++ b/antora/components/refguide/modules/applib-methods/pages/prefixes.adoc
@@ -11,7 +11,7 @@ Thus, a property called "firstName", derived from a method `getFirstName()` may
Supporting methods are, therefore, each characterized by their own particular prefix.
-The table below lists the method prefixes that are recognized as part of Apache Isis' default programming model.
+The table below lists the method prefixes that are recognized as part of Apache Causeway' default programming model.
.Method Prefixes
[cols="2m,1,1,1,1,1,4a",options="header"]
@@ -111,7 +111,7 @@ See also xref:refguide:applib-methods:prefixes.adoc#set[set...()].
====
Using name matching to associate supporting methods generally works very well, but of course if an object member's method is renamed, there's always the risk that the developer forgets to rename the supporting method; the supporting methods become "orphaned".
-Apache Isis checks for this automatically, and will fail-fast (fail to boot) if any orphaned methods are located.
+Apache Causeway checks for this automatically, and will fail-fast (fail to boot) if any orphaned methods are located.
A suitable error message is logged so that the issue can be easily diagnosed.
====
diff --git a/antora/components/refguide/modules/applib-methods/pages/prefixes/disable.adoc b/antora/components/refguide/modules/applib-methods/pages/prefixes/disable.adoc
index d9f74b9375..e030fb7e9d 100644
--- a/antora/components/refguide/modules/applib-methods/pages/prefixes/disable.adoc
+++ b/antora/components/refguide/modules/applib-methods/pages/prefixes/disable.adoc
@@ -12,7 +12,7 @@ For parameters, it disables the entry into the parameter; this is for actions wi
Typically modification/invocation is vetoed based on the state of the domain object being interacted with, though it could be any reason at all (eg the current date/time of the interaction, or the state of some other related data such as stock levels, or the identity of the calling user).
The reason for vetoing a modification/invocation is normally returned as a string.
-However, Apache Isis' xref:userguide:btb:i18n.adoc[i18n support] extends this so that reasons can be internationalized.
+However, Apache Causeway' xref:userguide:btb:i18n.adoc[i18n support] extends this so that reasons can be internationalized.
The signature of the supporting method is generally:
diff --git a/antora/components/refguide/modules/applib-methods/pages/prefixes/get.adoc b/antora/components/refguide/modules/applib-methods/pages/prefixes/get.adoc
index befee687fd..a948fa8725 100644
--- a/antora/components/refguide/modules/applib-methods/pages/prefixes/get.adoc
+++ b/antora/components/refguide/modules/applib-methods/pages/prefixes/get.adoc
@@ -7,11 +7,11 @@
The `get...()` prefix is simply the normal JavaBean getter prefix that denotes properties or collections.
-When Apache Isis builds its metamodel, it first searches for the getter methods, characterizing them as either properties or collections based on the return type. It then refines the metamodel based on the presence of annotations and supporting methods.
+When Apache Causeway builds its metamodel, it first searches for the getter methods, characterizing them as either properties or collections based on the return type. It then refines the metamodel based on the presence of annotations and supporting methods.
-All remaining `public` methods (that do not use one of the Apache Isis prefixes) are interpreted as actions.
+All remaining `public` methods (that do not use one of the Apache Causeway prefixes) are interpreted as actions.
-Any methods "left over" that _do_ use one of the Apache Isis prefixes, are interpreted to be orphaned. Apache Isis "fails-fast" and will not boot, instead printing an error message to the log so that the issue can be easily diagnosed.
+Any methods "left over" that _do_ use one of the Apache Causeway prefixes, are interpreted to be orphaned. Apache Causeway "fails-fast" and will not boot, instead printing an error message to the log so that the issue can be easily diagnosed.
See also xref:refguide:applib-methods:prefixes.adoc#set[set...()].
diff --git a/antora/components/refguide/modules/applib-methods/pages/ui-hints/title.adoc b/antora/components/refguide/modules/applib-methods/pages/ui-hints/title.adoc
index 2c2b9a9422..5f2bae8b81 100644
--- a/antora/components/refguide/modules/applib-methods/pages/ui-hints/title.adoc
+++ b/antora/components/refguide/modules/applib-methods/pages/ui-hints/title.adoc
@@ -10,7 +10,7 @@ This appears both as a main header for the object when viewed as well as being u
It therefore must contain enough information for the end-user to distinguish the object from any others.
This is most commonly done by including some unique key within the title, for example a customer's SSN, or an order number, and so forth.
-However note that Apache Isis itself does _not_ require the title to be unique; it is merely recommended in most cases.
+However note that Apache Causeway itself does _not_ require the title to be unique; it is merely recommended in most cases.
An object's title can be constructed in various ways, but the most flexible is to use the `title()` method.
The signature of this method is usually:
@@ -22,7 +22,7 @@ public String title() {
}
----
-Note that Apache Isis' xref:userguide:btb:i18n.adoc[i18n support] extends this so that titles can also be internationalized.
+Note that Apache Causeway' xref:userguide:btb:i18n.adoc[i18n support] extends this so that titles can also be internationalized.
For example, in a todoapp we can use this technique to change the title of items that have been completed:
diff --git a/antora/components/refguide/modules/applib-svc/pages/about.adoc b/antora/components/refguide/modules/applib-svc/pages/about.adoc
index f30990054d..26356d46e7 100644
--- a/antora/components/refguide/modules/applib-svc/pages/about.adoc
+++ b/antora/components/refguide/modules/applib-svc/pages/about.adoc
@@ -5,7 +5,7 @@
-This guide documents Apache Isis' domain services, both those that act as an API (implemented by the framework for your domain objects to call), and those domain services that act as an SPI (implemented by your domain application and which are called by the framework).
+This guide documents Apache Causeway' domain services, both those that act as an API (implemented by the framework for your domain objects to call), and those domain services that act as an SPI (implemented by your domain application and which are called by the framework).
== Types of Domain Service
@@ -50,8 +50,8 @@ include::applib-svc:partial$_security-spi.adoc[leveloffset=+2]
== Public API vs Internal Services
-The vast majority of Apache Isis' domain services are defined in Apache Isis' applib (`o.a.i.core:causeway-applib` module) as stable, public classes.
-Importantly, this also minimizes the coupling between your code and Apache Isis, allowing you to easily mock out these services in your unit tests.
+The vast majority of Apache Causeway' domain services are defined in Apache Causeway' applib (`o.a.i.core:causeway-applib` module) as stable, public classes.
+Importantly, this also minimizes the coupling between your code and Apache Causeway, allowing you to easily mock out these services in your unit tests.
The framework also defines a number of "internal" services.
These are not part of the framework's formal API, in that they use classes that are outside of the applib.
@@ -60,7 +60,7 @@ These internal framework services should be thought of as part of the internal d
== Using the services
-Apache Isis includes an extensive number of domain services for your domain objects to use; simply define the service as an annotated field and Apache Isis will inject the service into your object.
+Apache Causeway includes an extensive number of domain services for your domain objects to use; simply define the service as an annotated field and Apache Causeway will inject the service into your object.
For example:
diff --git a/antora/components/refguide/modules/applib-svc/partials/_application-layer-spi.adoc b/antora/components/refguide/modules/applib-svc/partials/_application-layer-spi.adoc
index d81718e423..d79e15ae39 100644
--- a/antora/components/refguide/modules/applib-svc/partials/_application-layer-spi.adoc
+++ b/antora/components/refguide/modules/applib-svc/partials/_application-layer-spi.adoc
@@ -15,7 +15,7 @@ Domain service SPIs influence how the framework handles application layer concer
|xref:refguide:security:index/spring/authconverters/AuthenticationConverter.adoc[AuthenticationConverter]
-|SPI service for xref:security:spring:about.adoc[Spring Security] to convert a Spring link:https://docs.spring.io/spring-security/site/docs/current/api/org/springframework/security/core/Authentication.html[Authentication] into an Apache Isis xref:refguide:applib:index/services/user/UserMemento.adoc[UserMemento].
+|SPI service for xref:security:spring:about.adoc[Spring Security] to convert a Spring link:https://docs.spring.io/spring-security/site/docs/current/api/org/springframework/security/core/Authentication.html[Authentication] into an Apache Causeway xref:refguide:applib:index/services/user/UserMemento.adoc[UserMemento].
Several implementations are provided by default for most of the common representations of a user principal.
This SPI does though provide additional flexibility for other security technologies that may be supported by link:https://spring.io/projects/spring-security[Spring].
diff --git a/antora/components/refguide/modules/applib-svc/partials/_core-domain-api.adoc b/antora/components/refguide/modules/applib-svc/partials/_core-domain-api.adoc
index c3817c5a37..ae4c18857e 100644
--- a/antora/components/refguide/modules/applib-svc/partials/_core-domain-api.adoc
+++ b/antora/components/refguide/modules/applib-svc/partials/_core-domain-api.adoc
@@ -23,7 +23,7 @@ The core/domain APIs provide general-purpose services to the domain objects, for
|xref:refguide:applib:index/services/eventbus/EventBusService.adoc[EventBusService]
|Programmatically post events to the internal event bus.
-Also used by Apache Isis itself to broadcast domain, UI and lifecycle events.
+Also used by Apache Causeway itself to broadcast domain, UI and lifecycle events.
|xref:refguide:applib:index/services/factory/FactoryService.adoc[FactoryService]
diff --git a/antora/components/refguide/modules/applib-svc/partials/_metadata-api.adoc b/antora/components/refguide/modules/applib-svc/partials/_metadata-api.adoc
index c6a1ed4812..1314b35bdd 100644
--- a/antora/components/refguide/modules/applib-svc/partials/_metadata-api.adoc
+++ b/antora/components/refguide/modules/applib-svc/partials/_metadata-api.adoc
@@ -26,7 +26,7 @@ xref:refguide:applib:index/services/layout/LayoutServiceMenu.adoc[LayoutServiceM
|xref:refguide:applib:index/services/metamodel/MetaModelService.adoc[MetaModelService] & xref:refguide:applib:index/services/metamodel/MetaModelServiceMenu.adoc[MetaModelServiceMenu]
-|Access to certain information from the Apache Isis metamodel.
+|Access to certain information from the Apache Causeway metamodel.
|xref:refguide:applib:index/services/sitemap/SitemapService.adoc[SitemapService] & xref:refguide:applib:index/services/sitemap/SitemapServiceMenu.adoc[SitemapServiceMenu]
diff --git a/antora/components/relnotes/modules/ROOT/pages/about.adoc b/antora/components/relnotes/modules/ROOT/pages/about.adoc
index f3a60b6fcf..f865d39d73 100644
--- a/antora/components/relnotes/modules/ROOT/pages/about.adoc
+++ b/antora/components/relnotes/modules/ROOT/pages/about.adoc
@@ -4,12 +4,12 @@
: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 [...]
-This table summarises all releases of Apache Isis v2.0 to date.
+This table summarises all releases of Apache Causeway v2.0 to date.
////
| 2.0.0-RC1
| not released yet (upcoming)
-| First release candidate for Apache Isis 2.0.0
+| First release candidate for Apache Causeway 2.0.0
| ?
| ?
| ?
@@ -32,7 +32,7 @@ This table summarises all releases of Apache Isis v2.0 to date.
| 2.0.0-M9
| 18-Oct-2022
|
-Ninth milestone release for Apache Isis 2.0.0 +
+Ninth milestone release for Apache Causeway 2.0.0 +
Fixes CVE-2022-42466.
| 2
| 3
@@ -42,7 +42,7 @@ Fixes CVE-2022-42466.
| 2.0.0-M8
| 06-Oct-2022
-| Eighth milestone release for Apache Isis 2.0.0 +
+| Eighth milestone release for Apache Causeway 2.0.0 +
Fixes CVE-2022-42467.
| 26
| 79
@@ -53,7 +53,7 @@ Fixes CVE-2022-42467.
| 2.0.0-M7
| 28-Feb-2022
-| Seventh milestone release for Apache Isis 2.0.0
+| Seventh milestone release for Apache Causeway 2.0.0
| 9
| 17
| 41
@@ -63,7 +63,7 @@ Fixes CVE-2022-42467.
| 2.0.0-M6
| 26-Aug-2021
-| Sixth milestone release for Apache Isis 2.0.0; now JDK11+
+| Sixth milestone release for Apache Causeway 2.0.0; now JDK11+
| 23
| 92
| 92
@@ -73,7 +73,7 @@ Fixes CVE-2022-42467.
| 2.0.0-M5
| 28-Mar-2021
-| Fifth milestone release for Apache Isis 2.0.0
+| Fifth milestone release for Apache Causeway 2.0.0
| 4
| 68
| 44
@@ -83,7 +83,7 @@ Fixes CVE-2022-42467.
| 2.0.0-M4
| 17-Oct-2020
-| Fourth milestone release for Apache Isis 2.0.0
+| Fourth milestone release for Apache Causeway 2.0.0
| 14
| 28
| 56
@@ -94,7 +94,7 @@ Fixes CVE-2022-42467.
| 2.0.0-M3
| 27-Mar-2020
-| Third milestone release for Apache Isis 2.0.0: now re-platformed on top of Spring Boot.
+| Third milestone release for Apache Causeway 2.0.0: now re-platformed on top of Spring Boot.
| 24
| 149
| 46
@@ -105,7 +105,7 @@ Fixes CVE-2022-42467.
| 2.0.0-M2
| 22-Jan-2019
-| Second milestone release for Apache Isis 2.0.0: tree support, initial work on simplifying bootstrapping and configuration, removing dependencies
+| Second milestone release for Apache Causeway 2.0.0: tree support, initial work on simplifying bootstrapping and configuration, removing dependencies
| 2
| 36
| 13
@@ -115,7 +115,7 @@ Fixes CVE-2022-42467.
|2.0.0-M1
| 31-Jul-2018
-| First milestone release for Apache Isis 2.0.0: Java 8 support, DataNucleus 5.1, Wicket 8, meta-annotations, breadcrumbs
+| First milestone release for Apache Causeway 2.0.0: Java 8 support, DataNucleus 5.1, Wicket 8, meta-annotations, breadcrumbs
| 6
| 55
+ 4 tasks
diff --git a/antora/components/setupguide/modules/ROOT/pages/about.adoc b/antora/components/setupguide/modules/ROOT/pages/about.adoc
index ca3ece9e17..ff89053842 100644
--- a/antora/components/setupguide/modules/ROOT/pages/about.adoc
+++ b/antora/components/setupguide/modules/ROOT/pages/about.adoc
@@ -4,7 +4,7 @@
: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 [...]
-The vast majority of Java developers use an IDE to assist with developing their code, and we highly recommend that you do likewise as you develop your Apache Isis applications using an IDE.
+The vast majority of Java developers use an IDE to assist with developing their code, and we highly recommend that you do likewise as you develop your Apache Causeway applications using an IDE.
-The purpose of this guide therefore is to explain how to setup your IDE so you can effectively and efficiently develop your Apache Isis apps.
+The purpose of this guide therefore is to explain how to setup your IDE so you can effectively and efficiently develop your Apache Causeway apps.
diff --git a/antora/components/setupguide/modules/eclipse/pages/about.adoc b/antora/components/setupguide/modules/eclipse/pages/about.adoc
index 271b29b0a8..cd6f58eceb 100644
--- a/antora/components/setupguide/modules/eclipse/pages/about.adoc
+++ b/antora/components/setupguide/modules/eclipse/pages/about.adoc
@@ -13,7 +13,7 @@ If you are an http://www.eclipse.org[Eclipse] user, then we recommend you downlo
//These are used to add new methods to existing classes.
//(These are equivalent to the xref:setupguide:intellij:about.adoc#live-templates[IntelliJ live templates]):
//
-//* `is` (Apache Isis domain objects). link:./resources/eclipse/causeway-templates.xml[Download]
+//* `is` (Apache Causeway domain objects). link:./resources/eclipse/causeway-templates.xml[Download]
//* `ju` (for JUnit tests) link:./resources/eclipse/junit4-templates.xml[Download]
//* `jm` (for JMock mocks or libraries) link:./resources/eclipse/jmock2-templates.xml[Download]
//
@@ -22,7 +22,7 @@ If you are an http://www.eclipse.org[Eclipse] user, then we recommend you downlo
== Install the DataNucleus plugin
-When running an Apache Isis application, it's necessary to setup the development environment so that the Java bytecode can be enhanced by the link:http://www.datanucleus.org[DataNucleus] enhancer.
+When running an Apache Causeway application, it's necessary to setup the development environment so that the Java bytecode can be enhanced by the link:http://www.datanucleus.org[DataNucleus] enhancer.
If using Eclipse, then JDO enhancement is most easily done by installing the http://www.datanucleus.org/products/accessplatform/jpa/tools.html#eclipse[DataNucleus' Eclipse plugin].
This hooks the bytecode enhancement of your domain objects into Eclipse's normal incremental compilation.
@@ -214,7 +214,7 @@ And, remember also to configure Eclipse's DataNucleus plugin for these other dom
//
//link:http://github.com/dcevm/dcevm[DCEVM] enhances the JVM with true hot-swap adding/removing of methods as well as more reliable hot swapping of the implementation of existing methods.
//
-//In the context of Apache Isis, this is very useful for contributed actions and mixins and also view models; you should then be able to write these actions and have them be picked up without restarting the application.
+//In the context of Apache Causeway, this is very useful for contributed actions and mixins and also view models; you should then be able to write these actions and have them be picked up without restarting the application.
//
//Changing persisting domain entities is more problematic, for two reasons: the JDO/DataNucleus enhancer needs to run on domain entities, and also at runtime JDO/DataNucleus would need to rebuild its own metamodel.
//You may find that adding actions will work, but adding new properties or collections is much less likely to.
diff --git a/antora/components/setupguide/modules/intellij/partials/UNUSED/coding-standards.adoc b/antora/components/setupguide/modules/intellij/partials/UNUSED/coding-standards.adoc
index dc2c1ddeb0..f347a65ae0 100644
--- a/antora/components/setupguide/modules/intellij/partials/UNUSED/coding-standards.adoc
+++ b/antora/components/setupguide/modules/intellij/partials/UNUSED/coding-standards.adoc
@@ -4,7 +4,7 @@
CAUTION: seem to have mislaid this file... would need verifying/updating anyway, I think.
-Next, we suggest you import settings for standard ASF/Apache Isis coding conventions.
+Next, we suggest you import settings for standard ASF/Apache Causeway coding conventions.
This file is also provided as a settings file, namely *link:{attachmentsdir}/intellij/causeway-settings-code-style.jar[causeway-settings-code-style.jar]*.
Download and import (as for the above settings JAR files).
diff --git a/antora/components/setupguide/modules/intellij/partials/UNUSED/faster-turnaround-times.adoc b/antora/components/setupguide/modules/intellij/partials/UNUSED/faster-turnaround-times.adoc
index a56d5c826b..efd2c0c8c4 100644
--- a/antora/components/setupguide/modules/intellij/partials/UNUSED/faster-turnaround-times.adoc
+++ b/antora/components/setupguide/modules/intellij/partials/UNUSED/faster-turnaround-times.adoc
@@ -8,7 +8,7 @@ In this section are several options that will reduce the time it takes between m
== Using Grade to compile/enhance
-Running an Apache Isis application requires that the DataNucleus enhancer runs on the compiled bytecode.
+Running an Apache Causeway application requires that the DataNucleus enhancer runs on the compiled bytecode.
As described xref:setupguide:intellij:about.adoc#running-the-app[above], the recommended way to do this with IntelliJ is to use a Run configuration that runs the enhancer goal prior to launch.
Alternative, you can use the following `build.gradle` script in your `dom` module:
@@ -152,7 +152,7 @@ image::070-advanced/006-livereload-js.png[width="800px"]
link:http://github.com/dcevm/dcevm[DCEVM] enhances the JVM with true hot-swap adding/removing of methods as well as more reliable hot swapping of the implementation of existing methods.
-In the context of Apache Isis, this is very useful for contributed actions and mixins and also view models; you should then be able to write these actions and have them be picked up without restarting the application.
+In the context of Apache Causeway, this is very useful for contributed actions and mixins and also view models; you should then be able to write these actions and have them be picked up without restarting the application.
Changing persisting domain entities is more problematic, for two reasons: the JDO/DataNucleus enhancer needs to run on domain entities, and also at runtime JDO/DataNucleus would need to rebuild its own metamodel.
You may find that adding actions will work, but adding new properties or collections is much less likely to.
@@ -190,7 +190,7 @@ image::070-advanced/040-dcevm-run-configuration.png[width="600px"]
== Setting up JRebel
-See the repo for the (non-ASF) link:https://github.com/isisaddons/causeway-jrebel-plugin[Isis JRebel] plugin.
+See the repo for the (non-ASF) link:https://github.com/isisaddons/causeway-jrebel-plugin[Causeway JRebel] plugin.
Note that JRebel is a commercial product, requiring a license.
At the time of writing there is also currently a non-commercial free license (though note this comes with some usage conditions).
diff --git a/antora/components/setupguide/modules/intellij/partials/UNUSED/live-templates.adoc b/antora/components/setupguide/modules/intellij/partials/UNUSED/live-templates.adoc
index a3c3fee898..2060709022 100644
--- a/antora/components/setupguide/modules/intellij/partials/UNUSED/live-templates.adoc
+++ b/antora/components/setupguide/modules/intellij/partials/UNUSED/live-templates.adoc
@@ -11,7 +11,7 @@ image::030-import-settings/050-live-templates.png[width="600px"]
The live templates have a prefix of either:
-* `is` : for Apache Isis domain objects
+* `is` : for Apache Causeway domain objects
* `ju` : for JUnit tests
* `jm` : for JMock mocks or libraries
diff --git a/antora/components/tutorials/modules/ROOT/pages/about.adoc b/antora/components/tutorials/modules/ROOT/pages/about.adoc
index 6605d1768f..a4be505339 100644
--- a/antora/components/tutorials/modules/ROOT/pages/about.adoc
+++ b/antora/components/tutorials/modules/ROOT/pages/about.adoc
@@ -4,7 +4,7 @@
: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 [...]
-This page catalogues the tutorials available to help you learn Apache Isis.
+This page catalogues the tutorials available to help you learn Apache Causeway.
* xref:petclinic:about.adoc[Petclinic]
+
diff --git a/antora/components/tutorials/modules/petclinic/pages/010-getting-started.adoc b/antora/components/tutorials/modules/petclinic/pages/010-getting-started.adoc
index 0553c67572..2453f12873 100644
--- a/antora/components/tutorials/modules/petclinic/pages/010-getting-started.adoc
+++ b/antora/components/tutorials/modules/petclinic/pages/010-getting-started.adoc
@@ -10,7 +10,7 @@ You'll need:
* Java 11
+
-Apache Isis should work up to at least Java 15, but stick with Java 11 for now.
+Apache Causeway should work up to at least Java 15, but stick with Java 11 for now.
* Maven 3.6.x
+
@@ -23,7 +23,7 @@ This has multiple tags for the various checkpoints so you can pick up the tutori
* a Java IDE with support for Maven.
+
-The Apache Isis website has detailed documentation for setting up to use xref:setupguide:intellij:about.adoc[IntelliJ] or xref:setupguide:eclipse:about.adoc[Eclipse].
+The Apache Causeway website has detailed documentation for setting up to use xref:setupguide:intellij:about.adoc[IntelliJ] or xref:setupguide:eclipse:about.adoc[Eclipse].
+
For this tutorial, make sure that your IDE is configured to support Lombok.
@@ -32,7 +32,7 @@ For this tutorial, make sure that your IDE is configured to support Lombok.
[#exercise-1-1-starter-apps-clone-the-repo]
== Ex 1.1: Starter apps / clone the repo
-Apache Isis provides a two starter apps, xref:docs:starters:helloworld.adoc[HelloWorld] and xref:docs:starters:simpleapp.adoc[SimpleApp].
+Apache Causeway provides a two starter apps, xref:docs:starters:helloworld.adoc[HelloWorld] and xref:docs:starters:simpleapp.adoc[SimpleApp].
These are identical in terms of functionality, but the simpleapp provides more structure and includes example tests.
NOTE: there are JPA and JDO variants of the starter apps.
@@ -106,12 +106,12 @@ If you want to go deeper, open up the xref:docs:starters:simpleapp.adoc[page des
[#exercise-1-4-naked-objects-pattern]
== Ex 1.4: Naked Objects pattern
-Apache Isis is an implementation of the _naked objects pattern_, which means that entities (and later, as we'll see view models) are automatically exposed in the UI.
+Apache Causeway is an implementation of the _naked objects pattern_, which means that entities (and later, as we'll see view models) are automatically exposed in the UI.
[TIP]
====
An ORM such as JPA (EclipseLink or Hibernate) maps domain objects into an RDBMS or other datastore.
-You can think of Apache Isis (and naked objects) similarly, but it's an OIM - an object _interface_ mapper.
+You can think of Apache Causeway (and naked objects) similarly, but it's an OIM - an object _interface_ mapper.
It maps to the UI layer rather than the persistence layer.
Common to both ORMs and OIMs is an internal metamodel; this is where much of the power comes from.
@@ -133,7 +133,7 @@ It's common for each entity (or more precisely, aggregate root) to have a corres
This abstraction hides the details of interacting with the persistence data store.
Domain services are automatically injected wherever they are required, using `@javax.inject.Inject`.
-Apache Isis applications therefore generally follow the _hexagonal architecture_ (aka the _ports and adapters_ architecture).
+Apache Causeway applications therefore generally follow the _hexagonal architecture_ (aka the _ports and adapters_ architecture).
As well as writing our own domain services, there are also many framework-provided domain services, for example `RepositoryService` (to persist objects).
See the xref:refguide:applib-svc:about.adoc[Reference Guide: Domain Services] docs for the full list.
@@ -189,13 +189,13 @@ Frameworks that implement the _naked objects pattern_ automatically provide a de
In many cases the details of that representation can be inferred directly from the domain members.
For example the label of a field for an object's property (eg `SimpleObject#name`) can be derived directly from the name of the object property itself (`getName()`).
-In the absence of other metadata, Apache Isis will render a domain object with its properties to the left-hand side and its collections (if any) to the right.
+In the absence of other metadata, Apache Causeway will render a domain object with its properties to the left-hand side and its collections (if any) to the right.
The order of these properties and collections can be specified using the `@PropertyLayout` annotation and the `@CollectionLayout` annotation.
There are other annotations to group properties together and to associate action buttons with either properties or collections.
The downside of using annotations is that changing the layout requires that the application be restarted, and certain more complex UIs, such as multi-columns or tab groups are difficult or impossible to express.
-Therefore Apache Isis also allows the layout of domain objects to be specified using a complementary layout file, eg `SimpleObject.layout.xml`.
+Therefore Apache Causeway also allows the layout of domain objects to be specified using a complementary layout file, eg `SimpleObject.layout.xml`.
This is modelled upon bootstrap and so supports arbitrary rows and columns as well as tab groups and tabs.
*Mini-Exercise*:
diff --git a/antora/components/tutorials/modules/petclinic/pages/020-the-petclinic-domain.adoc b/antora/components/tutorials/modules/petclinic/pages/020-the-petclinic-domain.adoc
index cc89c84d66..bd3033c4a4 100644
--- a/antora/components/tutorials/modules/petclinic/pages/020-the-petclinic-domain.adoc
+++ b/antora/components/tutorials/modules/petclinic/pages/020-the-petclinic-domain.adoc
@@ -2,7 +2,7 @@
= An Example Domain
-By now you should understand the basics of what Apache Isis does, but there's only so much we can learn from a single domain class.
+By now you should understand the basics of what Apache Causeway does, but there's only so much we can learn from a single domain class.
Let's therefore evolve the app into a slightly more interesting domain and explore other features of the framework.
The domain we're going to work on is a version of the venerable "Pet Clinic" app.
diff --git a/antora/components/userguide/modules/ROOT/pages/about.adoc b/antora/components/userguide/modules/ROOT/pages/about.adoc
index 1a3a63377f..890a0a38f5 100644
--- a/antora/components/userguide/modules/ROOT/pages/about.adoc
+++ b/antora/components/userguide/modules/ROOT/pages/about.adoc
@@ -4,9 +4,9 @@
: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 [...]
-This guide introduces the xref:userguide:fun:concepts-patterns.adoc[core concepts] and provides an xref:userguide:fun:overview.adoc[overview] of the building blocks of Apache Isis applications.
+This guide introduces the xref:userguide:fun:concepts-patterns.adoc[core concepts] and provides an xref:userguide:fun:overview.adoc[overview] of the building blocks of Apache Causeway applications.
-It next describes the basics of the Apache Isis' programming model: xref:userguide:fun:domain-entities-and-services.adoc[domain entities and services], xref:userguide:fun:object-members.adoc[object members], xref:userguide:fun:ui.adoc[UI layout and hints], xref:userguide:fun:business-rules.adoc[business rules] and xref:userguide:fun:drop-downs-and-defaults.adoc[drop downs and defaults].
+It next describes the basics of the Apache Causeway' programming model: xref:userguide:fun:domain-entities-and-services.adoc[domain entities and services], xref:userguide:fun:object-members.adoc[object members], xref:userguide:fun:ui.adoc[UI layout and hints], xref:userguide:fun:business-rules.adoc[business rules] and xref:userguide:fun:drop-downs-and-defaults.adoc[drop downs and defaults].
This includes a discussion on xref:userguide:fun:domain-entities-and-services.adoc#object-management-crud[the basic CRUD operations].
diff --git a/antora/components/userguide/modules/btb/pages/about.adoc b/antora/components/userguide/modules/btb/pages/about.adoc
index 651c83cebf..16584c1229 100644
--- a/antora/components/userguide/modules/btb/pages/about.adoc
+++ b/antora/components/userguide/modules/btb/pages/about.adoc
@@ -3,7 +3,7 @@
: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 [...]
-This chapter covers a miscellany of more advanced topics that may be of help when developing your Apache Isis applications.
+This chapter covers a miscellany of more advanced topics that may be of help when developing your Apache Causeway applications.
diff --git a/antora/components/userguide/modules/btb/pages/headless-access.adoc b/antora/components/userguide/modules/btb/pages/headless-access.adoc
index eef541482a..0d65fc104f 100644
--- a/antora/components/userguide/modules/btb/pages/headless-access.adoc
+++ b/antora/components/userguide/modules/btb/pages/headless-access.adoc
@@ -4,18 +4,18 @@
: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 [...]
:page-partial:
-This section tackles the topic of enabling access to an Apache Isis application directly, or at least, not through either the xref:vw:ROOT:about.adoc[Wicket] or xref:vro:ROOT:about.adoc[Restful] viewers.
+This section tackles the topic of enabling access to an Apache Causeway application directly, or at least, not through either the xref:vw:ROOT:about.adoc[Wicket] or xref:vro:ROOT:about.adoc[Restful] viewers.
There are a number of use-cases:
-* implementing a REST end point that needs to reach into the Apache Isis runtime
+* implementing a REST end point that needs to reach into the Apache Causeway runtime
** this could be a custom UI
-** this could be to integrate from other systems, eg a subscriber on a pub/sub event bus, pushing changes through an Apache Isis domain model.
+** this could be to integrate from other systems, eg a subscriber on a pub/sub event bus, pushing changes through an Apache Causeway domain model.
* calling from Quartz for a background batch process
-Note that the calling thread runs in the same process space as the Apache Isis domain object model (must be physically linked to the JAR files containing the domain classes).
+Note that the calling thread runs in the same process space as the Apache Causeway domain object model (must be physically linked to the JAR files containing the domain classes).
The xref:docs:starters:simpleapp.adoc[SimpleApp] starter app demonstrates the pattern with a custom UI controller:
@@ -55,6 +55,6 @@ class CustomController {
<.> handles null case, if required
<.> a more sophisticated implementation could inspect the HTTP request
-The API described here is reasonably low-level, allowing code to interact very directly with the Apache Isis metamodel and runtime.
-Such callers should be considered trusted: they do not (by default) honour any business rules eg implicit in the Isis annotations or hide/disable/validate methods.
+The API described here is reasonably low-level, allowing code to interact very directly with the Apache Causeway metamodel and runtime.
+Such callers should be considered trusted: they do not (by default) honour any business rules eg implicit in the Causeway annotations or hide/disable/validate methods.
diff --git a/antora/components/userguide/modules/btb/pages/hints-and-tips.adoc b/antora/components/userguide/modules/btb/pages/hints-and-tips.adoc
index d60da6c169..9229c2b24d 100644
--- a/antora/components/userguide/modules/btb/pages/hints-and-tips.adoc
+++ b/antora/components/userguide/modules/btb/pages/hints-and-tips.adoc
@@ -6,7 +6,7 @@
-This chapter provides some solutions for problems we've encountered ourselves or have been raised on the Apache Isis mailing lists.
+This chapter provides some solutions for problems we've encountered ourselves or have been raised on the Apache Causeway mailing lists.
diff --git a/antora/components/userguide/modules/btb/pages/hints-and-tips/how-to-handle-void-and-null-results.adoc b/antora/components/userguide/modules/btb/pages/hints-and-tips/how-to-handle-void-and-null-results.adoc
index c5b62e0a4d..a63f35fae5 100644
--- a/antora/components/userguide/modules/btb/pages/hints-and-tips/how-to-handle-void-and-null-results.adoc
+++ b/antora/components/userguide/modules/btb/pages/hints-and-tips/how-to-handle-void-and-null-results.adoc
@@ -6,7 +6,7 @@
-From this link:http://causeway.markmail.org/thread/yf7qdeiu3vrvk2ei[thread] on the Apache Isis users mailing list:
+From this link:http://causeway.markmail.org/thread/yf7qdeiu3vrvk2ei[thread] on the Apache Causeway users mailing list:
* _When using a `void` action, let's say a remove action, the user is redirected to a
page "no results".
@@ -73,8 +73,8 @@ public class RoutingServiceUsingBreadcrumbs
<.> ensure that any persisted objects have been deleted.
<.> reach inside the Wicket viewer's internals to obtain the list of breadcrumbs.
<.> loop over all breadcrumbs
-<.> unwrap the Wicket viewer's serializable representation of each domain object (`EntityModel`) to the Isis runtime's representation (`ManagedObject`)
-<.> unwrap the Isis runtime's representation of each domain object (`ManagedObject`) to the domain object pojo itself
+<.> unwrap the Wicket viewer's serializable representation of each domain object (`EntityModel`) to the Causeway runtime's representation (`ManagedObject`)
+<.> unwrap the Causeway runtime's representation of each domain object (`ManagedObject`) to the domain object pojo itself
<.> if object is persistable (not a view model) then make sure it is not deleted
<.> return the first object if any, otherwise the home page object (if any).
diff --git a/antora/components/userguide/modules/btb/pages/hints-and-tips/how-to-implement-a-spellchecker.adoc b/antora/components/userguide/modules/btb/pages/hints-and-tips/how-to-implement-a-spellchecker.adoc
index 0545ec03e7..10acc90002 100644
--- a/antora/components/userguide/modules/btb/pages/hints-and-tips/how-to-implement-a-spellchecker.adoc
+++ b/antora/components/userguide/modules/btb/pages/hints-and-tips/how-to-implement-a-spellchecker.adoc
@@ -6,7 +6,7 @@
-From this link:http://causeway.markmail.org/thread/dduarjscrbnodfsi[thread] on the Apache Isis users mailing list:
+From this link:http://causeway.markmail.org/thread/dduarjscrbnodfsi[thread] on the Apache Causeway users mailing list:
* _What is the easiest way to add a spell checker to the text written in a field in
a domain object, for instance to check English syntax?_
diff --git a/antora/components/userguide/modules/btb/pages/hints-and-tips/replacing-default-service-implementations.adoc b/antora/components/userguide/modules/btb/pages/hints-and-tips/replacing-default-service-implementations.adoc
index 195bfa633a..84f7c60c6a 100644
--- a/antora/components/userguide/modules/btb/pages/hints-and-tips/replacing-default-service-implementations.adoc
+++ b/antora/components/userguide/modules/btb/pages/hints-and-tips/replacing-default-service-implementations.adoc
@@ -20,7 +20,7 @@ Here's how:
@Priority(PriorityPrecedence.EARLY) // <.>
public class MyLanguageProvider implements LanguageProvider { ... }
----
-<.> `PriorityPrecedence` (in the Apache Isis applib) provides some standard values.
+<.> `PriorityPrecedence` (in the Apache Causeway applib) provides some standard values.
== Decorating existing implementations
diff --git a/antora/components/userguide/modules/btb/pages/hints-and-tips/simulating-collections-of-values.adoc b/antora/components/userguide/modules/btb/pages/hints-and-tips/simulating-collections-of-values.adoc
index 1c023e808e..cf399ae7fc 100644
--- a/antora/components/userguide/modules/btb/pages/hints-and-tips/simulating-collections-of-values.adoc
+++ b/antora/components/userguide/modules/btb/pages/hints-and-tips/simulating-collections-of-values.adoc
@@ -6,7 +6,7 @@
-Although in Apache Isis you can have properties of either values (string, number, date etc) or of (references to other) entities, with collections the framework (currently) only supports collections of (references to) entities. That is, collections of values (a bag of numbers, say) are not supported.
+Although in Apache Causeway you can have properties of either values (string, number, date etc) or of (references to other) entities, with collections the framework (currently) only supports collections of (references to) entities. That is, collections of values (a bag of numbers, say) are not supported.
However, it is possible to simulate a bag of numbers using view models.
@@ -19,5 +19,5 @@ NOTE: FIXME
== Persistence Concerns
-NOTE: FIXME - easiest to simply store using DataNucleus' support for collections, marked as xref:refguide:applib:index/annotation/Programmatic.adoc[@Programmatic] so that it is ignored by Apache Isis. Alternatively can store as json/xml in a varchar(4000) or clob and manually unpack.
+NOTE: FIXME - easiest to simply store using DataNucleus' support for collections, marked as xref:refguide:applib:index/annotation/Programmatic.adoc[@Programmatic] so that it is ignored by Apache Causeway. Alternatively can store as json/xml in a varchar(4000) or clob and manually unpack.
diff --git a/antora/components/userguide/modules/btb/pages/hints-and-tips/transactions-and-errors.adoc b/antora/components/userguide/modules/btb/pages/hints-and-tips/transactions-and-errors.adoc
index 2912dc7c91..b10d7cd842 100644
--- a/antora/components/userguide/modules/btb/pages/hints-and-tips/transactions-and-errors.adoc
+++ b/antora/components/userguide/modules/btb/pages/hints-and-tips/transactions-and-errors.adoc
@@ -4,9 +4,9 @@
: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 [...]
:page-partial:
-In Apache Isis, every interaction (action invocation or property edit) is automatically wrapped in a transaction, and any repository query automatically does a flush before hand.
+In Apache Causeway, every interaction (action invocation or property edit) is automatically wrapped in a transaction, and any repository query automatically does a flush before hand.
-What that means is that there's no need to explicitly start or commit transactions in Apache Isis; this will be done for you.
+What that means is that there's no need to explicitly start or commit transactions in Apache Causeway; this will be done for you.
Indeed, if you do try to manage transactions (eg by reaching into the JDO `PersistenceManager` exposed by the xref:refguide:persistence:index/jdo/applib/services/JdoSupportService.adoc[JdoSupportService] domain service, then you are likely to confuse the framework and get a stack trace for your trouble.
However, you can complete a given transaction and start a new one.
@@ -54,7 +54,7 @@ None of these messages/errors has any influence on the transaction; any changes
== Aborting transactions
-If you want to abort Apache Isis' transaction, this can be done by throwing an exception.
+If you want to abort Apache Causeway' transaction, this can be done by throwing an exception.
The exception message is displayed to the user on the error page (if xref:vw:ROOT:about.adoc[Web UI (Wicket viewer)]) or a 500 status error code (if the
xref:vro:ROOT:about.adoc[Restful Objects] viewer).
diff --git a/antora/components/userguide/modules/btb/pages/i18n.adoc b/antora/components/userguide/modules/btb/pages/i18n.adoc
index 9a1ee8716e..7e79b2a955 100644
--- a/antora/components/userguide/modules/btb/pages/i18n.adoc
+++ b/antora/components/userguide/modules/btb/pages/i18n.adoc
@@ -5,14 +5,14 @@
:page-partial:
-Apache Isis' support for internationlization (i18n) allows every element of the domain model (the class names, property names, action names, parameter names and so forth) to be translated.
+Apache Causeway' support for internationlization (i18n) allows every element of the domain model (the class names, property names, action names, parameter names and so forth) to be translated.
It also supports translations of messages raised imperatively, by which we mean as the result of a call to `title()` to obtain an object's title, or messages resulting from any business rule violations (eg xref:refguide:applib-methods:prefixes.adoc#disable[disable...()] or xref:refguide:applib-methods:prefixes.adoc#validate[validate...()], and so on.
The xref:vw:ROOT:about.adoc[Web UI (Wicket viewer)] (that is, its labels and messages) is also internationalized using the same mechanism.
If no translations are available, then the Wicket viewer falls back to using Wicket resource bundles.
-Isis does not translate the values of your domain objects, though.
+Causeway does not translate the values of your domain objects, though.
So, if you have a domain concept such as `Country` whose name is intended to be localized according to the current user, you will need to model this yourself.
== Implementation Approach
@@ -24,7 +24,7 @@ However, there are some serious drawbacks in this approach, including:
* there is no support for plural forms (see this link:http://stackoverflow.com/questions/14326653/java-internationalization-i18n-with-proper-plurals/14327683#14327683[SO answer])
* there is no tooling support for translators
-Apache Isis therefore takes a different approach, drawing inspiration from GNU's https://www.gnu.org/software/gettext/manual/index.html[gettext] API and specifically its `.pot` and `.po` files.
+Apache Causeway therefore takes a different approach, drawing inspiration from GNU's https://www.gnu.org/software/gettext/manual/index.html[gettext] API and specifically its `.pot` and `.po` files.
These are intended to be used as follows:
* the `.pot` (portable object template) file holds the message text to be translated
@@ -37,7 +37,7 @@ These message strings can also have singular and plural forms.
[IMPORTANT]
====
-Although Apache Isis' implementation is modelled after GNU's API, it does _not_ use any GNU software.
+Although Apache Causeway' implementation is modelled after GNU's API, it does _not_ use any GNU software.
This is for two reasons: (a) to simplify the toolchain/developer experience, and (b) because GNU software is usually GPL, which would be incompatible with the Apache license.
====
@@ -50,7 +50,7 @@ This design tackles all the issues of ``ResourceBundle``s:
In fact, there are also online communities/platforms of translators to assist with translating files.
One such is https://crowdin.com/[crowdin] (nb: this link does not imply endorsement).
-In Apache Isis' implementation, if the translation is missing from the `.po` file then the original message text from the `.pot` file will be returned.
+In Apache Causeway' implementation, if the translation is missing from the `.po` file then the original message text from the `.pot` file will be returned.
In fact, it isn't even necessary for there to be any `.po` files; `.po` translations can be added piecemeal as the need arises.
== API
diff --git a/antora/components/userguide/modules/btb/pages/other-techniques.adoc b/antora/components/userguide/modules/btb/pages/other-techniques.adoc
index 4f74dc3bf9..b02db592e0 100644
--- a/antora/components/userguide/modules/btb/pages/other-techniques.adoc
+++ b/antora/components/userguide/modules/btb/pages/other-techniques.adoc
@@ -6,7 +6,7 @@
-This chapter pulls together a number of more advanced techniques that we've discovered and developed while building our own Apache Isis applications.
+This chapter pulls together a number of more advanced techniques that we've discovered and developed while building our own Apache Causeway applications.
diff --git a/antora/components/userguide/modules/btb/pages/programming-model.adoc b/antora/components/userguide/modules/btb/pages/programming-model.adoc
index 13a2fd64b0..17b5f4f0c6 100644
--- a/antora/components/userguide/modules/btb/pages/programming-model.adoc
+++ b/antora/components/userguide/modules/btb/pages/programming-model.adoc
@@ -5,7 +5,7 @@
:page-partial:
-This chapter explains the main APIs to extend or alter the programming conventions that Apache Isis understands to
+This chapter explains the main APIs to extend or alter the programming conventions that Apache Causeway understands to
build up its metamodel.
diff --git a/antora/components/userguide/modules/btb/pages/programming-model/custom-validator.adoc b/antora/components/userguide/modules/btb/pages/programming-model/custom-validator.adoc
index 8763f51978..77b5cc8981 100644
--- a/antora/components/userguide/modules/btb/pages/programming-model/custom-validator.adoc
+++ b/antora/components/userguide/modules/btb/pages/programming-model/custom-validator.adoc
@@ -4,7 +4,7 @@
: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 [...]
:page-partial:
-Apache Isis' programming model includes a validator component that detects and prevents (by failing fast) a number of situations where the domain model is logically inconsistent.
+Apache Causeway' programming model includes a validator component that detects and prevents (by failing fast) a number of situations where the domain model is logically inconsistent.
For example, the validator will detect any orphaned supporting methods (eg `hideXxx()`) if the corresponding property or action has been renamed or deleted but the supporting method was not also updated.
Another example is that a class cannot have a title specified both using `title()` method and also using `@Title` annotation.
@@ -19,7 +19,7 @@ There are several ways to go about implementing a validator.
=== `MetaModelValidator`
-Any custom validator must implement Apache Isis' internal `MetaModelValidator` interface, so the simplest option is just to implement `MetaModelValidator` directly:
+Any custom validator must implement Apache Causeway' internal `MetaModelValidator` interface, so the simplest option is just to implement `MetaModelValidator` directly:
[source,java]
----
diff --git a/antora/components/userguide/modules/btb/pages/programming-model/finetuning.adoc b/antora/components/userguide/modules/btb/pages/programming-model/finetuning.adoc
index 1ffb743160..9f61a7b202 100644
--- a/antora/components/userguide/modules/btb/pages/programming-model/finetuning.adoc
+++ b/antora/components/userguide/modules/btb/pages/programming-model/finetuning.adoc
@@ -5,7 +5,7 @@
:page-partial:
-The core metamodel defines APIs and implementations for building the Apache Isis metamodel: a description of the set of entities, domain services and values that make up the domain model.
+The core metamodel defines APIs and implementations for building the Apache Causeway metamodel: a description of the set of entities, domain services and values that make up the domain model.
The description of each domain class consists of a number of elements:
@@ -23,7 +23,7 @@ The property's type is either a reference to another entity, or is a value type.
link:https://github.com/apache/causeway/blob/master/core/metamodel/src/main/java/org/apache/causeway/core/metamodel/spec/feature/OneToManyAssociation.java[OneToManyAssociation]::
Represents a class member that is a collection of references to other entities.
-Note that Apache Isis does not currently support collections of values.
+Note that Apache Causeway does not currently support collections of values.
link:https://github.com/apache/causeway/blob/master/core/metamodel/src/main/java/org/apache/causeway/core/metamodel/spec/feature/ObjectAction.java[ObjectAction]::
@@ -36,7 +36,7 @@ Two special `FacetFactory` implementations - link:https://github.com/apache/caus
Pretty much all the other ``FacetFactory``s are responsible for installing https://github.com/apache/causeway/blob/master/core/metamodel/src/main/java/org/apache/causeway/core/metamodel/facetapi/Facet.java[Facet]s onto the metamodel elements.
There are many many such ``Facet``s, and are used to do such things get values from properties or collections, modify properties or collections, invoke action, hide or disable class members, provide UI hints for class members, and so on.
-In short, the ``FacetFactory``s registered defines the Apache Isis programming conventions.
+In short, the ``FacetFactory``s registered defines the Apache Causeway programming conventions.
== Modifying the Prog. Model
diff --git a/antora/components/userguide/modules/fun/pages/concepts-patterns.adoc b/antora/components/userguide/modules/fun/pages/concepts-patterns.adoc
index 81edbbfaa4..3fc08c18ad 100644
--- a/antora/components/userguide/modules/fun/pages/concepts-patterns.adoc
+++ b/antora/components/userguide/modules/fun/pages/concepts-patterns.adoc
@@ -3,7 +3,7 @@
: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 [...]
:page-partial:
-This introductory chapter should give you a good about what Apache Isis actually *is*: the ideas and principles that it builds upon, what its core values are, its architecture, how it compares to other architectural approaches other frameworks, and how it can be deployed.
+This introductory chapter should give you a good about what Apache Causeway actually *is*: the ideas and principles that it builds upon, what its core values are, its architecture, how it compares to other architectural approaches other frameworks, and how it can be deployed.
include::concepts-patterns/domain-driven-design.adoc[leveloffset=+1]
diff --git a/antora/components/userguide/modules/fun/pages/concepts-patterns/apache-isis-vs-cqrs-and-event-sourcing.adoc b/antora/components/userguide/modules/fun/pages/concepts-patterns/apache-isis-vs-cqrs-and-event-sourcing.adoc
index d6b438f9c3..276fb87b30 100644
--- a/antora/components/userguide/modules/fun/pages/concepts-patterns/apache-isis-vs-cqrs-and-event-sourcing.adoc
+++ b/antora/components/userguide/modules/fun/pages/concepts-patterns/apache-isis-vs-cqrs-and-event-sourcing.adoc
@@ -1,10 +1,10 @@
-= Apache Isis vs CQRS/ES
+= Apache Causeway vs CQRS/ES
: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 [...]
:page-partial:
CQRS and Event Sourcing (ES) are two architectural patterns often used (and often used together) to implement domain driven design systems.
-This section explores the similarities and differences that Apache Isis has with these other architectural approaches.
+This section explores the similarities and differences that Apache Causeway has with these other architectural approaches.
[#cqrs]
== CQRS
@@ -34,32 +34,32 @@ When invoked, this emits a corresponding `OrderPlacedEvent`.
It is this event that is used to maintain the read model projection.
-Comparing CQRS to Apache Isis, the most obvious difference is that Apache Isis does not require that the command/write model is separated from the query/read model; there is usually just a single datastore.
-But then again, having a separate read model just so that the querying is very straightforward is pointless with Apache Isis because, of course, Isis provides the UI "for free".
+Comparing CQRS to Apache Causeway, the most obvious difference is that Apache Causeway does not require that the command/write model is separated from the query/read model; there is usually just a single datastore.
+But then again, having a separate read model just so that the querying is very straightforward is pointless with Apache Causeway because, of course, Causeway provides the UI "for free".
-It is possible though to use Apache Isis in a CQRS style.
+It is possible though to use Apache Causeway in a CQRS style.
The entities would have no behaviour in and of themselves to modify their state, they would just be data structures.
The behaviour (commands) would instead be implemented as xref:userguide:fun:mixins.adoc[mixins] that act upon those commands.
In the UI (surfaced by the xref:vw:ROOT:about.adoc[Web UI (Wicket viewer)]) or in the REST API (surfaced by the xref:vro:ROOT:about.adoc[RestfulObjects viewer]) the behaviour appears to reside on the domain object; however the behaviour actually resides on separate classes and is mixed in (like a trait), only at runtime.
However, this wouldn't be true CQRS because those mixins would modify those entities which would then be flushed back to the single database.
-Apache Isis' cross-cutting design does allow for denormalized data stores to be implemented.
-For example, there are community implementations of link:https://github.com/erikdehair/causeway-module-elasticsearch[Elastic Search database] to enable a free-text search (this is likely to be incorporated into the Apache Isis framework in the future, if it hasn't already).
+Apache Causeway' cross-cutting design does allow for denormalized data stores to be implemented.
+For example, there are community implementations of link:https://github.com/erikdehair/causeway-module-elasticsearch[Elastic Search database] to enable a free-text search (this is likely to be incorporated into the Apache Causeway framework in the future, if it hasn't already).
There are other reasons why a separate read model might make sense, such as to precompute particular queries, or against denormalized data.
-In these cases Apache Isis can often provide a reasonable alternative, namely to map domain entities against RDBMS views, either materialized views or dynamic.
+In these cases Apache Causeway can often provide a reasonable alternative, namely to map domain entities against RDBMS views, either materialized views or dynamic.
In such cases there is still only a single physical datastore, and so transactional integrity is retained.
-If you want to go all-in with CQRS with separate databases for the write and read model, then this could still be implemented with Apache Isis without pulling the framework apart too much.
-Here, Apache Isis would be used to provide the UI for the _read_ model, with the entities being truly immutable.
-Mixins would decorate these entities, but would act upon a write model whose persistence is handled outside of Apache Isis, probably using Spring Boot directly to provide a datasource.
+If you want to go all-in with CQRS with separate databases for the write and read model, then this could still be implemented with Apache Causeway without pulling the framework apart too much.
+Here, Apache Causeway would be used to provide the UI for the _read_ model, with the entities being truly immutable.
+Mixins would decorate these entities, but would act upon a write model whose persistence is handled outside of Apache Causeway, probably using Spring Boot directly to provide a datasource.
To synchronise the write- and read- model, the events emitted by xref:refguide:applib:index/services/publishing/spi/ExecutionSubscriber.adoc[ExecutionSubscriber] could be used.
-With respect to commands, Apache Isis provides the xref:refguide:applib:index/services/publishing/spi/CommandSubscriber.adoc[CommandSubscriber] which allows each business action to be reified into a xref:refguide:applib:index/services/command/Command.adoc[Command].
-However, names are misleading here: Apache Isis' commands are relatively passive, merely recording the intent of the user to invoke some operation.
+With respect to commands, Apache Causeway provides the xref:refguide:applib:index/services/publishing/spi/CommandSubscriber.adoc[CommandSubscriber] which allows each business action to be reified into a xref:refguide:applib:index/services/command/Command.adoc[Command].
+However, names are misleading here: Apache Causeway' commands are relatively passive, merely recording the intent of the user to invoke some operation.
In a CQRS architecture, commands take a more active role, locating and acting upon the domain objects.
More significantly, in CQRS each command has its own class, such as `PlaceOrderCommand`, instantiated by the client and then executed.
-With Apache Isis, though, the end-user merely invokes the `placeOrder(...)` action upon the domain object; the framework itself creates the xref:refguide:applib:index/services/command/Command.adoc[Command] as a side-effect of this.
+With Apache Causeway, though, the end-user merely invokes the `placeOrder(...)` action upon the domain object; the framework itself creates the xref:refguide:applib:index/services/command/Command.adoc[Command] as a side-effect of this.
== Event Sourcing
@@ -80,15 +80,15 @@ Note that the event might be dispatched and consumed in-process or alternatively
If the latter, then the subscriber will operate within a separate transaction, meaning the usual eventual consistency concerns and also compensating actions if a rollback is required.
CQRS/event sourcing advocates point out -- correctly -- that this is just how things are in the "real world" too.
-Comparing event sourcing with Apache Isis, in many ways they are orthogonal and so could in theory be combined.
+Comparing event sourcing with Apache Causeway, in many ways they are orthogonal and so could in theory be combined.
An event sourced entity "rehydrate" the domain object from persistence differently than an ORM, but once that is done, the domain object is in memory to be interacted with.
-To use Apache Isis with event sourcing would require disregarding the inbuild support for persistence though an ORM, but instead implement some other event sourced persistence mechanism to rehydrate the object.
-Because Apache Isis runs on top of Spring Boot, such an integration ought to be comparatively easy to do.
+To use Apache Causeway with event sourcing would require disregarding the inbuild support for persistence though an ORM, but instead implement some other event sourced persistence mechanism to rehydrate the object.
+Because Apache Causeway runs on top of Spring Boot, such an integration ought to be comparatively easy to do.
But in any case the roadmap is to support JPA as well as JDO, indeed as you read this the framework may already support this, and so in the future there are likely be additional SPIs to enable this trivially).
As with a CQRS architecture, Apache xref:userguide:fun:mixins.adoc[mixins] would be the obvious way to associate behaviour with an event sourced entity.
These mixins would most likely delegate to an event sourcing framework such as link:https://axoniq.io/[Axon] to do the work.
-Also, in Apache Isis every business action (and indeed, property and collection) emits domain events through the xref:refguide:applib:index/services/eventbus/EventBusService.adoc[EventBusService], and can optionally also be published through the xref:refguide:applib:index/services/publishing/spi/ExecutionSubscriber.adoc[ExecutionSubscriber].
+Also, in Apache Causeway every business action (and indeed, property and collection) emits domain events through the xref:refguide:applib:index/services/eventbus/EventBusService.adoc[EventBusService], and can optionally also be published through the xref:refguide:applib:index/services/publishing/spi/ExecutionSubscriber.adoc[ExecutionSubscriber].
These features could also have a role to play in an event sourced system.
diff --git a/antora/components/userguide/modules/fun/pages/concepts-patterns/architecture.adoc b/antora/components/userguide/modules/fun/pages/concepts-patterns/architecture.adoc
index 2c9197e2a5..b764f2a6d5 100644
--- a/antora/components/userguide/modules/fun/pages/concepts-patterns/architecture.adoc
+++ b/antora/components/userguide/modules/fun/pages/concepts-patterns/architecture.adoc
@@ -3,7 +3,7 @@
: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 [...]
:page-partial:
-This section describes some of the architectural patterns upon which Apache Isis builds.
+This section describes some of the architectural patterns upon which Apache Causeway builds.
[#hexagonal-architecture]
== Hexagonal Architecture
@@ -16,7 +16,7 @@ In particular, we have a layer dedicated to the domain model.
The code in this layer is unencumbered with the (mostly technical) responsibilities of the other layers and so can evolve to tackle complex domains as well as simple ones.
This is a well-established pattern, almost de-facto; there's very little debate that these responsibilities should be kept separate from each other.
-With Apache Isis the responsibility for presentation is a framework concern, the responsibility for the domain logic is implemented by your application code.
+With Apache Causeway the responsibility for presentation is a framework concern, the responsibility for the domain logic is implemented by your application code.
A few years ago Alistair Cockburn reworked the traditional layered architecture diagram and came up with the *_hexagonal architecture_* (also known as/very similar to the link:http://jeffreypalermo.com/blog/the-onion-architecture-part-1/[Onion] architecture):
@@ -30,20 +30,20 @@ Associated with each port can be an *_adapter_* (in fact, Cockburn's alternative
An adapter is a device (piece of software) that talks in the protocol (or _API_) of the port.
Each port could have several adapters.
-Apache Isis maps very nicely onto the hexagonal architecture.
-Apache Isis' viewers act as user-side adapters and use the Apache Isis metamodel API as a port into the domain objects.
+Apache Causeway maps very nicely onto the hexagonal architecture.
+Apache Causeway' viewers act as user-side adapters and use the Apache Causeway metamodel API as a port into the domain objects.
For the data side, we are mostly concerned with persisting domain objects to some sort of object store.
-Here Apache Isis delegates most of the heavy lifting to an ORM (DataNucleus or similar).
+Here Apache Causeway delegates most of the heavy lifting to an ORM (DataNucleus or similar).
[[aop]]
== Aspect Oriented
Although not a book about object modelling, Evans' "Domain Driven Design" does use object orientation as its primary modelling tool; while xref:userguide:fun:concepts-patterns.adoc#naked-objects-pattern[naked objects pattern] very much comes from an OO background (it even has 'object' in its name).
-It's certainly true that to develop an Apache Isis application you will need reasonably good object oriented modelling skills.
+It's certainly true that to develop an Apache Causeway application you will need reasonably good object oriented modelling skills.
But given that all the mainstream languages for developing business systems are object oriented (Java, C#, Ruby), that's not such a stretch.
-However, what you'll also discover is that in some ways an Apache Isis application is more aspect-oriented than it is object oriented.
+However, what you'll also discover is that in some ways an Apache Causeway application is more aspect-oriented than it is object oriented.
Given that aspect-orientation -- as a programming paradigm at least -- hasn't caught on, that statement probably needs unpacking a little.
=== AOP Concepts
@@ -59,15 +59,15 @@ This is actually then one bit of AOP that is quite mainstream; DI containers suc
Another aspect (so to speak!) of aspect-oriented programming has found its way into other programming languages, that of a mix-in or trait.
In languages such as Scala these mix-ins are specified statically as part of the inheritance hierarchy, whereas with AOP the binding of a trait to some other class/type is done without the class "knowing" that additional behaviour is being mixed-in to it.
-=== Realization within Apache Isis
+=== Realization within Apache Causeway
-What does all this have to do with Apache Isis?
+What does all this have to do with Apache Causeway?
Well, a different way to think of the naked objects pattern is that the visualization of a domain object within a UI is a cross-cutting concern.
-By following certain very standard programming conventions that represent the _Apache Isis Programming Model_ (POJOs plus annotations), the framework is able to build a metamodel and from this can render your domain objects in a standard generic fashion.
+By following certain very standard programming conventions that represent the _Apache Causeway Programming Model_ (POJOs plus annotations), the framework is able to build a metamodel and from this can render your domain objects in a standard generic fashion.
That's a rather more interesting cross-cutting concern than boring old logging!
-Apache Isis also draws heavily on the AOP concept of interceptors.
+Apache Causeway also draws heavily on the AOP concept of interceptors.
Whenever an object is rendered in the UI, it is filtered with respect to the user's permissions.
That is, if a user is not authorized to either view or perhaps modify an object, then this is applied transparently by the framework.
The xref:security:ROOT:about.adoc[SecMan extension] provides a rich user/role/permissions subdomain to use out of the box; but you can integrate with a different security mechanism if you have one already.
@@ -76,12 +76,12 @@ Another example of interceptors are the xref:userguide:commandlog:about.adoc[Com
The _Command Log_ module captures every user interaction that modifies the state of the system (the "cause" of a change) while the _Auditer_ module captures every change to every object (the "effect" of a change).
Again, this is all transparent to the user.
-Apache Isis also leverages the Spring framework's event bus.
+Apache Causeway also leverages the Spring framework's event bus.
A domain event is fired whenever an object is interacted with, and this allows any subscribers to influence the operation (or even veto it).
-This is a key mechanism in ensuring that Apache Isis applications are maintainable, by decoupling logic into separate modules.
+This is a key mechanism in ensuring that Apache Causeway applications are maintainable, by decoupling logic into separate modules.
But fundamentally its relying on this AOP concept of interceptors, with event subscribers in one module potentially influencing or responding to interaction triggered in another.
-Finally, Apache Isis also a feature that is akin to AOP traits.
+Finally, Apache Causeway also a feature that is akin to AOP traits.
A "contributed action" is one that is implemented by a mixin class but that appears to be a behaviour of rendered domain object.
Mixins can also contribute read-only properties or collections: effectively the result of running a query that returns a scalar or a vector.
In other words, we can dissociate behaviour from data.
@@ -90,8 +90,8 @@ That's not always the right thing to do of course.
In Richard Pawson's description of the xref:userguide:fun:concepts-patterns.adoc#naked-objects-pattern[naked objects pattern] he talks about "behaviourally rich" objects, in other words where the business functionality encapsulates the data.
But on the other hand sometimes the behaviour and data structures change at different rates.
The link:http://en.wikipedia.org/wiki/Single_responsibility_principle[single responsibility principle] says we should only lump code together that changes at the same rate.
-Apache Isis' support for contributions (not only contributed actions, but also contributed properties and contributed collections) enables this.
+Apache Causeway' support for contributions (not only contributed actions, but also contributed properties and contributed collections) enables this.
And again, to loop back to the topic of this section, it's an AOP concept that being implemented by the framework.
The nice thing about aspect orientation is that for the most part you can ignore these cross-cutting concerns and - at least initially - just focus on implementing your domain object.
-Later when your app starts to grow and you start to break it out into smaller modules, you can leverage Apache Isis' AOP support for xref:userguide:fun:overview.adoc#mixins[mixins] and interceptors (using the xref:refguide:applib:index/services/eventbus/EventBusService.adoc[event bus]) to ensure that your codebase remains maintainable.
+Later when your app starts to grow and you start to break it out into smaller modules, you can leverage Apache Causeway' AOP support for xref:userguide:fun:overview.adoc#mixins[mixins] and interceptors (using the xref:refguide:applib:index/services/eventbus/EventBusService.adoc[event bus]) to ensure that your codebase remains maintainable.
diff --git a/antora/components/userguide/modules/fun/pages/concepts-patterns/core-values.adoc b/antora/components/userguide/modules/fun/pages/concepts-patterns/core-values.adoc
index 329dcfee0b..9494843909 100644
--- a/antora/components/userguide/modules/fun/pages/concepts-patterns/core-values.adoc
+++ b/antora/components/userguide/modules/fun/pages/concepts-patterns/core-values.adoc
@@ -3,11 +3,11 @@
: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 [...]
:page-partial:
-This section describes the core values that the the Apache Isis framework tries to uphold.
+This section describes the core values that the the Apache Causeway framework tries to uphold.
== Aligned with the Business
-Apache Isis is primarily aimed at custom-built "enterprise" applications, with a UI provided by the xref:vw:ROOT:about.adoc[Web UI (Wicket viewer)] is intended to be usable by domain experts, typically end-users within the organization.
+Apache Causeway is primarily aimed at custom-built "enterprise" applications, with a UI provided by the xref:vw:ROOT:about.adoc[Web UI (Wicket viewer)] is intended to be usable by domain experts, typically end-users within the organization.
But why should an organisation build software, when it could just buy it?
@@ -61,7 +61,7 @@ What this means in turn is that the application needs to be maintainable, so tha
That's a tall order for any application to meet, and realistically it _can_ only be met if the application is modular.
Any application that lacks a coherent internal structure will ultimately degrade into an unmaintable "big ball of mud", and the development team's velocity/capacity to make changes will reduce accordingly.
-Apache Isis' architecture allows the internal structure to be maintained in two distinct ways.
+Apache Causeway' architecture allows the internal structure to be maintained in two distinct ways.
* first, the naked objects pattern acts as a "firewall", ensuring that any business logic in the domain layer doesn't leak out into the presentation layer (it can't, because the developer doesn't write any controllers/views).
@@ -95,7 +95,7 @@ For further discussion on modular monoliths, check out Dan Haywood's article on
== Easing the road to DDD
The case for xref:concepts-patterns.adoc#domain-driven-design[domain driven design] might be compelling, but that doesn't necessarily make it easy to do.
-Let's take a look at some of the challenges that _DDD_ throws up and see how Apache Isis (and its implementation of the naked objects pattern) helps address them.
+Let's take a look at some of the challenges that _DDD_ throws up and see how Apache Causeway (and its implementation of the naked objects pattern) helps address them.
=== DDD takes a conscious effort
@@ -110,8 +110,8 @@ It takes a _conscious_ effort by the entire team to develop the ubiquitous langu
Everyone in the team must challenge the use of new or unfamiliar terms, must clarify concepts when used in a new context, and in general must be on the lookout for sloppy thinking.
This takes willingness on the part of all involved, not to mention some practice.
-With Apache Isis, though, the ubiquitous language evolves with scarcely any effort at all.
-For the business experts, the Apache Isis viewers show the domain concepts they identify and the relationships between those concepts in a straightforward fashion.
+With Apache Causeway, though, the ubiquitous language evolves with scarcely any effort at all.
+For the business experts, the Apache Causeway viewers show the domain concepts they identify and the relationships between those concepts in a straightforward fashion.
Meanwhile, the developers can devote themselves to encoding those domain concepts directly as domain classes.
There's no technology to get distracted by; there is literally nothing else for the developers to be working on.
@@ -125,7 +125,7 @@ If we fail to do this, then we open up the communication divide, and our ubiquit
There is literally no point having a domain model that cannot be represented in code.
We cannot invent our ubiquitous language in a vacuum, and the developers must ensure that the model remains grounded in the doable.
-In Apache Isis, we have a very pure one-to-one correspondence between the domain concepts and its implementation.
+In Apache Causeway, we have a very pure one-to-one correspondence between the domain concepts and its implementation.
Domain concepts are represented as classes and interfaces, easily demonstrated back to the business.
If the model is clumsy, then the application will be clumsy too, and so the team can work together to find a better implementable model.
@@ -139,10 +139,10 @@ Or we could generate a PDF document from Javadoc comments, but comments aren't c
Anyway, even if we do create such a document, not everyone will read it.
A better way to represent the model is to show it in action as a working prototype.
-As we show with the xref:docs:starters:helloworld.adoc[starter apps], Apache Isis enables this with ease.
+As we show with the xref:docs:starters:helloworld.adoc[starter apps], Apache Causeway enables this with ease.
Such prototypes bring the domain model to life, engaging the audience in a way that a piece of paper never can.
-Moreover, with Apache Isis prototypes, the domain model will come shining through.
+Moreover, with Apache Causeway prototypes, the domain model will come shining through.
If there are mistakes or misunderstandings in the domain model (inevitable when building any complex system), they will be obvious to all.
=== Architecture must be robust
@@ -159,13 +159,13 @@ It takes real skill to ensure the correct separation of concerns between these l
Even with the best intentions, it's all too easy for custom-written layers to blur the boundaries and put (for example) validation in the user interface layer when it should belong to the domain layer.
At the other extreme, it's quite possible for custom layers to distort or completely subvert the underlying domain model.
-Because of Apache Isis' generic __OOUI__s, there's no need to write the other layers of the architecture.
+Because of Apache Causeway' generic __OOUI__s, there's no need to write the other layers of the architecture.
Of course, this reduces the development cost.
But more than that, there will be no leakage of concerns outside the domain model.
All the validation logic *must* be in the domain model because there is nowhere else to put it.
-Moreover, although Apache Isis does provide a complete runtime framework, there is no direct coupling of your domain model to the framework.
-That means it is very possible to take your domain model prototyped in Apache Isis and then deploy it on some other _J(2)EE_ architecture, with a custom _UI_ if you want.
+Moreover, although Apache Causeway does provide a complete runtime framework, there is no direct coupling of your domain model to the framework.
+That means it is very possible to take your domain model prototyped in Apache Causeway and then deploy it on some other _J(2)EE_ architecture, with a custom _UI_ if you want.
This is discussed later on, in xref:concepts-patterns.adoc#deployment-options[deployment options].
=== Extending the reach of DDD
@@ -177,10 +177,10 @@ The trouble is that we immediately have to make a choice: is the domain complex
This goes back to the previous point, building and maintaining a layered architecture.
It doesn't seem cost effective to go to all the effort of a DDD approach if the underlying domain model is simple.
-However, with Apache Isis, we don't write these other layers, so we don't have to make a call on how complex our domain is.
+However, with Apache Causeway, we don't write these other layers, so we don't have to make a call on how complex our domain is.
We can start working solely on our domain, even if we suspect it will be simple.
If it is indeed a simple domain, then there's no hardship, but if unexpected subtleties arise, then we're in a good position to handle them.
-If you're just starting out writing domain-driven applications, then Apache Isis should significantly ease your journey into applying _DDD_.
+If you're just starting out writing domain-driven applications, then Apache Causeway should significantly ease your journey into applying _DDD_.
And if you _have_ used _DDD_ for a while, then you should find the framework a very useful new tool in your arsenal.
diff --git a/antora/components/userguide/modules/fun/pages/concepts-patterns/deployment-options.adoc b/antora/components/userguide/modules/fun/pages/concepts-patterns/deployment-options.adoc
index e9c516107b..368e67afbd 100644
--- a/antora/components/userguide/modules/fun/pages/concepts-patterns/deployment-options.adoc
+++ b/antora/components/userguide/modules/fun/pages/concepts-patterns/deployment-options.adoc
@@ -6,10 +6,10 @@
-Apache Isis is a mature platform suitable for production deployment, with its "sweet spot" being line-of-business enterprise applications.
+Apache Causeway is a mature platform suitable for production deployment, with its "sweet spot" being line-of-business enterprise applications.
So if you're looking to develop that sort of application, we certainly hope you'll seriously evaluate it.
-But there are other ways that you can make Apache Isis work for you; in this section we explore a few of them.
+But there are other ways that you can make Apache Causeway work for you; in this section we explore a few of them.
include::partial$_deployment-options.adoc[]
diff --git a/antora/components/userguide/modules/fun/pages/concepts-patterns/metamodel.adoc b/antora/components/userguide/modules/fun/pages/concepts-patterns/metamodel.adoc
index 0b4a9c6011..bb9e1f2c5a 100644
--- a/antora/components/userguide/modules/fun/pages/concepts-patterns/metamodel.adoc
+++ b/antora/components/userguide/modules/fun/pages/concepts-patterns/metamodel.adoc
@@ -5,21 +5,21 @@
:page-partial:
-At its core, Apache Isis is a metamodel that is built at runtime from the domain classes (eg `Customer.java`), along with optional supporting metadata (eg `Customer.layout.xml`).
+At its core, Apache Causeway is a metamodel that is built at runtime from the domain classes (eg `Customer.java`), along with optional supporting metadata (eg `Customer.layout.xml`).
The contents of this metamodel are the entities and supporting services, as well the members of those classes.
These are all meta-annotated with link:https://docs.spring.io/spring-framework/docs/current/javadoc-api/org/springframework/stereotype/Component.html[@Component] and are either registered explicitly (framework services) or dynamically discovered (entities and user-defined services) by Spring Boot on the classpath via link:https://docs.spring.io/spring/docs/current/javadoc-api/org/springframework/context/annotation/ComponentScan.html[@ComponentScan].
The detail of the metamodel is generally explicit, usually represented by Java annotations such as `@Title` or `@Action`, though this is configurable.
-Notably the metamodel is xref:userguide:btb:programming-model.adoc[extensible]; it is possible to teach Apache Isis new programming conventions/rules (and conversely to remove those that are built in).
+Notably the metamodel is xref:userguide:btb:programming-model.adoc[extensible]; it is possible to teach Apache Causeway new programming conventions/rules (and conversely to remove those that are built in).
-Most of the annotations recognized by the framework are defined by the Apache Isis framework itself.
+Most of the annotations recognized by the framework are defined by the Apache Causeway framework itself.
For example the `@Title` annotation -- which identifies how the framework should derive a human-readable label for each rendered domain object -- is part of the `org.apache.causeway.applib.annotations` package.
However the framework also recognizes certain other JEE annotations such as `@javax.inject.Inject` (used for dependency injection).
The framework integrates an ORM for persistence, specifically DataNucleus and the JDO API and since version 2.0.0, JPA (Eclipselink) is supported as well.
Both JDO and JPA can map to both relational databases and also to various NoSQL objectstores such as MongoDB or Neo4J.
-Apache Isis recognizes a number of these persistence-specific annotations, for example `@javax.jdo.annotations.Column(allowsNull=...)`.
+Apache Causeway recognizes a number of these persistence-specific annotations, for example `@javax.jdo.annotations.Column(allowsNull=...)`.
In addition, the framework builds up the metamodel for each domain object using xref:userguide:fun:ui.adoc#object-layout[layout hints], such as `Customer.layout.xml`.
These provide metadata such as grouping elements of the UI together, using multi-column layouts, and so on.
diff --git a/antora/components/userguide/modules/fun/pages/concepts-patterns/naked-objects-pattern.adoc b/antora/components/userguide/modules/fun/pages/concepts-patterns/naked-objects-pattern.adoc
index a96d372224..568d077f0c 100644
--- a/antora/components/userguide/modules/fun/pages/concepts-patterns/naked-objects-pattern.adoc
+++ b/antora/components/userguide/modules/fun/pages/concepts-patterns/naked-objects-pattern.adoc
@@ -4,7 +4,7 @@
: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 [...]
:page-partial:
-Apache Isis implements the naked objects pattern, originally formulated by Richard Pawson.
+Apache Causeway implements the naked objects pattern, originally formulated by Richard Pawson.
So who better than Richard to explain the origination of the idea:
__________________________
@@ -32,7 +32,7 @@ Thus was born the idea of Naked Objects.
__________________________
You can learn much more about the pattern in the book, link:http://www.amazon.com/exec/obidos/ISBN=0470844205/[Naked Objects], also freely available to link:http://www.nakedobjects.org/book/[read online].
-Richard co-wrote the book with one of Apache Isis' committers, Robert Matthews, who was in turn the author of the Naked Objects Framework for Java (the original codebase of Apache Isis).
+Richard co-wrote the book with one of Apache Causeway' committers, Robert Matthews, who was in turn the author of the Naked Objects Framework for Java (the original codebase of Apache Causeway).
You might also want to read Richard's link:{attachmentsdir}/core-concepts/Pawson-Naked-Objects-thesis.pdf[PhD on the subject].
diff --git a/antora/components/userguide/modules/fun/pages/domain-entities-and-services/crud.adoc b/antora/components/userguide/modules/fun/pages/domain-entities-and-services/crud.adoc
index e315063d05..6b43ef89bd 100644
--- a/antora/components/userguide/modules/fun/pages/domain-entities-and-services/crud.adoc
+++ b/antora/components/userguide/modules/fun/pages/domain-entities-and-services/crud.adoc
@@ -281,7 +281,7 @@ Rather, the ORM (DataNucleus) automatically keeps track of the state of each obj
That said, it is possible to "flush" pending changes:
-* xref:refguide:applib:index/services/xactn/TransactionService.adoc[TransactionService] acts at the Apache Isis layer, and flushes any pending object persistence or object deletions
+* xref:refguide:applib:index/services/xactn/TransactionService.adoc[TransactionService] acts at the Apache Causeway layer, and flushes any pending object persistence or object deletions
* (if using xref:pjdo:ROOT:about.adoc[JDO/DataNucleus]), the xref:refguide:persistence:index/jdo/applib/services/JdoSupportService.adoc[JdoSupportService] domain service can be used reach down to the underlying JDO API, and perform a flush of pending object updates also.
diff --git a/antora/components/userguide/modules/fun/pages/domain-entities-and-services/domain-entities.adoc b/antora/components/userguide/modules/fun/pages/domain-entities-and-services/domain-entities.adoc
index dfdcea9b4b..a11a8adfee 100644
--- a/antora/components/userguide/modules/fun/pages/domain-entities-and-services/domain-entities.adoc
+++ b/antora/components/userguide/modules/fun/pages/domain-entities-and-services/domain-entities.adoc
@@ -17,7 +17,7 @@ In addition they will also require ORM metadata.
TIP: It is also possible to specify ORM metadata using `.xml` files.
-In this section we discuss the mechanics of writing domain objects that comply with Apache Isis' programming model.
+In this section we discuss the mechanics of writing domain objects that comply with Apache Causeway' programming model.
== Entities (JPA)
@@ -80,7 +80,7 @@ A common strategy is to allow the database to assign the id, for example using a
<.> The `@Version` annotation is useful for optimistic locking; the strategy indicates what to store in the `version` column.
-<.> The `@DomainObject` annotation identifies the domain object to Apache Isis (not DataNucleus).
+<.> The `@DomainObject` annotation identifies the domain object to Apache Causeway (not DataNucleus).
It isn't necessary to include this annotation -- at least, not for entities -- but it is nevertheless recommended.
In particular, its strongly recommended that the `logicalTypeName` (which acts like an alias to the concrete domain class) is specified; note that it corresponds to the schema/table for DataNucleus' `@PersistenceCapable` annotation.
diff --git a/antora/components/userguide/modules/fun/pages/domain-entities-and-services/domain-services.adoc b/antora/components/userguide/modules/fun/pages/domain-entities-and-services/domain-services.adoc
index b4a1da8ce2..bed22a62ba 100644
--- a/antora/components/userguide/modules/fun/pages/domain-entities-and-services/domain-services.adoc
+++ b/antora/components/userguide/modules/fun/pages/domain-entities-and-services/domain-services.adoc
@@ -14,7 +14,7 @@ Domain services that are visible in the UI or REST API are annotated with xref:r
xref:https://docs.spring.io/spring/docs/current/javadoc-api/org/springframework/stereotype/Service.html[@Service]
orxref:https://docs.spring.io/spring/docs/current/javadoc-api/org/springframework/stereotype/Repository.html[@Repository].
-Apache Isis runs on top of Spring Boot, and relies on Spring Boot for dependency injection using `@javax.inject.Inject`.
+Apache Causeway runs on top of Spring Boot, and relies on Spring Boot for dependency injection using `@javax.inject.Inject`.
The `@javax.annotation.Priority` annotation is used to prioritize multiple service implementations, effectively allowing any framework-provided domain service to be substituted out by a user-defined one encountered with an earlier precedence (= higher priority) if required.
This section looks at the programming model for writing your own domain services.
@@ -22,12 +22,12 @@ This section looks at the programming model for writing your own domain services
== Nature of Service
-Apache Isis uses Spring Boot to instantiate and manage the dependency injection of domain services.
+Apache Causeway uses Spring Boot to instantiate and manage the dependency injection of domain services.
The vast majority of these are singleton (application) scoped; a smaller number are request scoped (using the xref:refguide:applib:index/annotation/InteractionScope.adoc[@IsisSessionScope] annotation).
Accordingly, all domain services are annotated or meta-annotated using Spring's link:https://docs.spring.io/spring-framework/docs/current/javadoc-api/org/springframework/stereotype/Component.html[@Component] annotation.
-For domain services to be visible in the Apache Isis UI, they must be annotated with xref:refguide:applib:index/annotation/DomainService.adoc[@DomainService].
+For domain services to be visible in the Apache Causeway UI, they must be annotated with xref:refguide:applib:index/annotation/DomainService.adoc[@DomainService].
Its xref:refguide:applib:index/annotation/DomainService.adoc#nature[#nature()] attribute is either:
* `VIEW` (the default if not specified)
@@ -197,7 +197,7 @@ Sometimes though a service's lifetime is applicable only to a single (http) requ
The framework has a number of such services, including a xref:refguide:applib:index/services/scratchpad/Scratchpad.adoc[Scratchpad] service (to share adhoc data between methods), and xref:refguide:applib:index/services/queryresultscache/QueryResultsCache.adoc[QueryResultsCache], which as its name suggests will cache query results.
Such services _do_ hold state, but that state is scoped per (possibly concurrent) request and should be removed afterwards.
-The requirement for request-scoped services is supported using Apache Isis' own xref:refguide:applib:index/annotation/InteractionScope.adoc[@IsisSessionScope] annotation (named because a short-lived `IsisSession` is created for each request).
+The requirement for request-scoped services is supported using Apache Causeway' own xref:refguide:applib:index/annotation/InteractionScope.adoc[@IsisSessionScope] annotation (named because a short-lived `IsisSession` is created for each request).
This is used by the framework services and can also be used for user-defined services.
For example:
@@ -237,7 +237,7 @@ public class SomeClient {
Spring provides numerous mechanisms to configure domain services, both in terms of binding or passing in the configuration property to the service, and in terms of setting the value within some sort of configuration file.
-The mechanism prefered by Apache Isis itself, and which you are free to use for your own services, is the type-safe link:https://docs.spring.io/spring-boot/docs/current/api/org/springframework/boot/context/properties/ConfigurationProperties.html[ConfigurationProperties], whereby the configuration properties are expressed in a series of nested static classes.
+The mechanism prefered by Apache Causeway itself, and which you are free to use for your own services, is the type-safe link:https://docs.spring.io/spring-boot/docs/current/api/org/springframework/boot/context/properties/ConfigurationProperties.html[ConfigurationProperties], whereby the configuration properties are expressed in a series of nested static classes.
The xref:docs:starters:simpleapp.adoc[simpleapp starter app] includes an example:
diff --git a/antora/components/userguide/modules/fun/pages/domain-entities-and-services/inject-services.adoc b/antora/components/userguide/modules/fun/pages/domain-entities-and-services/inject-services.adoc
index e7d2f225b2..0bb400860c 100644
--- a/antora/components/userguide/modules/fun/pages/domain-entities-and-services/inject-services.adoc
+++ b/antora/components/userguide/modules/fun/pages/domain-entities-and-services/inject-services.adoc
@@ -5,7 +5,7 @@
:page-partial:
-Apache Isis runs on top of Spring Boot, and uses Spring Boot for dependency injection, both the application's own domain services and also the many additional services defined by the framework (such as xref:refguide:applib:index/services/repository/RepositoryService.adoc[RepositoryService]).
+Apache Causeway runs on top of Spring Boot, and uses Spring Boot for dependency injection, both the application's own domain services and also the many additional services defined by the framework (such as xref:refguide:applib:index/services/repository/RepositoryService.adoc[RepositoryService]).
Since this is a core capability of Spring, it's worth checking out Spring's link:https://docs.spring.io/spring/docs/current/spring-framework-reference/core.html#beans-factory-collaborators[documentation] on the topic.
@@ -18,7 +18,7 @@ It is also possible to use Spring's own link:https://docs.spring.io/spring-frame
Since the two annotations are effectively equivalent, we recommend using the JEE standard.
====
-However, not only does Apache Isis use Spring to autowire domain services into other services, the framework _also_ ensures that services are injected into any domain object (eg xref:overview.adoc#domain-entities[entity], xref:overview.adoc#view-models[view model], xref:overview.adoc#mixins[mixins], xref:testing:fixtures:about.adoc#fixture-scripts[fixture script], xref:refguide:applib:index/spec/Specification.adoc[specification] etc).
+However, not only does Apache Causeway use Spring to autowire domain services into other services, the framework _also_ ensures that services are injected into any domain object (eg xref:overview.adoc#domain-entities[entity], xref:overview.adoc#view-models[view model], xref:overview.adoc#mixins[mixins], xref:testing:fixtures:about.adoc#fixture-scripts[fixture script], xref:refguide:applib:index/spec/Specification.adoc[specification] etc).
This is key enabler to place functionality in the "right place", eg in a domain entity/view model itself, or in a mixin.
@@ -145,7 +145,7 @@ Using default visibility here still allows the field to be mocked out within uni
If there is more than one implementation of the service, then a specific implementation can be requested using either Spring's link:https://docs.spring.io/spring-framework/docs/current/javadoc-api/org/springframework/context/annotation/Primary.html[@Primary] annotation (further discussion link:https://docs.spring.io/spring/docs/current/spring-framework-reference/core.html#beans-autowired-annotation-primary[here]) or Spring's link:https://docs.spring.io/spring-framework/docs/current/javad [...]
-All of the domain services provided by Apache Isis' are annotated with `@Qualifier` to enable this.
+All of the domain services provided by Apache Causeway' are annotated with `@Qualifier` to enable this.
== Injecting Lists of Services
diff --git a/antora/components/userguide/modules/fun/pages/meta-annotations.adoc b/antora/components/userguide/modules/fun/pages/meta-annotations.adoc
index 85de5b874d..b0da2b1dd9 100644
--- a/antora/components/userguide/modules/fun/pages/meta-annotations.adoc
+++ b/antora/components/userguide/modules/fun/pages/meta-annotations.adoc
@@ -4,9 +4,9 @@
:page-partial:
-Apache Isis supports the use of meta-annotations, as does Spring Boot and the ORM (xref:pjdo:ROOT:about.adoc[JDO/DataNucleus] from DN 5.x, xref:pjpa:ROOT:about.adoc[JPA/EclipseLink] from Eclipse 2.7 supporting JPA 2.2).
+Apache Causeway supports the use of meta-annotations, as does Spring Boot and the ORM (xref:pjdo:ROOT:about.adoc[JDO/DataNucleus] from DN 5.x, xref:pjpa:ROOT:about.adoc[JPA/EclipseLink] from Eclipse 2.7 supporting JPA 2.2).
-This allows you to define custom annotations that are more descriptive of your domain model, and meta-annotate your custom annotations with those of Apache Isis, Spring or the ORM.
+This allows you to define custom annotations that are more descriptive of your domain model, and meta-annotate your custom annotations with those of Apache Causeway, Spring or the ORM.
In your domain model, you can just use the custom annotation.
The most common use case is to define meta-annotations for scalar types that are used in properties or parameters.
diff --git a/antora/components/userguide/modules/fun/pages/modules.adoc b/antora/components/userguide/modules/fun/pages/modules.adoc
index a9975c7f73..d2f1ad4272 100644
--- a/antora/components/userguide/modules/fun/pages/modules.adoc
+++ b/antora/components/userguide/modules/fun/pages/modules.adoc
@@ -4,7 +4,7 @@
: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 [...]
:page-partial:
-In Apache Isis we use Spring link:https://docs.spring.io/spring-framework/docs/current/javadoc-api/org/springframework/context/annotation/Configuration.html[@Configuration]s to define a module, consisting of a set of domain services and domain objects (entities, view models and mixins).
+In Apache Causeway we use Spring link:https://docs.spring.io/spring-framework/docs/current/javadoc-api/org/springframework/context/annotation/Configuration.html[@Configuration]s to define a module, consisting of a set of domain services and domain objects (entities, view models and mixins).
Spring's link:https://docs.spring.io/spring-framework/docs/current/javadoc-api/org/springframework/context/annotation/Import.html[@Import] is used to express a dependency between each "configuration" module.
TIP: See Spring documentation on link:https://docs.spring.io/spring-framework/docs/current/spring-framework-reference/core.html#beans-annotation-config[annotation-based container configuration], link:https://docs.spring.io/spring-framework/docs/current/spring-framework-reference/core.html#beans-classpath-scanning[classpath scanning] and link:https://docs.spring.io/spring-framework/docs/current/spring-framework-reference/core.html#beans-java[java-based configuration] for much more on this topic.
@@ -101,7 +101,7 @@ public class CustomerModule {}
<.> dependency on the Excel module (more precisely, its "applib")
<.> scan for domain services and objects etc under this package (eg a `Customer` entity or a `CustomerRepository` domain service).
-Since `@Configuration` and `@ComponentScan` often appear together, Apache Isis provides a convenience `@Module` annotation, which is meta-annotated with both.
+Since `@Configuration` and `@ComponentScan` often appear together, Apache Causeway provides a convenience `@Module` annotation, which is meta-annotated with both.
The above example could therefore be rewritten as:
[source,java]
diff --git a/antora/components/userguide/modules/fun/pages/object-members/actions.adoc b/antora/components/userguide/modules/fun/pages/object-members/actions.adoc
index 3d4d17cc95..75cbfbdbf3 100644
--- a/antora/components/userguide/modules/fun/pages/object-members/actions.adoc
+++ b/antora/components/userguide/modules/fun/pages/object-members/actions.adoc
@@ -15,7 +15,7 @@ There are three operations here: set the end date of the original lease term, cr
Instead, all of these operations can be combined into a single action, "renew".
Through such means the xref:concepts-patterns.adoc#ubiquitous-language[ubiquitous language] grows.
-TIP: This is the reason why Apache Isis' default is xref:object-members.adoc#editable-properties[non-editable properties]: to encourage this sort of "knowledge crunching".
+TIP: This is the reason why Apache Causeway' default is xref:object-members.adoc#editable-properties[non-editable properties]: to encourage this sort of "knowledge crunching".
You can find further discussion on when and why you should write actions xref:overview.adoc#actions[earlier].
diff --git a/antora/components/userguide/modules/fun/pages/object-members/collections.adoc b/antora/components/userguide/modules/fun/pages/object-members/collections.adoc
index 390245614a..232806fffb 100644
--- a/antora/components/userguide/modules/fun/pages/object-members/collections.adoc
+++ b/antora/components/userguide/modules/fun/pages/object-members/collections.adoc
@@ -15,7 +15,7 @@ Formally speaking, a collection is simply a regular JavaBean getter, returning a
Most collections (those that are modifiable) will also have a setter and, if persisted, a backing instance field.
And collections properties will also have a number of annotations:
-* Apache Isis defines its own xref xref:refguide:applib:index/annotation/Collection.adoc[@Collection] annotation for capturing domain semantics.
+* Apache Causeway defines its own xref xref:refguide:applib:index/annotation/Collection.adoc[@Collection] annotation for capturing domain semantics.
It also provides a xref:refguide:applib:index/annotation/CollectionLayout.adoc[@CollectionLayout] for UI hints (though the information in this annotation may instead be provided by a supplementary xref:userguide:fun:ui.adoc#object-layout[.layout.xml] file)
* the collections of domain entities are often annotated with ORM annotation(s).
@@ -24,7 +24,7 @@ Other annotations can be used to specify if the association is bidirectional, an
* for the collections of view models, then JAXB annotations such as link:https://docs.oracle.com/javase/7/docs/api/javax/xml/bind/annotation/XmlElementWrapper.html[@javax.xml.bind.annotation.XmlElementWrapper] and link:https://docs.oracle.com/javase/7/docs/api/javax/xml/bind/annotation/XmlElement.html[@javax.xml.bind.annotation.XmlElement] will be present
-Apache Isis may recognise some of these annotations from the persistence layer infers some domain semantics from them.
+Apache Causeway may recognise some of these annotations from the persistence layer infers some domain semantics from them.
Unlike xref:userguide:fun:object-members.adoc#properties[properties], the framework does not allow collections to be "edited".
Instead, xref:userguide:fun:object-members.adoc#actions[action]s can be written that will modify the contents of the collection as a side-effect.
@@ -72,7 +72,7 @@ public class ParentObject
----
<.> indicates a bidirectional association; the foreign key pointing back to the `Parent` will be in the table for `ChildObject`
<.> disables cascade delete
-<.> (not actually required in this case, because no attributes are set, but acts as a useful reminder that this collection will be rendered in the UI by Apache Isis)
+<.> (not actually required in this case, because no attributes are set, but acts as a useful reminder that this collection will be rendered in the UI by Apache Causeway)
<.> uses a `SortedSet` (as opposed to some other collection type; discussion below)
while in the child object you will have:
@@ -101,18 +101,18 @@ JDO/Datanucleus does support the mapping of these other types, but RDBMS are set
== Maps
-While ORMs support `java.util.Map` as a collection type, maps are not supported by Apache Isis.
+While ORMs support `java.util.Map` as a collection type, maps are not supported by Apache Causeway.
-If you do wish to use this collection type, then annotate the getter with xref:refguide:applib:index/annotation/Programmatic.adoc[@Programmatic] so that it is ignored by the Apache Isis framework.
+If you do wish to use this collection type, then annotate the getter with xref:refguide:applib:index/annotation/Programmatic.adoc[@Programmatic] so that it is ignored by the Apache Causeway framework.
== Value vs Reference Types
-While ORMs support collections/arrays of value types, such collections are not supported by Apache Isis.
-Apache Isis can (currently) only provide a UI for collections of references.
+While ORMs support collections/arrays of value types, such collections are not supported by Apache Causeway.
+Apache Causeway can (currently) only provide a UI for collections of references.
-If you do wish to use collections of this type, then annotate the getter with xref:refguide:applib:index/annotation/Programmatic.adoc[@Programmatic] so that it is ignored by the Apache Isis framework.
+If you do wish to use collections of this type, then annotate the getter with xref:refguide:applib:index/annotation/Programmatic.adoc[@Programmatic] so that it is ignored by the Apache Causeway framework.
-As a workaround, if you want to visualize an array of value types in Apache Isis, then one option is to wrap the value in a view model, as explained xref:userguide:btb:hints-and-tips/simulating-collections-of-values.adoc[here].
+As a workaround, if you want to visualize an array of value types in Apache Causeway, then one option is to wrap the value in a view model, as explained xref:userguide:btb:hints-and-tips/simulating-collections-of-values.adoc[here].
== Derived Collections
diff --git a/antora/components/userguide/modules/fun/pages/object-members/properties.adoc b/antora/components/userguide/modules/fun/pages/object-members/properties.adoc
index 5064620892..6140e5f9e6 100644
--- a/antora/components/userguide/modules/fun/pages/object-members/properties.adoc
+++ b/antora/components/userguide/modules/fun/pages/object-members/properties.adoc
@@ -15,7 +15,7 @@ Formally speaking, a property is simply a regular JavaBean getter, returning a s
Most properties (those that are editable/modifiable) will also have a setter and, if persisted, a backing instance field.
And most properties will also have a number of annotations:
-* Apache Isis defines its own xref:refguide:applib:index/annotation/Property.adoc[@Property] annotation for capturing domain semantics.
+* Apache Causeway defines its own xref:refguide:applib:index/annotation/Property.adoc[@Property] annotation for capturing domain semantics.
It also provides a xref:refguide:applib:index/annotation/PropertyLayout.adoc[@PropertyLayout] for UI hints (though the information in this annotation may instead be provided by a supplementary xref:userguide:fun:ui.adoc#object-layout[.layout.xml] file)
* the properties of domain entities are usually also annotated with an ORM annotation.
@@ -26,7 +26,7 @@ It's also possible (using annotations) to define a link table to hold foreign ke
* for the properties of view models, then JAXB annotations such as link:https://docs.oracle.com/javase/8/docs/api/javax/xml/bind/annotation/XmlElement.html[@XmlElement] may be present
-Apache Isis recognises some of these annotations from the persistence layer and infers some domain semantics from them (for example, the maximum allowable length of a string property).
+Apache Causeway recognises some of these annotations from the persistence layer and infers some domain semantics from them (for example, the maximum allowable length of a string property).
Since writing getter and setter methods adds quite a bit of boilerplate, it's common to use link:https://projectlombok.org/[Project Lombok] to code generate these methods at compile time (using Java's annotation processor) simply by adding the `@lombok.Getter` and `@lombok.Setter` annotations to the field.
The xref:docs:starters:simpleapp.adoc[SimpleApp] starter app uses this approach.
@@ -87,11 +87,11 @@ For further details on mapping associations using xref:pjdo:ROOT:about.adoc[JDO/
(For domain entities) JDO/DataNucleus' default is that a property is assumed to be mandatory if it is a primitive type (eg `int`, `boolean`), but optional if a reference type (eg `String`, `BigDecimal` etc).
To override optionality in JDO/DataNucleus the `@Column(allowsNull="...")` annotations is used.
-Apache Isis on the other hand assumes that all properties (and action parameters, for that matter) are mandatory, not optional.
-These defaults can also be overridden using Apache Isis' own annotations, specifically `@Property(optionality=...)`, or (because it's much less verbose) using `@javax.annotation.Nullable`.
+Apache Causeway on the other hand assumes that all properties (and action parameters, for that matter) are mandatory, not optional.
+These defaults can also be overridden using Apache Causeway' own annotations, specifically `@Property(optionality=...)`, or (because it's much less verbose) using `@javax.annotation.Nullable`.
These different defaults can lead to incompatibilities between the two frameworks.
-To counteract that, Apache Isis also recognizes and honours JDO's `@Column(allowsNull=...)`.
+To counteract that, Apache Causeway also recognizes and honours JDO's `@Column(allowsNull=...)`.
For example, you can write:
@@ -121,12 +121,12 @@ import lombok.Setter;
private LocalDate date;
----
-The framework will search for any incompatibilities in optionality (whether specified explicitly or defaulted implicitly) between Apache Isis' defaults and DataNucleus, and will refuse to boot if any are found.
+The framework will search for any incompatibilities in optionality (whether specified explicitly or defaulted implicitly) between Apache Causeway' defaults and DataNucleus, and will refuse to boot if any are found.
[#editable-properties]
== Editable Properties
-Apache Isis provides the capability to allow individual properties to be modified.
+Apache Causeway provides the capability to allow individual properties to be modified.
This is specified using the `@Property(editing=...)` attribute.
For example:
@@ -186,19 +186,19 @@ AddressService addressService; // <.>
----
<.> the representation of the address, in human readable form, eg "10 Downing Street, London, UK"
<.> the lat/long representation of the address, eg "51.503363;-0.127625".
-Excluded from the Apache Isis metamodel.
+Excluded from the Apache Causeway metamodel.
<.> an injected service that can convert to/from address and latLong.
== Ignoring Properties
-By default Apache Isis will automatically render all properties in the xref:vw:ROOT:about.adoc[Wicket UI] or in the xref:vro:ROOT:about.adoc[REST API].
-To get Apache Isis to ignore a property (exclude it from its metamodel), annotate the getter using xref:refguide:applib:index/annotation/Programmatic.adoc[@Programmatic].
+By default Apache Causeway will automatically render all properties in the xref:vw:ROOT:about.adoc[Wicket UI] or in the xref:vro:ROOT:about.adoc[REST API].
+To get Apache Causeway to ignore a property (exclude it from its metamodel), annotate the getter using xref:refguide:applib:index/annotation/Programmatic.adoc[@Programmatic].
Similarly, for the JDO/DataNucleus ORM, ignore a property using the `@javax.jdo.annotations.NotPersistent` annotation.
-This is independent of Apache Isis; in other words that property will still be rendered in the UI (unless also annotated with `@Programmatic`).
+This is independent of Apache Causeway; in other words that property will still be rendered in the UI (unless also annotated with `@Programmatic`).
For view models, you can tell JAXB to ignore a property using the `@javax.xml.bind.annotation.XmlTransient` annotation.
-Again, this is independent of Apache Isis.
+Again, this is independent of Apache Causeway.
You can also suppress a property from the UI using xref:refguide:applib:index/annotation/Property.adoc#hidden[@Property#hidden()] or indeed xref:refguide:applib:index/annotation/PropertyLayout.adoc#hidden[@PropertyLayout#hidden()].
However, this doesn't exclude the property from the metamodel.
@@ -236,11 +236,11 @@ import lombok.Setter;
private String firstName
----
-This is a good example of a case where Apache Isis infers domain semantics from the JDO annotation.
+This is a good example of a case where Apache Causeway infers domain semantics from the JDO annotation.
=== JODA Dates
-Apache Isis' bundles DataNucleus' http://www.datanucleus.org/documentation/products/plugins.html[built-in support] for Joda `LocalDate` and `LocalDateTime` datatypes, meaning that entity properties of these types will be persisted as appropriate data types in the database tables.
+Apache Causeway' bundles DataNucleus' http://www.datanucleus.org/documentation/products/plugins.html[built-in support] for Joda `LocalDate` and `LocalDateTime` datatypes, meaning that entity properties of these types will be persisted as appropriate data types in the database tables.
It is, however, necessary to annotate your properties with `@javax.jdo.annotations.Persistent`, otherwise the data won't actually be persisted.
See the link:http://db.apache.org/jdo/field_types.html[JDO docs] for more details on this.
@@ -312,7 +312,7 @@ More information can be found http://www.opentaps.org/docs/index.php/How_to_Use_
=== ``Blob``s
-Apache Isis configures JDO/DataNucleus so that the properties of type `org.apache.causeway.applib.value.Blob` and `org.apache.causeway.applib.value.Clob` can also be persisted.
+Apache Causeway configures JDO/DataNucleus so that the properties of type `org.apache.causeway.applib.value.Blob` and `org.apache.causeway.applib.value.Clob` can also be persisted.
As for Joda dates, this requires the `@javax.jdo.annotations.Persistent` annotation.
However, whereas for dates one would always expect this value to be retrieved eagerly, for blobs and clobs it is not so clear cut.
@@ -337,7 +337,7 @@ import lombok.Setter;
private Blob attachment;
----
-The three `@Column` annotations are required because the mapping classes that Apache Isis provides (https://github.com/apache/causeway/blob/causeway-1.4.0/component/objectstore/jdo/jdo-datanucleus/src/main/java/org/apache/causeway/objectstore/jdo/datanucleus/valuetypes/IsisBlobMapping.java#L59[IsisBlobMapping] and https://github.com/apache/causeway/blob/causeway-1.4.0/component/objectstore/jdo/jdo-datanucleus/src/main/java/org/apache/causeway/objectstore/jdo/datanucleus/valuetypes/IsisCl [...]
+The three `@Column` annotations are required because the mapping classes that Apache Causeway provides (https://github.com/apache/causeway/blob/causeway-1.4.0/component/objectstore/jdo/jdo-datanucleus/src/main/java/org/apache/causeway/objectstore/jdo/datanucleus/valuetypes/IsisBlobMapping.java#L59[IsisBlobMapping] and https://github.com/apache/causeway/blob/causeway-1.4.0/component/objectstore/jdo/jdo-datanucleus/src/main/java/org/apache/causeway/objectstore/jdo/datanucleus/valuetypes/Is [...]
(It is not an error to omit these `@Column` annotations, but without them the names of the table columns are simply suffixed `_0`, `_1`, `_2` etc.
If the `Blob` is mandatory, then use:
diff --git a/antora/components/userguide/modules/fun/pages/overview.adoc b/antora/components/userguide/modules/fun/pages/overview.adoc
index 9ceb580a63..710e6b857f 100644
--- a/antora/components/userguide/modules/fun/pages/overview.adoc
+++ b/antora/components/userguide/modules/fun/pages/overview.adoc
@@ -2,7 +2,7 @@
: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 [...]
-In this section we run through the main building blocks that make up an Apache Isis application.
+In this section we run through the main building blocks that make up an Apache Causeway application.
include::overview/types-of-domain-objects.adoc[leveloffset=+1]
diff --git a/antora/components/userguide/modules/fun/pages/overview/events.adoc b/antora/components/userguide/modules/fun/pages/overview/events.adoc
index c14f917adb..7d6d8e8a00 100644
--- a/antora/components/userguide/modules/fun/pages/overview/events.adoc
+++ b/antora/components/userguide/modules/fun/pages/overview/events.adoc
@@ -61,7 +61,7 @@ There are two use cases where this feature is useful:
* the first is to override the title/icon/CSS class/layout of 3rd party library code, for example as provided by the xref:security:secman:about.adoc[SecMan] extension.
-* the second is for xref:userguide:fun:view-models.adoc#jaxb[JAXB-style view models] which are code generated from XSDs and so cannot have any dependencies on the rest of the Apache Isis framework.
+* the second is for xref:userguide:fun:view-models.adoc#jaxb[JAXB-style view models] which are code generated from XSDs and so cannot have any dependencies on the rest of the Apache Causeway framework.
In this second case a subscriber on the default events can provide a title and icon for such an object, with the behaviour provided using xref:userguide:fun:overview.adoc#mixins[mixins].
diff --git a/antora/components/userguide/modules/fun/pages/overview/identifiers.adoc b/antora/components/userguide/modules/fun/pages/overview/identifiers.adoc
index 3fb6f57a9a..294abbf944 100644
--- a/antora/components/userguide/modules/fun/pages/overview/identifiers.adoc
+++ b/antora/components/userguide/modules/fun/pages/overview/identifiers.adoc
@@ -4,7 +4,7 @@
:page-partial:
-The Apache Isis framework tracks the identity of each domain object.
+The Apache Causeway framework tracks the identity of each domain object.
This identity is represented to the end-user in human-readable form so that they know which object they are interacting with, and is also used and is available internally/for integrations.
This section explores these two related concepts.
@@ -38,7 +38,7 @@ Details on how to actually write titles and icons (the programming model) can be
[[oid]]
== OIDs
-As well as defining a xref:userguide:fun:concepts-patterns.adoc#metamodel[metamodel] of the structure (domain classes) of its domain objects, Apache Isis also manages the runtime instances of said domain objects.
+As well as defining a xref:userguide:fun:concepts-patterns.adoc#metamodel[metamodel] of the structure (domain classes) of its domain objects, Apache Causeway also manages the runtime instances of said domain objects.
When a domain entity is recreated from the database, the framework keeps track of its identity through an "OID": an object identifier.
Fundamentally this is a combination of its type (domain class), along with an identifier.
@@ -48,7 +48,7 @@ For portability and resilience, though, the object type is generally an alias fo
This is derived from an annotation.
The identifier meanwhile is always converted to a string.
-Although simple, the OID is an enormously powerful concept: it represents a URI to any domain object managed by a given Apache Isis application.
+Although simple, the OID is an enormously powerful concept: it represents a URI to any domain object managed by a given Apache Causeway application.
With it, we have the ability to lookup any arbitrary domain objects.
Some examples:
diff --git a/antora/components/userguide/modules/fun/pages/overview/modules.adoc b/antora/components/userguide/modules/fun/pages/overview/modules.adoc
index de86b4c8e9..93b145b708 100644
--- a/antora/components/userguide/modules/fun/pages/overview/modules.adoc
+++ b/antora/components/userguide/modules/fun/pages/overview/modules.adoc
@@ -4,12 +4,12 @@
: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 [...]
:page-partial:
-Enabling and ensuring modularity is a xref:concepts-patterns.adoc#modular[key principle] for the Apache Isis framework.
+Enabling and ensuring modularity is a xref:concepts-patterns.adoc#modular[key principle] for the Apache Causeway framework.
Modularity is the only way to ensure that a complex application domain does not over time degenerate into the infamous "big ball of mud", software that is difficult, dangerous and expensive to change.
Modules chunk up the overall application into smaller pieces, usually a pacakge and subpackages.
The smaller pieces can be either tiers (presentation / domain / persistence) or functional architectural layers (eg customer vs orders vs products vs invoice etc).
-Because Apache Isis takes care of the presentation and persistence tiers, modules for us focuses just on the important bit: considering how the functionality within the domain model should be broken up into modules, and determining the dependencies between those modules.
+Because Apache Causeway takes care of the presentation and persistence tiers, modules for us focuses just on the important bit: considering how the functionality within the domain model should be broken up into modules, and determining the dependencies between those modules.
== Rules of Thumb
@@ -27,7 +27,7 @@ But this stuff is domain specific.
Having broken up a domain into multiple modules, there is still a need for higher level modules to use lower level modules, and the application must still appear as a coherent whole to the end-user.
-The key features that Apache Isis provides to support this are:
+The key features that Apache Causeway provides to support this are:
* dependency injection of services
+
@@ -126,7 +126,7 @@ Customer -u.-^ DocumentHolder
In the context of Java applications, modularity is a rather overloaded term.
We have Maven modules, Java 9 modules and we also have Spring link:https://docs.spring.io/spring-framework/docs/current/javadoc-api/org/springframework/context/annotation/Configuration.html[@Configuration]s, which define a set of domain services.
-In the context of Apache Isis, a module is actually the last of these, a Spring module.
+In the context of Apache Causeway, a module is actually the last of these, a Spring module.
The xref:docs:starters:simpleapp.adoc[simpleapp starter app] provide some structure and illustrates the idioms.
To summarise:
diff --git a/antora/components/userguide/modules/fun/pages/overview/object-members.adoc b/antora/components/userguide/modules/fun/pages/overview/object-members.adoc
index 02ab1f8eb0..2abca33adc 100644
--- a/antora/components/userguide/modules/fun/pages/overview/object-members.adoc
+++ b/antora/components/userguide/modules/fun/pages/overview/object-members.adoc
@@ -5,7 +5,7 @@
:page-partial:
-Every domain object in Apache Isis consists of (at most) three types of members:
+Every domain object in Apache Causeway consists of (at most) three types of members:
* properties, such as a ``Customer``'s `firstName`
@@ -19,7 +19,7 @@ Typically the behaviour being contributed is an action, but it could also be a d
[NOTE]
====
-What follows _is_ a simplification; the Apache Isis programming model also recognizes a number of other supporting methods for domain object members, for associated business logic.
+What follows _is_ a simplification; the Apache Causeway programming model also recognizes a number of other supporting methods for domain object members, for associated business logic.
This is covered in more detail in xref:userguide:fun:business-rules.adoc[business rules].
====
@@ -107,7 +107,7 @@ In more complex domains, it's not realistic/feasible to expect the end-user to h
Actions allow those business rules to be encoded programmatically.
Those actions can either be defined in the domain class itself, or can be contributed by way of a xref:overview.adoc#mixins[mixin].
-The general philosophy for an Apache Isis (naked objects) application is _not_ to constrain the end-user in how they interact with the UI: it doesn't attempt to define a rigid business process.
+The general philosophy for an Apache Causeway (naked objects) application is _not_ to constrain the end-user in how they interact with the UI: it doesn't attempt to define a rigid business process.
However, it _does_ aim to ensure that business rule invariants are maintained, that is that domain objects aren't allowed to enter into an invalid state.
For simple domain applications, you may want to start prototyping only with properties, and only later introduce actions (representing the most common business operations).
diff --git a/antora/components/userguide/modules/fun/pages/overview/programming-model.adoc b/antora/components/userguide/modules/fun/pages/overview/programming-model.adoc
index 0ee9b1341e..4985db749b 100644
--- a/antora/components/userguide/modules/fun/pages/overview/programming-model.adoc
+++ b/antora/components/userguide/modules/fun/pages/overview/programming-model.adoc
@@ -3,7 +3,7 @@
: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 [...]
-Apache Isis works by building a xref:concepts-patterns.adoc#metamodel[metamodel] of the domain objects: entities, domain services, view models and mixins.
+Apache Causeway works by building a xref:concepts-patterns.adoc#metamodel[metamodel] of the domain objects: entities, domain services, view models and mixins.
Dependent on the xref:overview.adoc#type-of-domain-objects[sort of domain object], the class methods represent both state -- (single-valued) xref:overview.adoc#properties[properties] and (multi-valued) xref:overview.adoc#collections[collections] -- and behaviour -- xref:overview.adoc#actions[actions].
More specifically, both xref:overview.adoc#domain-entities[entities] and xref:overview.adoc#view-models[view models] can have properties, collections and actions, while xref:overview.adoc#domain-services[domain services] have just actions.
@@ -15,15 +15,15 @@ A collection is generally rendered as a table.
Additional xref:business-rules.adoc[business rules] semantics are inferred both imperatively from _supporting methods_ (such as `disableXxx()`) and declaratively from xref:refguide:applib-ant:about.adoc[annotations].
-Taken together this set of conventions are what we call the _**Apache Isis Programming Model**_.
+Taken together this set of conventions are what we call the _**Apache Causeway Programming Model**_.
In essence, these conventions are just an extension of the pojo / JavaBean standard of yesteryear: properties and collections are getters/setters, while actions are simply any remaining `public` methods.
[TIP]
====
-In fact, the Apache Isis programming model is extensible; you can teach Apache Isis new programming conventions and you can remove existing ones; ultimately they amount to syntax.
+In fact, the Apache Causeway programming model is extensible; you can teach Apache Causeway new programming conventions and you can remove existing ones; ultimately they amount to syntax.
The only real fundamental that can't be changed is the notion that objects consist of properties, collections and actions.
-You can learn more about extending Apache Isis programming model xref:userguide:btb:programming-model.adoc[here].
+You can learn more about extending Apache Causeway programming model xref:userguide:btb:programming-model.adoc[here].
====
diff --git a/antora/components/userguide/modules/fun/pages/overview/types-of-domain-objects.adoc b/antora/components/userguide/modules/fun/pages/overview/types-of-domain-objects.adoc
index 332769a81c..312255f07d 100644
--- a/antora/components/userguide/modules/fun/pages/overview/types-of-domain-objects.adoc
+++ b/antora/components/userguide/modules/fun/pages/overview/types-of-domain-objects.adoc
@@ -5,7 +5,7 @@
:page-partial:
-Apache Isis supports recognises four main types of domain classes:
+Apache Causeway supports recognises four main types of domain classes:
* *domain entities* - domain objects persisted to the database the ORM (eg JDO/DataNucleus); for example `Customer`
@@ -20,8 +20,8 @@ From the end-user's perspective the UI displays a single domain object instance
The end-user can then inspect and modify its state, and navigate to related objects.
Domain classes are generally recognized using annotations.
-Apache Isis defines its own set of annotations, and
-you can generally recognize an Apache Isis domain class because it will be probably be annotated using `@DomainObject` and `@DomainService`.
+Apache Causeway defines its own set of annotations, and
+you can generally recognize an Apache Causeway domain class because it will be probably be annotated using `@DomainObject` and `@DomainService`.
The framework also recognises some annotations from the ORM layer (eg JDO/DataNucleus) and infers domain semantics from these annotations.
Similarly, JAXB annotations are typically used for view models.
@@ -48,7 +48,7 @@ There's good logic here: requiring only root-to-root relationships reduces the n
On the other hand, this constraint can substantially complicate matters when mapping domain layer to the persistence layer.
DDD tends to de-emphasise such matters: it aims to be completely agnostic about the persistence layer, with the responsibilities for managing relationships moved (pretty much by definition) into the domain layer.
-As a framework Apache Isis is less dogmatic about such things.
+As a framework Apache Causeway is less dogmatic about such things.
Generally the domain objects are mapped to a relational database and so we can lean on the referential integrity capabilities of the persistence layer to maintain referential invariants.
Said another way: we don't tend to require that only roots can maintain roots: we don't see anything wrong in an `InvoiceItem` referencing an `OrderItem`, for example.
@@ -77,7 +77,7 @@ For example, for the `Customer` entity there may be a `CustomerRepository`, whil
Similarly, entities might also have a corresponding factory service: a `CustomerFactory` or an `OrderFactory`; Evans' link:http://books.google.com/books/about/Domain_Driven_Design.html?id=hHBf4YxMnWMC[Domain Driven Design], draws a clear distinction between a factory (that creates object) and a repository (that is used to find existing objecpts).
On the other hand, from an end-users' perspective the act of finding an existing object vs creating a new one are quite closely related.
-For this reason, in Apache Isis it's therefore quite common to have a single domain service that acts as both a factory and a repository (and is usually called just a "repository").
+For this reason, in Apache Causeway it's therefore quite common to have a single domain service that acts as both a factory and a repository (and is usually called just a "repository").
The behaviour of these services is rendered in various ways, though the most obvious is as the menu actions on the top-level menu bars in the xref:vw:ROOT:about.adoc[Web UI (Wicket viewer)]'s UI.
@@ -89,11 +89,11 @@ Domain services can also be used for a number of other purposes:
+
This is discussed in more detail below, in the section on xref:userguide:fun:overview.adoc#events[events].
-* to implement an link:https://en.wikipedia.org/wiki/Service_provider_interface[SPI] of the Apache Isis framework, most notably cross-cutting concerns such as security, command profiling, auditing and publishing.
+* to implement an link:https://en.wikipedia.org/wiki/Service_provider_interface[SPI] of the Apache Causeway framework, most notably cross-cutting concerns such as security, command profiling, auditing and publishing.
Domain objects of any type (entities, other services, view models, mixins) can also delegate to domain services; domain services are automatically injected into every other domain object.
This injection of domain services into entities is significant: it allows business logic to be implemented in the domain entities, rather than have it "leach away" into supporting service layers.
-Said another way: it is the means by which Apache Isis helps you avoid the anaemic domain model anti-pattern.
+Said another way: it is the means by which Apache Causeway helps you avoid the anaemic domain model anti-pattern.
Domain services are instantiated once and once only by the framework, and are used to centralize any domain logic that does not logically belong in a domain entity or value.
@@ -145,7 +145,7 @@ Details on how to actually write a view model (the programming model for view mo
Sometimes the entities that make up your application are persisted not in the local database but reside in some other system, for example accessible only through a SOAP web service.
Logically that data might still be considered a domain entity and we might want to associate behaviour with it, however it cannot be modelled as a domain entity if only because JDO/DataNucleus doesn't know about the entity nor how to retrieve or update it.
-There are a couple of ways around this: we could either replicate the data somehow from the external system into the Isis-managed database (in which case it is once again just another domain entity), or we could set up a stub/proxy for the externally managed entity.
+There are a couple of ways around this: we could either replicate the data somehow from the external system into the Causeway-managed database (in which case it is once again just another domain entity), or we could set up a stub/proxy for the externally managed entity.
This proxy would hold the reference to the externally-managed domain entity (eg an external id), as well as the "smarts" to know how to interact with that entity (by making SOAP web service calls etc).
The stub/proxy is a type of view model: a view -- if you like -- onto the domain entity managed by the external system.
@@ -158,11 +158,11 @@ A simple example is read-only configuration data that is read from a config file
=== Application-layer view models
-Domain entities (whether locally persisted or managed externally) are the bread-and-butter of Apache Isis applications: the focus after all, should be on the business domain concepts and ensuring that they are solid.
+Domain entities (whether locally persisted or managed externally) are the bread-and-butter of Apache Causeway applications: the focus after all, should be on the business domain concepts and ensuring that they are solid.
Generally those domain entities will make sense to the business domain experts: they form the _ubiquitous language_ of the domain.
These domain entities are part of the domain layer.
-When developing an Apache Isis application you will most likely start off with the persistent domain entities: `Customer`, `Order`, `Product`, and so on.
+When developing an Apache Causeway application you will most likely start off with the persistent domain entities: `Customer`, `Order`, `Product`, and so on.
For some applications this may well suffice.
That said, it may not always be practical to expect end-users of the application to interact solely with those domain entities.
@@ -200,7 +200,7 @@ It is not a persisted entity, instead it belongs to the application layer.
DTOs (data transfer objects) are simple classes that (according to link:https://en.wikipedia.org/wiki/Data_transfer_object[wikipedia]) "carry data between processes".
-If those two processes are parts of the same overall application (the same team builds and deploys both server and client) then there's generally no need to define a DTO; just access the entities using Apache Isis' xref:vro:ROOT:about.adoc[RestfulObjects viewer].
+If those two processes are parts of the same overall application (the same team builds and deploys both server and client) then there's generally no need to define a DTO; just access the entities using Apache Causeway' xref:vro:ROOT:about.adoc[RestfulObjects viewer].
On the other hand, if the client consuming the DTO is a different application -- by which we mean developed/deployed by a different (possible third-party) team -- then the DTOs act as a formal contract between the provider and the consumer.
In such cases, exposing domain entities over xref:vro:ROOT:about.adoc[RestfulObjects] would be "A Bad Thing"(TM) because the consumer would in effect have access to implementation details that could then not be easily changed by the producer.
@@ -271,7 +271,7 @@ In fact, we find mixins nicely balance inside-out vs outside-in ways of thinking
* outside-in tends to focus on the behaviour, that is the functionality that the system provides to automate the business processes; the verbs, in other words.
-So, while Apache Isis allows you to put behaviour onto the underlying domain entities, it can often be better to treat the domain entities as immutable.
+So, while Apache Causeway allows you to put behaviour onto the underlying domain entities, it can often be better to treat the domain entities as immutable.
Instead, use mixins to implement behaviour.
When using an agile development methodology, it's common for a user story to correspond to a new mixin.
@@ -294,7 +294,7 @@ Mixins are an implementation of the link:http://www.artima.com/articles/dci_visi
Reenskaug was the inventor of the MVC pattern (and also the external examiner for Richard Pawson's link:../../../../../ug/fun/_attachments/core-concepts/Pawson-Naked-Objects-thesis.pdf[PhD thesis]), while Coplien has a long history in object-orientation, C++ and patterns.
DCI stands for Data-Context-Interaction and is presented as an evolution of object-oriented programming, but one where behaviour is bound to objects dynamically rather than statically in some context or other.
-The mixin pattern is Apache Isis' straightforward take on the same basic concept.
+The mixin pattern is Apache Causeway' straightforward take on the same basic concept.
****
diff --git a/antora/components/userguide/modules/fun/pages/ui.adoc b/antora/components/userguide/modules/fun/pages/ui.adoc
index 23a93b6c38..e5eae40a08 100644
--- a/antora/components/userguide/modules/fun/pages/ui.adoc
+++ b/antora/components/userguide/modules/fun/pages/ui.adoc
@@ -5,10 +5,10 @@
:page-partial:
-In implementing the http://en.wikipedia.org/wiki/Naked_objects[naked objects pattern], Apache Isis infers as much information from the domain classes as possible.
+In implementing the http://en.wikipedia.org/wiki/Naked_objects[naked objects pattern], Apache Causeway infers as much information from the domain classes as possible.
Nevertheless, some metadata relating solely to the UI is inevitably required.
-The Apache Isis programming model includes several mechanisms to influence the way in which the domain objects are rendered in the UI.
+The Apache Causeway programming model includes several mechanisms to influence the way in which the domain objects are rendered in the UI.
* the layout of application menu items (inferred from xref:domain-entities-and-services.adoc#domain-services[domain services])
diff --git a/antora/components/userguide/modules/fun/pages/ui/action-icons-and-css.adoc b/antora/components/userguide/modules/fun/pages/ui/action-icons-and-css.adoc
index 5ec983358f..2883e69af9 100644
--- a/antora/components/userguide/modules/fun/pages/ui/action-icons-and-css.adoc
+++ b/antora/components/userguide/modules/fun/pages/ui/action-icons-and-css.adoc
@@ -4,7 +4,7 @@
:page-partial:
-Apache Isis allows link:http://fortawesome.github.io/Font-Awesome/icons/[font awesome] icons to be associated with each action, and for link:http://getbootstrap.com/css/#buttons[Bootstrap CSS] to be applied to action rendered as buttons.
+Apache Causeway allows link:http://fortawesome.github.io/Font-Awesome/icons/[font awesome] icons to be associated with each action, and for link:http://getbootstrap.com/css/#buttons[Bootstrap CSS] to be applied to action rendered as buttons.
These UI hints can be applied either to individual actions, or can be applied en-masse using pattern matching.
It is also possible to specify additional CSS for an object's members (not just actions).
diff --git a/antora/components/userguide/modules/fun/pages/ui/menubars-layout.adoc b/antora/components/userguide/modules/fun/pages/ui/menubars-layout.adoc
index 605cfaa2e8..6c1b62ace4 100644
--- a/antora/components/userguide/modules/fun/pages/ui/menubars-layout.adoc
+++ b/antora/components/userguide/modules/fun/pages/ui/menubars-layout.adoc
@@ -97,7 +97,7 @@ There are some disadvantages to using file-based layouts:
* they also suffer from syntactic fragility: an invalid XML document could result in no metadata for the entire class.
-The `menubars.layout.xml` file is just the serialized form of a xref:refguide:applib-classes:layout/menubars.adoc[MenuBars] layout class defined within Apache Isis' applib.
+The `menubars.layout.xml` file is just the serialized form of a xref:refguide:applib-classes:layout/menubars.adoc[MenuBars] layout class defined within Apache Causeway' applib.
These are JAXB-annotated classes with corresponding XSD schemas; the upshot of that
is that IDEs such as IntelliJ and Eclipse can provide "intellisense", making it easy to author such layout files.
diff --git a/antora/components/userguide/modules/fun/pages/ui/object-layout.adoc b/antora/components/userguide/modules/fun/pages/ui/object-layout.adoc
index 916428dbee..231c272fd2 100644
--- a/antora/components/userguide/modules/fun/pages/ui/object-layout.adoc
+++ b/antora/components/userguide/modules/fun/pages/ui/object-layout.adoc
@@ -24,7 +24,7 @@ There are some downsides, though:
* there is no notion of inheritance, so a `.layout.xml` is required for all concrete classes and also for any abstract classes (if used as a collection type).
-The `Xxx.layout.xml` file is just the serialized form of a xref:refguide:applib-classes:layout/object-layout.adoc[Grid] layout class defined within Apache Isis' applib.
+The `Xxx.layout.xml` file is just the serialized form of a xref:refguide:applib-classes:layout/object-layout.adoc[Grid] layout class defined within Apache Causeway' applib.
These are JAXB-annotated classes with corresponding XSD schemas; the upshot of that is that IDEs such as IntelliJ and Eclipse can provide "intellisense", making iteasy to author such layout files.
== Grids vs Components
diff --git a/antora/components/userguide/modules/fun/pages/ui/object-titles-and-icons.adoc b/antora/components/userguide/modules/fun/pages/ui/object-titles-and-icons.adoc
index 6d74564092..258647f3c7 100644
--- a/antora/components/userguide/modules/fun/pages/ui/object-titles-and-icons.adoc
+++ b/antora/components/userguide/modules/fun/pages/ui/object-titles-and-icons.adoc
@@ -5,7 +5,7 @@
:page-partial:
-In Apache Isis every object is identified to the user by a title (label) and an icon.
+In Apache Causeway every object is identified to the user by a title (label) and an icon.
This is shown in several places: as the main heading for an object; as a link text for an object referencing another object, and also in tables representing collections of objects.
The icon is often the same for all instances of a particular class, but it's also possible for an individual instance to return a custom icon.
diff --git a/antora/components/userguide/modules/fun/pages/view-models.adoc b/antora/components/userguide/modules/fun/pages/view-models.adoc
index 5a9f2007f2..89807b1ebf 100644
--- a/antora/components/userguide/modules/fun/pages/view-models.adoc
+++ b/antora/components/userguide/modules/fun/pages/view-models.adoc
@@ -19,7 +19,7 @@ The framework provides three ways to implement a view model:
+
The serialized form of these view models is therefore XML, which also enables these view models to act as DTO (useful for various integration scenarios).
-* Using Apache Isis specific annotations.
+* Using Apache Causeway specific annotations.
+
This is more concise, but less powerful: only the state of the object's properties is serialized -- collections are ignored -- and not every datatype is recognized.
+
@@ -72,7 +72,7 @@ public class CompareCustomers {
}
----
-<.> The JAXB xref:refguide:applib-ant:XmlRootElement.adoc[@XmlRootElement] annotation indicates this is a view model to Apache Isis, which then uses JAXB to serialize the state of the view model between interactions
+<.> The JAXB xref:refguide:applib-ant:XmlRootElement.adoc[@XmlRootElement] annotation indicates this is a view model to Apache Causeway, which then uses JAXB to serialize the state of the view model between interactions
<.> Optionally, the properties of the view model can be listed using the `XmlType#propOrder` attribute. +
This is an all-or-nothing affair: either all properties must be listed, or else the annotation omitted.
<.> Specifying field accessor type allows the Lombok `@Getter` and `@Setter` annotations to be used.
@@ -98,7 +98,7 @@ It's quite common for view models to be "backed by" (be projections of) some und
For example, the `CompareCustomers` view model described xref:userguide:fun:view-models.adoc#jaxb[above] actually references two underlying ``Customer`` entities.
It wouldn't make sense to serialize out the state of a persistent entity.
-However, the identity of the underlying entity is well defined; Apache Isis defines the xref:refguide:schema:common.adoc[common schema] which defines the `<oid-dto>` element (and corresponding `OidDto` class): the object's type and its identifier.
+However, the identity of the underlying entity is well defined; Apache Causeway defines the xref:refguide:schema:common.adoc[common schema] which defines the `<oid-dto>` element (and corresponding `OidDto` class): the object's type and its identifier.
This is basically a formal XML equivalent to the `Bookmark` object obtained from the xref:refguide:applib:index/services/bookmark/BookmarkService.adoc[BookmarkService].
There is only one requirement to make this work: every referenced domain entity must be annotated with xref:refguide:applib-ant:XmlJavaTypeAdapter.adoc[@XmlJavaTypeAdapter], specifying the framework-provided `PersistentEntityAdapter`.
@@ -152,7 +152,7 @@ public class CompareCustomers {
If your JAXB view model contains fields using the JODA datatypes (`LocalDate` and so on), then `@XmlJavaTypeAdapter` additional annotations in order to "teach" JAXB how to serialize out the state.
-The Apache Isis applib provides a number of adapters to use out-of-the-box.
+The Apache Causeway applib provides a number of adapters to use out-of-the-box.
For example:
[source,java]
@@ -313,7 +313,7 @@ We can characterise these as:
* external entities
+
For example the application may interact synchronously with state exposed on another system through a REST or SOAP API.
-In this case the entity with your Apache Isis application is a proxy or a facade for the state on the external system
+In this case the entity with your Apache Causeway application is a proxy or a facade for the state on the external system
* internal entities
+
diff --git a/antora/components/userguide/modules/fun/partials/_deployment-options.adoc b/antora/components/userguide/modules/fun/partials/_deployment-options.adoc
index e2f26a9453..154109574a 100644
--- a/antora/components/userguide/modules/fun/partials/_deployment-options.adoc
+++ b/antora/components/userguide/modules/fun/partials/_deployment-options.adoc
@@ -5,7 +5,7 @@
== Prototyping
-Apache Isis is great for rapid prototyping, because all you need to write in order to get an application up-and-running is the domain model objects.
+Apache Causeway is great for rapid prototyping, because all you need to write in order to get an application up-and-running is the domain model objects.
By focusing just on the domain, you'll also find that you start to develop a ubiquitous language - a set of terms and concepts that the entire team (business and technologists alike) have a shared understanding.
@@ -17,12 +17,12 @@ Once you've sketched out your domain model, you can then either start-over and d
[#deploy-with-a-generic-ui]
== Deploy with a generic UI
-One of the original motivations for Apache Isis was to be able automatically generate a user interface for a domain object model.
+One of the original motivations for Apache Causeway was to be able automatically generate a user interface for a domain object model.
The framework's architecture allows for different user interface technologies.
The principal implementation is the xref:vw:ROOT:about.adoc[Web UI (Wicket viewer)], which as well as providing an appealing default user interface also has the ability to be customized the user interface by writing new link:http://wicket.apache.org[Apache Wicket] components.
The framework provides a xref:extensions:ROOT:about.adoc[number of these].
-Deploying on Apache Isis means that the framework also manages object persistence.
+Deploying on Apache Causeway means that the framework also manages object persistence.
Again this is pluggable.
There are two implementations, either xref:pjdo:ROOT:about.adoc[JDO (DataNucleus)] or xref:pjpa:ROOT:about.adoc[JPA (EclipseLink)].
These are normally used with an RDBMS, though in principle could be used with NoSQL databases.
@@ -35,7 +35,7 @@ JDO/DataNucleus historically has link:https://www.datanucleus.org/products/acces
If the xref:vw:ROOT:about.adoc[Web UI (Wicket viewer)]'s extensions are too restrictive, another option is to deploy custom controllers/views for specific use cases _alongside_ the generic viewer.
This way you can use the generic viewer to deliver the majority of the app's functionality, but you can justify the additional effort of writing a custom controller for those specialised/high volume use cases where a different flow is needed.
-Because Apache Isis runs on top of link:https://spring.io/projects/spring-boot[Spring Boot], you can easily integrate any of the UI technologies supported by Spring, or of course use Apache Wicket for a similar look-n-feel.
+Because Apache Causeway runs on top of link:https://spring.io/projects/spring-boot[Spring Boot], you can easily integrate any of the UI technologies supported by Spring, or of course use Apache Wicket for a similar look-n-feel.
== Deploy as a REST API
@@ -45,10 +45,10 @@ Many commercial web APIs (twitter, facebook, Amazon) are implemented as either p
The http://restfulobjects.org[Restful Objects specification] defines a means by which a domain object model can be exposed as RESTful resources using JSON representations over HTTP.
-Apache Isis' xref:vro:ROOT:about.adoc[RestfulObjects viewer] is an implementation of that spec, making any Apache Isis domain object automatically available via REST.
+Apache Causeway' xref:vro:ROOT:about.adoc[RestfulObjects viewer] is an implementation of that spec, making any Apache Causeway domain object automatically available via REST.
The set of domain objects can also be optionally restricted to exclude domain entities (thereby avoiding leaking implementation details).
-There are three main use cases for deploying Apache Isis as a RESTful web service are:
+There are three main use cases for deploying Apache Causeway as a RESTful web service are:
* to allow a custom UI to be built against the RESTful API
+
@@ -74,18 +74,18 @@ It is perfectly possible to deploy the RESTful API alongside an auto-generated w
== Deploy on your own platform
-You may be happy to use Apache Isis for prototyping, but have your own proprietary application framework to actually build production apps.
+You may be happy to use Apache Causeway for prototyping, but have your own proprietary application framework to actually build production apps.
-Apache Isis supports this, because the programming model defined by Apache Isis deliberately minimizes the dependencies on the rest of the framework.
-In fact, the only hard dependency that the domain model classes have on Apache Isis is through the `org.apache.causeway.applib` classes, mostly to pick up annotations such as xref:refguide:applib:index/annotation/Action.adoc[@Action] and xref:refguide:applib:index/annotation/Property.adoc[@Property].
-It's therefore relatively easy to take a domain object prototyped and/or tested using Apache Isis, but to deploy on some other framework's runtime.
+Apache Causeway supports this, because the programming model defined by Apache Causeway deliberately minimizes the dependencies on the rest of the framework.
+In fact, the only hard dependency that the domain model classes have on Apache Causeway is through the `org.apache.causeway.applib` classes, mostly to pick up annotations such as xref:refguide:applib:index/annotation/Action.adoc[@Action] and xref:refguide:applib:index/annotation/Property.adoc[@Property].
+It's therefore relatively easy to take a domain object prototyped and/or tested using Apache Causeway, but to deploy on some other framework's runtime.
If you are interested in taking this approach, then you will need to provide your own implementations of any framework-provided services used by your code.
If your own application framework is based on link:https://spring.io/projects/spring-boot[Spring Boot] and with JPA or JDO, then there is another option.
-As noted above, Apache Isis itself runs on top of Spring Boot.
-You could therefore develop a complete custom UI using one of the regular Spring technologies and run that alongside Apache Isis - in effect the option described <<deploy-with-custom-controllers,earlier>> but for every use case, not just selected ones.
-Apache Isis continues to manage the object lifecycle and persistence as a thin layer on top of Spring, but your custom UI renders the domain objects exactly as you require.
+As noted above, Apache Causeway itself runs on top of Spring Boot.
+You could therefore develop a complete custom UI using one of the regular Spring technologies and run that alongside Apache Causeway - in effect the option described <<deploy-with-custom-controllers,earlier>> but for every use case, not just selected ones.
+Apache Causeway continues to manage the object lifecycle and persistence as a thin layer on top of Spring, but your custom UI renders the domain objects exactly as you require.
diff --git a/api/schema/src/main/adoc/modules/schema/pages/about.adoc b/api/schema/src/main/adoc/modules/schema/pages/about.adoc
index 0ec7f625d2..357e14affe 100644
--- a/api/schema/src/main/adoc/modules/schema/pages/about.adoc
+++ b/api/schema/src/main/adoc/modules/schema/pages/about.adoc
@@ -4,7 +4,7 @@
Most applications need to integrate with other apps in the enterprise.
-To facilitate such integration scenarios, Apache Isis defines a number of standard XSD schemas:
+To facilitate such integration scenarios, Apache Causeway defines a number of standard XSD schemas:
* the xref:refguide:schema:mml.adoc[metamodel] schema, which allows the internal metamodel to be exported in a canonical fashion
diff --git a/api/schema/src/main/adoc/modules/schema/pages/common.adoc b/api/schema/src/main/adoc/modules/schema/pages/common.adoc
index 4ea7376a7b..83bc6f5895 100644
--- a/api/schema/src/main/adoc/modules/schema/pages/common.adoc
+++ b/api/schema/src/main/adoc/modules/schema/pages/common.adoc
@@ -12,7 +12,7 @@ The "common" schema defines a number of complex types that are used by other hig
The `oidDto` complex type captures an object's type and its identifier.
This is basically a formal XML equivalent to the `Bookmark` object obtained from the xref:refguide:applib:index/services/bookmark/BookmarkService.adoc[BookmarkService].
-Although simple, this is an enormously powerful concept, in that it represents a URI to any domain object managed by a given Apache Isis application.
+Although simple, this is an enormously powerful concept, in that it represents a URI to any domain object managed by a given Apache Causeway application.
With it, we have the ability to lookup any arbitrary object.
Further discussion and examples can be found xref:userguide:fun:overview.adoc#oid[here].
diff --git a/commons/src/main/adoc/modules/commons/pages/about.adoc b/commons/src/main/adoc/modules/commons/pages/about.adoc
index a22ed21220..c0b3db72b6 100644
--- a/commons/src/main/adoc/modules/commons/pages/about.adoc
+++ b/commons/src/main/adoc/modules/commons/pages/about.adoc
@@ -2,7 +2,7 @@
: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 [...]
-_Apache Isis Commons_ is a library with utilities, that are shared with the entire
+_Apache Causeway Commons_ is a library with utilities, that are shared with the entire
_Apache Isis_ ecosystem.
== Motivation
diff --git a/commons/src/main/adoc/modules/commons/pages/concurrent-task-list-UNUSED.adoc b/commons/src/main/adoc/modules/commons/pages/concurrent-task-list-UNUSED.adoc
index 1a3c321d67..3549194057 100644
--- a/commons/src/main/adoc/modules/commons/pages/concurrent-task-list-UNUSED.adoc
+++ b/commons/src/main/adoc/modules/commons/pages/concurrent-task-list-UNUSED.adoc
@@ -33,7 +33,7 @@ Dan::
OK, good enough for me.
Andi::
-ConcurrentTaskList and its co-operator classes reside in the internal API section of the 'commons' module, however they don't follow the _ prefixed scheme. I was in conflict with whether to move them up in the package hierarchy to make them also official usable by Isis coders. I decided 'not-yet' so we might want to add the prefixes.
+ConcurrentTaskList and its co-operator classes reside in the internal API section of the 'commons' module, however they don't follow the _ prefixed scheme. I was in conflict with whether to move them up in the package hierarchy to make them also official usable by Causeway coders. I decided 'not-yet' so we might want to add the prefixes.
Dan::
Yes, I'd prefer that : "_" to mean internal. If we do decide to make them formal API, we can refactor our internal code that uses it
@@ -43,7 +43,7 @@ most simple usecase scenario ...
+
[source,java]
----
-val taskList = ConcurrentTaskList.named("Isis Application Background Initialization Tasks")
+val taskList = ConcurrentTaskList.named("Causeway Application Background Initialization Tasks")
.addRunnable("Configure WebJars", this::configureWebJars)
.addRunnable("Configure WicketBootstrap", this::configureWicketBootstrap)
.addRunnable("Configure WicketSelect2", this::configureWicketSelect2);
diff --git a/core/config/src/main/adoc/modules/config/pages/about.adoc b/core/config/src/main/adoc/modules/config/pages/about.adoc
index e0075a2ca5..9373d3e77d 100644
--- a/core/config/src/main/adoc/modules/config/pages/about.adoc
+++ b/core/config/src/main/adoc/modules/config/pages/about.adoc
@@ -2,21 +2,21 @@
: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 [...]
-Apache Isis' is a Spring Boot application, and so is typically configured using an `application.properties` or `application.yml` file.
+Apache Causeway' is a Spring Boot application, and so is typically configured using an `application.properties` or `application.yml` file.
The configuration can be obtained from a variety of external locations; see the link:https://docs.spring.io/spring-boot/docs/current/reference/html/spring-boot-features.html#boot-features-external-config[Spring Boot] documentation for more details.
TIP: The xref:docs:starters:about.adoc[starter apps] use `application.yml` for configuration that doesn't change between environments, and `config/application.properties` for settings (such as JDBC URL) that does vary.
-This chapter describes the configuration properties available to configure an Apache Isis application.
+This chapter describes the configuration properties available to configure an Apache Causeway application.
[#deployment-types]
== Deployment Types
-Apache Isis distinguishes between the application being run in prototyping mode vs running in production mode.
+Apache Causeway distinguishes between the application being run in prototyping mode vs running in production mode.
The framework calls this the "deployment type" (corresponding internally to the `DeploymentType` class).
A similar concept appears in the link:https://wicket.apache.org[Apache Wicket] framework (which is the library with which the xref:vw:ROOT:about.adoc[Web UI (Wicket viewer)] is implemented, of course).
@@ -26,7 +26,7 @@ Wicket's term is the "configuration".
[cols="1a,1a", options="header"]
|===
-| Apache Isis +
+| Apache Causeway +
deployment type
| Apache Wicket library +
configuration
@@ -40,7 +40,7 @@ configuration
|===
-By default Apache Isis runs in production mode.
+By default Apache Causeway runs in production mode.
But if configured to run instead in prototyping mode, then any actions xref:refguide:applib:index/annotation/Action.adoc#restrictTo[restricted to] to prototype mode are visible.
In particular, the "Prototyping" menu will appear, containing a number of framework-provided menu services - all restricted to prototyping mode.
For example, menu items to run in xref:testing:fixtures:about.adoc[fixture scripts] are on this menu.
@@ -96,7 +96,7 @@ Applications can discover the prototyping mode by injecting the `IsisSystemEnvir
[#specifying-components]
== Specifying components
-Components are pluggable parts of the Apache Isis framework that are responsible for the presentation layer, for security, or for persistence.
+Components are pluggable parts of the Apache Causeway framework that are responsible for the presentation layer, for security, or for persistence.
Each component corresponds to one or more Maven module(s), and are specified using the Spring link:https://docs.spring.io/spring-framework/docs/current/javadoc-api/org/springframework/context/annotation/Import.html[@Import] statements from a top-level class annotated with Spring's link:https://docs.spring.io/spring-framework/docs/current/javadoc-api/org/springframework/context/annotation/Configuration.html[@Configuration] annotation.
These are then bootstrapped from a link:https://docs.spring.io/spring-boot/docs/current/api/org/springframework/boot/autoconfigure/SpringBootApplication.html[@SpringBootApplication] or link:https://docs.spring.io/spring-boot/docs/current/api/org/springframework/boot/test/context/SpringBootTest.html[@SpringBootTest].
@@ -122,7 +122,7 @@ public class SimpleApp
<.> specifies prototyping mode.
This enables actions marked for prototyping to become available, useful during the early stages of development.
-In turn, the "app manifest" (the name has been retained from Apache Isis v1.x) is the top-level Spring `@Configuration`.
+In turn, the "app manifest" (the name has been retained from Apache Causeway v1.x) is the top-level Spring `@Configuration`.
It looks like this:
[source,java]
@@ -143,7 +143,7 @@ public class AppManifest {
}
----
-<.> Mandatory - specifies the core of the Apache Isis framework
+<.> Mandatory - specifies the core of the Apache Causeway framework
<.> Enables the Shiro security mechanism.
There are several security implementations, precisely one must be selected
<.> Enables xref:pjpa:ROOT:about.adoc[JPA/Eclipselink] for persistence.
diff --git a/core/config/src/main/adoc/modules/config/pages/section-hooks/datanucleus~pre.adoc b/core/config/src/main/adoc/modules/config/pages/section-hooks/datanucleus~pre.adoc
index 67cd451a5a..503a001094 100644
--- a/core/config/src/main/adoc/modules/config/pages/section-hooks/datanucleus~pre.adoc
+++ b/core/config/src/main/adoc/modules/config/pages/section-hooks/datanucleus~pre.adoc
@@ -1,5 +1,5 @@
: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 [...]
-Configuration properties that are passed through directly to DataNucleus, unused by Apache Isis itself.
+Configuration properties that are passed through directly to DataNucleus, unused by Apache Causeway itself.
diff --git a/core/config/src/main/adoc/modules/config/pages/section-hooks/eclipselink~pre.adoc b/core/config/src/main/adoc/modules/config/pages/section-hooks/eclipselink~pre.adoc
index 2b3acd5a51..0f8b68cdf6 100644
--- a/core/config/src/main/adoc/modules/config/pages/section-hooks/eclipselink~pre.adoc
+++ b/core/config/src/main/adoc/modules/config/pages/section-hooks/eclipselink~pre.adoc
@@ -1,5 +1,5 @@
: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 [...]
-Configuration properties that are passed through directly to EclipseLink, unused by Apache Isis itself.
+Configuration properties that are passed through directly to EclipseLink, unused by Apache Causeway itself.
diff --git a/core/config/src/main/adoc/modules/config/pages/section-hooks/isis.core.config~pre.adoc b/core/config/src/main/adoc/modules/config/pages/section-hooks/isis.core.config~pre.adoc
index 436ffe469b..c31f00de1a 100644
--- a/core/config/src/main/adoc/modules/config/pages/section-hooks/isis.core.config~pre.adoc
+++ b/core/config/src/main/adoc/modules/config/pages/section-hooks/isis.core.config~pre.adoc
@@ -1,5 +1,5 @@
: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 [...]
-Configuration of the DataNucleus JDO persistence component (the Apache Isis component that wraps the DataNucleus ORM).
+Configuration of the DataNucleus JDO persistence component (the Apache Causeway component that wraps the DataNucleus ORM).
diff --git a/core/config/src/main/adoc/modules/config/pages/sections/isis.security.keycloak.adoc b/core/config/src/main/adoc/modules/config/pages/sections/isis.security.keycloak.adoc
index 353b1cb299..b190b33410 100644
--- a/core/config/src/main/adoc/modules/config/pages/sections/isis.security.keycloak.adoc
+++ b/core/config/src/main/adoc/modules/config/pages/sections/isis.security.keycloak.adoc
@@ -41,7 +41,7 @@ login-success-url
causeway.security.keycloak.realm
|
-| The name of the realm for the Apache Isis application, as configured in Keycloak.
+| The name of the realm for the Apache Causeway application, as configured in Keycloak.
diff --git a/core/metamodel/src/main/adoc/modules/metamodel/pages/about.adoc b/core/metamodel/src/main/adoc/modules/metamodel/pages/about.adoc
index 5f2a86facc..a0a1a75c12 100644
--- a/core/metamodel/src/main/adoc/modules/metamodel/pages/about.adoc
+++ b/core/metamodel/src/main/adoc/modules/metamodel/pages/about.adoc
@@ -28,8 +28,8 @@ endlegend
together {
rectangle "<$database_cube><$at>\n<<Annotation>>\nORM (JPA/JDO)" as PERS
rectangle "<$envira><$at>\n<<Annotation>>\nSpring" as SPRING
- rectangle "<img:https://causeway.apache.org/_/img/home/causeway-logo-56x64.png><$at>\n<<Annotation>>\nApache Isis" as FW
- rectangle "<img:https://causeway.apache.org/_/img/home/causeway-logo-56x64.png><$java>\n<<Supporting Methods>>\nApache Isis" as SM
+ rectangle "<img:https://causeway.apache.org/_/img/home/causeway-logo-56x64.png><$at>\n<<Annotation>>\nApache Causeway" as FW
+ rectangle "<img:https://causeway.apache.org/_/img/home/causeway-logo-56x64.png><$java>\n<<Supporting Methods>>\nApache Causeway" as SM
rectangle "<$java><$ma_xml><$at>\n<<Annotation>>\nJAXB" as JAXB
SPRING -[hidden]- PERS
@@ -130,7 +130,7 @@ together {
(Entity) as E
(View\nModel) as VM
}
-(<i>Apache Isis</i>) as FW
+(<i>Apache Causeway</i>) as FW
(Persistence\nLayer) as PL
together {
(Mixin) as M
diff --git a/core/metamodel/src/main/adoc/modules/metamodel/pages/class-diagram.adoc b/core/metamodel/src/main/adoc/modules/metamodel/pages/class-diagram.adoc
index aa95dddfc1..3e1a7e0cc0 100644
--- a/core/metamodel/src/main/adoc/modules/metamodel/pages/class-diagram.adoc
+++ b/core/metamodel/src/main/adoc/modules/metamodel/pages/class-diagram.adoc
@@ -3,7 +3,7 @@
: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 [...]
-The diagram below shows a simplified version of Apache Isis' internal metamodel.
+The diagram below shows a simplified version of Apache Causeway' internal metamodel.
[plantuml]
diff --git a/extensions/core/flyway/adoc/modules/flyway/pages/about.adoc b/extensions/core/flyway/adoc/modules/flyway/pages/about.adoc
index dbbadc6fb5..755b61555b 100644
--- a/extensions/core/flyway/adoc/modules/flyway/pages/about.adoc
+++ b/extensions/core/flyway/adoc/modules/flyway/pages/about.adoc
@@ -45,7 +45,7 @@ causeway.persistence.schema.auto-create-schemas= // <.>
<.> the default schema managed by Flyway (containing the `schema_version` table); see link:https://flywaydb.org/documentation/configuration/parameters/defaultSchema[flyway.defaultSchema] config property (Flyway docs) for more info
<.> all of the schemas managed by Flyway; see link:https://flywaydb.org/documentation/configuration/parameters/schemas[flyway.schemas] config property (Flyway docs) for more info
<.> whether Flyway should automatically create schemas ; see link:https://flywaydb.org/documentation/configuration/parameters/createSchemas[flyway.createSchemas] for more info
-<.> instruct Apache Isis to _not_ attempt to create schemas
+<.> instruct Apache Causeway to _not_ attempt to create schemas
The ORM should also be configured to _not_ automatically create tables:
diff --git a/extensions/security/secman/adoc/modules/secman/pages/about.adoc b/extensions/security/secman/adoc/modules/secman/pages/about.adoc
index 3555d9fdaa..731b47298e 100644
--- a/extensions/security/secman/adoc/modules/secman/pages/about.adoc
+++ b/extensions/security/secman/adoc/modules/secman/pages/about.adoc
@@ -6,7 +6,7 @@
SecMan provides an implementation of both the xref:refguide:core:index/security/authentication/Authenticator.adoc[Authenticator] and xref:refguide:core:index/security/authorization/Authorizor.adoc[Authorizor] SPIs, storing user, roles and permissions information as domain entities (persisted to relational database).
It can be used with both the JDO or JPA persistence mechanisms.
-Because these features are implemented using domain entities, it means that this security information can be administered from within your Apache Isis application.
+Because these features are implemented using domain entities, it means that this security information can be administered from within your Apache Causeway application.
The domain model is explained in more detail <<domain-model,below>>.
If SecMan is used for authentication, user/passwords are stored in encrypted form using a configured `PasswordEncoder`.
@@ -65,7 +65,7 @@ The diagram below shows the domain model for SecMan, and how it relates to the f
.SecMan domain model
image:secman-domain-model.drawio.svg[]
-SecMan's users, roles and permissions are entities, but application features are serializable value types that are derived from the Apache Isis metamodel.
+SecMan's users, roles and permissions are entities, but application features are serializable value types that are derived from the Apache Causeway metamodel.
Thus:
@@ -191,9 +191,9 @@ For this reason, the xref:refguide:extensions:index/secman/applib/user/dom/Appli
TIP: Another implementation of xref:refguide:extensions:index/secman/applib/tenancy/spi/ApplicationTenancyEvaluator.adoc[ApplicationTenancyEvaluator] can be found in the xref:docs:demo:about.adoc[Demo App]..
-.Apache Isis' multi-tenancy is only skin deep
+.Apache Causeway' multi-tenancy is only skin deep
****
-It's important to realize that Apache Isis' multi-tenancy support is only skin deep.
+It's important to realize that Apache Causeway' multi-tenancy support is only skin deep.
What we mean by that is that the restricting of access to data is only performed at the presentation layer.
If a user is not permitted to view/edit an object, then it is only the viewer component prevents them from doing so; the restricted object could still have been retrieved into memory from the database.
diff --git a/extensions/security/secman/adoc/modules/secman/pages/setting-up-with-shiro.adoc b/extensions/security/secman/adoc/modules/secman/pages/setting-up-with-shiro.adoc
index a0cb9f82a2..3c5e5688a3 100644
--- a/extensions/security/secman/adoc/modules/secman/pages/setting-up-with-shiro.adoc
+++ b/extensions/security/secman/adoc/modules/secman/pages/setting-up-with-shiro.adoc
@@ -17,12 +17,12 @@ image:secman-shiro-architecture.drawio.svg[]
Thus:
-* Apache Isis' xref:security:shiro:about.adoc[Shiro security] integration sets up Shiro web filters to intercept every http request, as well as the xref:refguide:security:index/shiro/authentication/AuthenticatorShiro.adoc[AuthenticatorShiro] implementation.
+* Apache Causeway' xref:security:shiro:about.adoc[Shiro security] integration sets up Shiro web filters to intercept every http request, as well as the xref:refguide:security:index/shiro/authentication/AuthenticatorShiro.adoc[AuthenticatorShiro] implementation.
* The `AuthenticatorShiro` calls to the Shiro Security Manager to obtain the authenticated principal.
* The Shiro Security Manager uses the `shiro.ini` configuration file to look up the realm to perform the authentication; in this case we configure it to use Secman's realm (xref:refguide:extensions:index/secman/delegated/shiro/realm/IsisModuleExtSecmanShiroRealm.adoc[IsisModuleExtSecmanShiroRealm]).
* Secman's realm implementation queries the database and uses this to create an instance of `PrincipalForApplicationUser`, where the `Principal` interface is Shiro's representation of an authenticated user.
The `PrincipalForApplicationUser` is backed by xref:refguide:extensions:index/secman/applib/user/dom/ApplicationUser.adoc[ApplicationUser], which all of the permissions to object members for this particular user.
-* to render a page, the Apache Isis viewer uses configured `Authorizor`, in this case
+* to render a page, the Apache Causeway viewer uses configured `Authorizor`, in this case
Secman's own xref:refguide:extensions:index/secman/integration/authorizor/AuthorizorSecman.adoc[AuthorizorSecman].
This looks up the current xref:refguide:extensions:index/secman/applib/user/dom/ApplicationUser.adoc[ApplicationUser] (which will already reside in-memory) and renders the page according to which object members are visible or not.
diff --git a/extensions/security/secman/adoc/modules/secman/pages/setting-up.adoc b/extensions/security/secman/adoc/modules/secman/pages/setting-up.adoc
index 72cdd38ddc..35dc242475 100644
--- a/extensions/security/secman/adoc/modules/secman/pages/setting-up.adoc
+++ b/extensions/security/secman/adoc/modules/secman/pages/setting-up.adoc
@@ -3,7 +3,7 @@
: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 [...]
:page-partial:
-This section describes how to setup and configure SecMan for use in your Apache Isis application, for both authentication (`Authenticator` SPI) and authorization (`Authorizor` SPI).
+This section describes how to setup and configure SecMan for use in your Apache Causeway application, for both authentication (`Authenticator` SPI) and authorization (`Authorizor` SPI).
It is also possible to use SecMan in conjunction with the framework's xref:security:shiro:about.adoc[integration with Shiro], where Shiro takes primary responsibility for authentication, while still using Secman for authorization.
This mode allows a separate authentication mechanism such as LDAP to be used.
diff --git a/extensions/security/shiro-realm-ldap/adoc/modules/shiro-realm-ldap/pages/about.adoc b/extensions/security/shiro-realm-ldap/adoc/modules/shiro-realm-ldap/pages/about.adoc
index 7c3aa555ae..4967fa5450 100644
--- a/extensions/security/shiro-realm-ldap/adoc/modules/shiro-realm-ldap/pages/about.adoc
+++ b/extensions/security/shiro-realm-ldap/adoc/modules/shiro-realm-ldap/pages/about.adoc
@@ -16,7 +16,7 @@
The Shiro framework also ships with an implementation of an LDAP-based realm; LDAP is often used to manage user/passwords and corresponding user groups.
-Apache Isis extends Shiro's implementation this `IsisLdapRealm`, which provides more flexibility for both group/role and role/permissions management.
+Apache Causeway extends Shiro's implementation this `IsisLdapRealm`, which provides more flexibility for both group/role and role/permissions management.
WARNING: TODO: v2 - to write up...
diff --git a/extensions/security/shiro-realm-ldap/adoc/modules/shiro-realm-ldap/pages/ldap-realm.adoc b/extensions/security/shiro-realm-ldap/adoc/modules/shiro-realm-ldap/pages/ldap-realm.adoc
index 5a28dd374b..2b2fa94c8e 100644
--- a/extensions/security/shiro-realm-ldap/adoc/modules/shiro-realm-ldap/pages/ldap-realm.adoc
+++ b/extensions/security/shiro-realm-ldap/adoc/modules/shiro-realm-ldap/pages/ldap-realm.adoc
@@ -4,7 +4,7 @@
:page-partial:
-Apache Isis ships with an implementation of http://shiro.apache.org[Apache Shiro]'s `Realm` class that allows user authentication and authorization to be performed against an LDAP server.
+Apache Causeway ships with an implementation of http://shiro.apache.org[Apache Shiro]'s `Realm` class that allows user authentication and authorization to be performed against an LDAP server.
image::security:shiro-realm-ldap:configure-shiro-to-use-causeway-ldap-realm.png[width="600px"]
@@ -49,7 +49,7 @@ securityManager.realms = $ldapRealm
----
<.> user accounts are searched using a dedicated service account
<.> SASL (CRAM-MD5) authentication is used for this authentication
-<.> Apache Isis' implementation of the LDAP realm.
+<.> Apache Causeway' implementation of the LDAP realm.
<.> groups are searched under `ou=groups,o=mojo` (where `mojo` is the company name)
<.> each group has an LDAP objectClass of `groupOfUniqueNames`
<.> each group has a vector attribute of `uniqueMember`
@@ -130,7 +130,7 @@ Create the `ou=groups,o=mojo` hierarchy:
image::security:shiro-realm-ldap:activeds-ldap-mojo-root-dse.png[]
-Configure SASL authentication. This means that the checking of user/password is done implicitly by virtue of Apache Isis connecting to LDAP using these credentials:
+Configure SASL authentication. This means that the checking of user/password is done implicitly by virtue of Apache Causeway connecting to LDAP using these credentials:
image::security:shiro-realm-ldap:activeds-ldap-sasl-authentication.png[]
diff --git a/incubator/clients/kroviz/adoc/modules/kroviz/pages/DevelopmentGuide.adoc b/incubator/clients/kroviz/adoc/modules/kroviz/pages/DevelopmentGuide.adoc
index 0d93c5ac7d..71c7d387b8 100644
--- a/incubator/clients/kroviz/adoc/modules/kroviz/pages/DevelopmentGuide.adoc
+++ b/incubator/clients/kroviz/adoc/modules/kroviz/pages/DevelopmentGuide.adoc
@@ -5,7 +5,7 @@ image::WheatFieldWithCrows.png[]
== Quickstart
-. Build Isis with kroviz
+. Build Causeway with kroviz
+
----
cd ~/causeway
@@ -34,7 +34,7 @@ http://localhost:3000
. Select 'Connect' in the Burger Menu
-TIP: Originally Apache Isis SimpleApp 1.16.0 was used as the reference RO backend.
+TIP: Originally Apache Causeway SimpleApp 1.16.0 was used as the reference RO backend.
This required some extra steps in order to deal with CORS setup, see sections on pre 2.0.0-M3 and CORS.
Currently (2.0.0-M6) Demo is used as reference - at the moment it's the only CORS enabled application.
=== Frontend
@@ -297,7 +297,7 @@ include::partial$design/dev-overview.adoc[]
==== Create from Archetype
-Create from the Apache Isis SimpleApp archetype:
+Create from the Apache Causeway SimpleApp archetype:
[source,bash]
----
@@ -405,7 +405,7 @@ Put into webapp/src/main/webapp/WEB-INF/lib:
==== Solution 3:
- Incorporate kroviz.js e.g. in the WAR containing your Apache Isis backend.
+ Incorporate kroviz.js e.g. in the WAR containing your Apache Causeway backend.
== Extensions
diff --git a/incubator/clients/kroviz/adoc/modules/kroviz/pages/about.adoc b/incubator/clients/kroviz/adoc/modules/kroviz/pages/about.adoc
index 9ac8f1e732..e144120b59 100644
--- a/incubator/clients/kroviz/adoc/modules/kroviz/pages/about.adoc
+++ b/incubator/clients/kroviz/adoc/modules/kroviz/pages/about.adoc
@@ -3,7 +3,7 @@
: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 [...]
-The Kroviz client provides a user interface for Apache Isis applications, the same as other viewers such as the xref:vw:ROOT:about.adoc[Web UI (Wicket viewer)].
+The Kroviz client provides a user interface for Apache Causeway applications, the same as other viewers such as the xref:vw:ROOT:about.adoc[Web UI (Wicket viewer)].
Krovix is called a "client" (rather than a "viewer") because it runs within the web browser, and consumes the REST API provided by the xref:vro:ROOT:about.adoc[REST API (Restful Objects viewer)].
diff --git a/incubator/clients/kroviz/adoc/modules/kroviz/pages/credits.adoc b/incubator/clients/kroviz/adoc/modules/kroviz/pages/credits.adoc
index ada95f9e93..be1f7d9acf 100644
--- a/incubator/clients/kroviz/adoc/modules/kroviz/pages/credits.adoc
+++ b/incubator/clients/kroviz/adoc/modules/kroviz/pages/credits.adoc
@@ -23,7 +23,7 @@ convert.exe WheatFieldWithCrows.jpg -channel all isis_clut.png -clut WheatFieldW
convert.exe WheatFieldWithCrows.jpg -separate -normalize -combine isis_clut.png -clut WheatFieldWithCrows.png
----
-== Apache Isis colors
+== Apache Causeway colors
In the icon: green, orange, red, blue
diff --git a/incubator/clients/kroviz/adoc/modules/kroviz/pages/regression-test.adoc b/incubator/clients/kroviz/adoc/modules/kroviz/pages/regression-test.adoc
index 7031622a92..a76751a747 100644
--- a/incubator/clients/kroviz/adoc/modules/kroviz/pages/regression-test.adoc
+++ b/incubator/clients/kroviz/adoc/modules/kroviz/pages/regression-test.adoc
@@ -38,7 +38,7 @@ end note
component Demo <<RO App>> as APP
FE <-> APP : request / response
-component "Apache Isis" <<Naked Objects FW>> as FW
+component "Apache Causeway" <<Naked Objects FW>> as FW
APP -> FW : uses
diff --git a/mavendeps/adoc/modules/mavendeps/pages/about.adoc b/mavendeps/adoc/modules/mavendeps/pages/about.adoc
index 52d9e6d63e..64a21f3798 100644
--- a/mavendeps/adoc/modules/mavendeps/pages/about.adoc
+++ b/mavendeps/adoc/modules/mavendeps/pages/about.adoc
@@ -23,7 +23,7 @@ For convenience, it includes all of the current components available:
* Spring Boot (link:https://docs.spring.io/spring-boot/docs/current/reference/html/getting-started.html#getting-started-first-application-dependencies[spring-boot-starter-web])
-* Apache Isis Core - the xref:refguide:ROOT:about.adoc[Applib] and underlying implementation (the _Runtime Services_ module)
+* Apache Causeway Core - the xref:refguide:ROOT:about.adoc[Applib] and underlying implementation (the _Runtime Services_ module)
* The xref:security:bypass:about.adoc[Bypass] security implementation.
+
@@ -35,7 +35,7 @@ If you don't need any of these, then use a Maven `<exclusion>`.
In addition, you will probably need to specify a persistence implementation (xref:pjpa:ROOT:about.adoc[JPA/Eclipselink] or xref:pjdo:ROOT:about.adoc[JDO/DataNucleus]) as well as a security implementation.
-Also, remember that adding the class onto the classpath does _not_ make that functionality available (Apache Isis does not currently leverage Spring Boot's link:https://docs.spring.io/spring-boot/docs/current/reference/html/using-spring-boot.html#using-boot-auto-configuration[auto configuration] capabilities).
+Also, remember that adding the class onto the classpath does _not_ make that functionality available (Apache Causeway does not currently leverage Spring Boot's link:https://docs.spring.io/spring-boot/docs/current/reference/html/using-spring-boot.html#using-boot-auto-configuration[auto configuration] capabilities).
You must therefore also add in the appropriate `IsisModuleXxx` to your application's top-level link:https://docs.spring.io/spring-framework/docs/current/javadoc-api/org/springframework/context/annotation/Configuration.html[@Configuration] (aka "app manifest").
For example, see the xref:docs:starters:simpleapp.adoc#appmanifest[AppManifest for the SimpleApp] starter app.
diff --git a/mavendeps/adoc/modules/mavendeps/partials/setup-and-configure-dependencyManagement.adoc b/mavendeps/adoc/modules/mavendeps/partials/setup-and-configure-dependencyManagement.adoc
index 3ee3da3fbb..8712eaef06 100644
--- a/mavendeps/adoc/modules/mavendeps/partials/setup-and-configure-dependencyManagement.adoc
+++ b/mavendeps/adoc/modules/mavendeps/partials/setup-and-configure-dependencyManagement.adoc
@@ -5,7 +5,7 @@
-If your application inherits from the Apache Isis starter app (`org.apache.causeway.app:causeway-app-starter-parent`) then that will define the version automatically:
+If your application inherits from the Apache Causeway starter app (`org.apache.causeway.app:causeway-app-starter-parent`) then that will define the version automatically:
[source,xml,subs="attributes+"]
.pom.xml
diff --git a/persistence/jdo/adoc/modules/ROOT/pages/configuring/disabling-persistence-by-reachability.adoc b/persistence/jdo/adoc/modules/ROOT/pages/configuring/disabling-persistence-by-reachability.adoc
index 276df407c5..c07f6e61b8 100644
--- a/persistence/jdo/adoc/modules/ROOT/pages/configuring/disabling-persistence-by-reachability.adoc
+++ b/persistence/jdo/adoc/modules/ROOT/pages/configuring/disabling-persistence-by-reachability.adoc
@@ -6,7 +6,7 @@
By default, JDO/DataNucleus supports the concept of link:http://www.datanucleus.org/products/datanucleus/jdo/persistence.html#persistence_by_reachability[persistence-by-reachability].
That is, if a non-persistent entity is associated with an already-persistent entity, then DataNucleus will detect this and will automatically persist the associated object.
-Put another way: there is no need to call Apache Isis' `RepositoryService#persist(.)` or `RepositoryService#persistAndFlush(.)` methods.
+Put another way: there is no need to call Apache Causeway' `RepositoryService#persist(.)` or `RepositoryService#persistAndFlush(.)` methods.
However, convenient though this feature is, you may find that it causes performance issues.
@@ -16,7 +16,7 @@ DataNucleus' persistence-by-reachability may cause performance issues.
We strongly recommend that you disable it.
====
-One scenario in particular where this performance issues can arise is if your entities implement the `java.lang.Comparable` interface, and you have used Apache Isis' xref:refguide:applib:index/util/ObjectContracts.adoc[ObjectContracts] utility class.
+One scenario in particular where this performance issues can arise is if your entities implement the `java.lang.Comparable` interface, and you have used Apache Causeway' xref:refguide:applib:index/util/ObjectContracts.adoc[ObjectContracts] utility class.
The issue here is that `ObjectContracts` implementation can cause DataNucleus to recursively rehydrate a larger number of associated entities.
(More detail below).
diff --git a/persistence/jdo/adoc/modules/ROOT/pages/dependency-injection.adoc b/persistence/jdo/adoc/modules/ROOT/pages/dependency-injection.adoc
index edec24230a..a2689eb9ba 100644
--- a/persistence/jdo/adoc/modules/ROOT/pages/dependency-injection.adoc
+++ b/persistence/jdo/adoc/modules/ROOT/pages/dependency-injection.adoc
@@ -3,7 +3,7 @@
: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 [...]
-With Apache Isis it's common to inject domain services into domain entities; this allows behaviour to be pushed down into those entities.
+With Apache Causeway it's common to inject domain services into domain entities; this allows behaviour to be pushed down into those entities.
For JDO, both field injection and setter injection is performed automatically:
diff --git a/persistence/jdo/adoc/modules/ROOT/pages/hints-and-tips.adoc b/persistence/jdo/adoc/modules/ROOT/pages/hints-and-tips.adoc
index ab963dc54b..3d4992e73b 100644
--- a/persistence/jdo/adoc/modules/ROOT/pages/hints-and-tips.adoc
+++ b/persistence/jdo/adoc/modules/ROOT/pages/hints-and-tips.adoc
@@ -4,7 +4,7 @@
: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 [...]
-This page provides some solutions for problems we've encountered ourselves or have been raised on the Apache Isis mailing lists.
+This page provides some solutions for problems we've encountered ourselves or have been raised on the Apache Causeway mailing lists.
include::hints-and-tips/tracing-sql-statements.adoc[leveloffset=+1]
include::hints-and-tips/overriding-jdo-annotations.adoc[leveloffset=+1]
diff --git a/persistence/jdo/adoc/modules/ROOT/pages/hints-and-tips/subtype-entity-not-fully-populated.adoc b/persistence/jdo/adoc/modules/ROOT/pages/hints-and-tips/subtype-entity-not-fully-populated.adoc
index 630247328a..ed6e58d390 100644
--- a/persistence/jdo/adoc/modules/ROOT/pages/hints-and-tips/subtype-entity-not-fully-populated.adoc
+++ b/persistence/jdo/adoc/modules/ROOT/pages/hints-and-tips/subtype-entity-not-fully-populated.adoc
@@ -4,10 +4,10 @@
: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 [...]
-Taken from link:http://markmail.org/message/ovgai56uqgfgnrx7[this thread] on the Apache Isis users mailing list...
+Taken from link:http://markmail.org/message/ovgai56uqgfgnrx7[this thread] on the Apache Causeway users mailing list...
-If it seems that Apache Isis (or rather DataNucleus) isn't fully populating domain entities (ie leaving some properties as `null`), then check that your actions are not accessing the fields directly.
+If it seems that Apache Causeway (or rather DataNucleus) isn't fully populating domain entities (ie leaving some properties as `null`), then check that your actions are not accessing the fields directly.
Use getters instead.
diff --git a/persistence/jdo/adoc/modules/ROOT/pages/mapping-guide/mandatory-properties-in-subtypes.adoc b/persistence/jdo/adoc/modules/ROOT/pages/mapping-guide/mandatory-properties-in-subtypes.adoc
index 775db4550e..e768ef9cc7 100644
--- a/persistence/jdo/adoc/modules/ROOT/pages/mapping-guide/mandatory-properties-in-subtypes.adoc
+++ b/persistence/jdo/adoc/modules/ROOT/pages/mapping-guide/mandatory-properties-in-subtypes.adoc
@@ -21,7 +21,7 @@ whereby a single table holds the properties of the subtype, and also holds the p
In the first "rollup" case, we can have a situation where - logically speaking - the property is mandatory in the subtype - but it must be mapped as nullable in the database because it is n/a for any other subtypes that are rolled up.
-In this situation we must tell JDO that the column is optional, but to Apache Isis we want to enforce it being mandatory. This can be done using the `@Property(optionality=Optionality.MANDATORY)` annotation.
+In this situation we must tell JDO that the column is optional, but to Apache Causeway we want to enforce it being mandatory. This can be done using the `@Property(optionality=Optionality.MANDATORY)` annotation.
For example:
diff --git a/persistence/jdo/adoc/modules/ROOT/pages/setup-and-configuration.adoc b/persistence/jdo/adoc/modules/ROOT/pages/setup-and-configuration.adoc
index 54e0de1ada..4ae668aa5f 100644
--- a/persistence/jdo/adoc/modules/ROOT/pages/setup-and-configuration.adoc
+++ b/persistence/jdo/adoc/modules/ROOT/pages/setup-and-configuration.adoc
@@ -157,7 +157,7 @@ For example, use `datanucleus.schema.autoCreateAll` not `datanucleus.schema.auto
DataNucleus will for itself also read the `META-INF/persistence.xml`.
In theory this can hold mappings and even connection strings.
-However, with Apache Isis we tend to use annotations instead and externalize connection strings. so its definition is extremely simply, specifying just the name of the "persistence unit".
+However, with Apache Causeway we tend to use annotations instead and externalize connection strings. so its definition is extremely simply, specifying just the name of the "persistence unit".
Here's the one provided by the xref:docs:starters:simpleapp.adoc[SimpleApp] starter app:
diff --git a/persistence/jpa/adoc/modules/ROOT/pages/dependency-injection.adoc b/persistence/jpa/adoc/modules/ROOT/pages/dependency-injection.adoc
index d63fe1461a..183ad712bb 100644
--- a/persistence/jpa/adoc/modules/ROOT/pages/dependency-injection.adoc
+++ b/persistence/jpa/adoc/modules/ROOT/pages/dependency-injection.adoc
@@ -3,7 +3,7 @@
: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 [...]
-With Apache Isis it's common to inject domain services into domain entities; this allows behaviour to be pushed down into those entities.
+With Apache Causeway it's common to inject domain services into domain entities; this allows behaviour to be pushed down into those entities.
For JPA, this requires that the following boilerplate:
diff --git a/persistence/jpa/adoc/modules/ROOT/pages/hints-and-tips.adoc b/persistence/jpa/adoc/modules/ROOT/pages/hints-and-tips.adoc
index 73acc3d90c..a693cfc7f2 100644
--- a/persistence/jpa/adoc/modules/ROOT/pages/hints-and-tips.adoc
+++ b/persistence/jpa/adoc/modules/ROOT/pages/hints-and-tips.adoc
@@ -4,6 +4,6 @@
: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 [...]
-This page provides some solutions for problems we've encountered ourselves or have been raised on the Apache Isis mailing lists.
+This page provides some solutions for problems we've encountered ourselves or have been raised on the Apache Causeway mailing lists.
include::pjdo:ROOT:page$hints-and-tips/tracing-sql-statements.adoc[leveloffset=+1]
diff --git a/persistence/jpa/adoc/modules/ROOT/pages/mapping-guide.adoc b/persistence/jpa/adoc/modules/ROOT/pages/mapping-guide.adoc
index 856ecc1357..3a7af87daf 100644
--- a/persistence/jpa/adoc/modules/ROOT/pages/mapping-guide.adoc
+++ b/persistence/jpa/adoc/modules/ROOT/pages/mapping-guide.adoc
@@ -159,7 +159,7 @@ public class MyEntity ... {
----
<.> the field as it is persisted by the ORM
-<.> the property as it is understood by Apache Isis.
+<.> the property as it is understood by Apache Causeway.
TIP: if you have multiple instancs of an `@Embedded` type, the `@javax.persistence.AttributeOverrides` and `@javax.persistence.AttributeOverride` provide a standardised way of fine-tuning the column definitions.
@@ -188,7 +188,7 @@ public class MyEntity ... {
----
<.> the field as it is persisted by the ORM
-<.> the property as it is understood by Apache Isis.
+<.> the property as it is understood by Apache Causeway.
TIP: if you have multiple instances of an `@Embedded` type, the `@javax.persistence.AttributeOverrides` and `@javax.persistence.AttributeOverride` provide a standardised way of fine-tuning the column definitions.
diff --git a/persistence/jpa/adoc/modules/ROOT/pages/setup-and-configuration.adoc b/persistence/jpa/adoc/modules/ROOT/pages/setup-and-configuration.adoc
index 36885de60d..d01827c91f 100644
--- a/persistence/jpa/adoc/modules/ROOT/pages/setup-and-configuration.adoc
+++ b/persistence/jpa/adoc/modules/ROOT/pages/setup-and-configuration.adoc
@@ -75,7 +75,7 @@ is set to `create-or-extend-tables`
* `javax.persistence.bean.manager`
+
-is set to an Apache Isis implementation, to assist with dependency injection into entities.
+is set to an Apache Causeway implementation, to assist with dependency injection into entities.
Generally these should not be changed, though if there is a requirement, then provide a subclasse alternate implementation of `org.apache.causeway.persistence.jpa.eclipselink.config.ElSettings` with an earlier `@Priority` precedence.
diff --git a/persistence/jpa/adoc/modules/ROOT/pages/weaving.adoc b/persistence/jpa/adoc/modules/ROOT/pages/weaving.adoc
index 3996ab1465..938fb221b5 100644
--- a/persistence/jpa/adoc/modules/ROOT/pages/weaving.adoc
+++ b/persistence/jpa/adoc/modules/ROOT/pages/weaving.adoc
@@ -73,7 +73,7 @@ As well as setting the above configuration options, it's also neceesary to run t
mvn dependency:get -DgroupId=org.springframework -DartifactId=spring-instrument -Dversion=XXX
----
=
-changing "XXX" to the value that `${spring-framework.version}` resolves to, from the Isis parent `pom.xml`.
+changing "XXX" to the value that `${spring-framework.version}` resolves to, from the Causeway parent `pom.xml`.
* Move and rename this file, eg to `lib/spring-instrument.jar`.
diff --git a/security/adoc/modules/ROOT/pages/about.adoc b/security/adoc/modules/ROOT/pages/about.adoc
index fe521546a1..5a18b9339d 100644
--- a/security/adoc/modules/ROOT/pages/about.adoc
+++ b/security/adoc/modules/ROOT/pages/about.adoc
@@ -4,12 +4,12 @@
:page-partial:
-This guide describes how to secure your Apache Isis application by configuring an appropriate implementation of its authentication and authorization SPIs.
+This guide describes how to secure your Apache Causeway application by configuring an appropriate implementation of its authentication and authorization SPIs.
== Security Architecture
-Apache Isis defines an SPI for both authentication and authorization:
+Apache Causeway defines an SPI for both authentication and authorization:
* By "authentication" we mean logging into the application using some credentials, typically a username and password.
Authentication also means looking up the set of roles to which a user belongs.
@@ -36,7 +36,7 @@ In addition to the security SPI implementations, there are a number of security-
* The xref:security:shiro-realm-ldap:about.adoc[LDAP Realm] extension confiures the xref:security:shiro:about.adoc[Shiro authenticator] to use LDAP as a credential source.
* The xref:security:secman:about.adoc[SecMan extension] provides both an authenticator and an authorizor from domain entities (users, roles and permission entities) using either xref:pjpa:ROOT:about.adoc[JPA] or xref:pjdo:ROOT:about.adoc[JDO].
+
-As these users, roles and permissions are domain objects, they can be administered through Apache Isis itself.
+As these users, roles and permissions are domain objects, they can be administered through Apache Causeway itself.
Note that authenticators and authorizor components can be mixed.
For example, the Keycloak or Spring OAuth2 authenticator can be used with Secman for authorization.
@@ -64,7 +64,7 @@ If there is neither _read_ nor _write_ permissions then the feature will be invi
A further aspect of security is auditing: recording what data was modified by which user.
-Apache Isis provides the xref:refguide:applib:index/services/iactnlayer/InteractionContext.adoc[InteractionContext] can be used to track the actions being invoked, and the xref:refguide:applib:index/services/publishing/spi/EntityPropertyChangeSubscriber.adoc[EntityPropertyChangeSubscriber] captures what data was modified as a result (auditing).
+Apache Causeway provides the xref:refguide:applib:index/services/iactnlayer/InteractionContext.adoc[InteractionContext] can be used to track the actions being invoked, and the xref:refguide:applib:index/services/publishing/spi/EntityPropertyChangeSubscriber.adoc[EntityPropertyChangeSubscriber] captures what data was modified as a result (auditing).
When xref:refguide:applib:index/services/iactn/Interaction.adoc[Interaction]s are persisted (eg by way of the xref:userguide:executionlog:about.adoc[Execution Log] extension) then this provides excellent traceability.
The xref:security:audittrail:about.adoc[Audit Trail] module provides an implementation of the xref:refguide:applib:index/services/publishing/spi/EntityPropertyChangeSubscriber.adoc[EntityPropertyChangeSubscriber] that persists audit entries to the database.
@@ -76,7 +76,7 @@ The xref:userguide:commandlog:about.adoc[Command Log] extension provides a simpl
Generally speaking your domain objects (or more generally your application) should be agnostic of the user/roles that are interacting with them; applying security permissions is the responsibility of the framework.
-If you need to determine the identity of the current user, you can usually use Apache Isis' xref:refguide:applib:index/services/user/UserService.adoc[UserService] API, in the form of xref:refguide:applib:index/services/user/UserMemento.adoc[UserMemento].
+If you need to determine the identity of the current user, you can usually use Apache Causeway' xref:refguide:applib:index/services/user/UserService.adoc[UserService] API, in the form of xref:refguide:applib:index/services/user/UserMemento.adoc[UserMemento].
For example:
diff --git a/security/adoc/modules/ROOT/pages/usage-by-isis-viewers.adoc b/security/adoc/modules/ROOT/pages/usage-by-isis-viewers.adoc
index 9e2f157980..6873a8eb36 100644
--- a/security/adoc/modules/ROOT/pages/usage-by-isis-viewers.adoc
+++ b/security/adoc/modules/ROOT/pages/usage-by-isis-viewers.adoc
@@ -1,10 +1,10 @@
[[usage-by-causeway-viewers]]
-= Usage by Apache Isis' Viewers
+= Usage by Apache Causeway' Viewers
: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 [...]
-By and large the security mechanisms within Isis are transparent to the rest of the framework.
+By and large the security mechanisms within Causeway are transparent to the rest of the framework.
That said, it is the responsibility of the viewers to ensure that for each request there is a valid user session present.
The sections below explain how this works.
diff --git a/security/adoc/modules/ROOT/partials/module-nav-end.adoc b/security/adoc/modules/ROOT/partials/module-nav-end.adoc
index 213153169c..656b8a7b64 100644
--- a/security/adoc/modules/ROOT/partials/module-nav-end.adoc
+++ b/security/adoc/modules/ROOT/partials/module-nav-end.adoc
@@ -1,3 +1,3 @@
-* xref:security:ROOT:usage-by-causeway-viewers.adoc[Usage by Isis Viewers]
+* xref:security:ROOT:usage-by-causeway-viewers.adoc[Usage by Causeway Viewers]
diff --git a/security/keycloak/src/main/adoc/modules/keycloak/pages/about.adoc b/security/keycloak/src/main/adoc/modules/keycloak/pages/about.adoc
index 56f1fae5d4..43b8c598a2 100644
--- a/security/keycloak/src/main/adoc/modules/keycloak/pages/about.adoc
+++ b/security/keycloak/src/main/adoc/modules/keycloak/pages/about.adoc
@@ -4,7 +4,7 @@
:page-partial:
-This guide describes the configuration of the Keycloak implementation of Apache Isis' `Authenticator` API.
+This guide describes the configuration of the Keycloak implementation of Apache Causeway' `Authenticator` API.
It does _not_ however provide any implementation of xref:refguide:core:index/security/authorization/Authorizor.adoc[Authorizor] SPI.
You will therefore need to configure an alternative implementation, eg the xref:bypass:about.adoc[Bypass] implementation (to disable authorisation checks completely), or use the xref:secman:about.adoc[SecMan] implementation (see xref:security:secman:setting-up-with-keycloak.adoc[here for details]).
@@ -112,7 +112,7 @@ image::define-simpleapp-realm.png[width=400px]
=== Create a Keycloak client for the application
-From the perspective of Keycloak, the Apache Isis domain application is a client: the domain app redirects its login page to Keycloak (and be redirected back on success).
+From the perspective of Keycloak, the Apache Causeway domain application is a client: the domain app redirects its login page to Keycloak (and be redirected back on success).
We therefore need to create the Keycloak client for our app:
* create the client:
@@ -206,7 +206,7 @@ image::logged-in-as-sven.png[width=800px]
=== Test
-Finally, start the Apache Isis application:
+Finally, start the Apache Causeway application:
* and confirm that navigating to http://localhost:8080 redirects to the keycloak login:
+
diff --git a/security/shiro/src/main/adoc/modules/shiro/pages/about.adoc b/security/shiro/src/main/adoc/modules/shiro/pages/about.adoc
index e888439686..9dd7c6effb 100644
--- a/security/shiro/src/main/adoc/modules/shiro/pages/about.adoc
+++ b/security/shiro/src/main/adoc/modules/shiro/pages/about.adoc
@@ -4,7 +4,7 @@
:page-partial:
-This guide describes the design and configuration of the Apache Shiro integration with Apache Isis.
+This guide describes the design and configuration of the Apache Shiro integration with Apache Causeway.
== Design
@@ -35,7 +35,7 @@ An enhanced "wildcard" syntax, described <<enhanced-wildcard-permission,below>>
[[configuring-causeway-to-use-shiro]]
== Configuring to use Shiro
-Apache Isis' security mechanism is configurable, specifying an `Authenticator` and an `Authorizor` (non-public) APIs.
+Apache Causeway' security mechanism is configurable, specifying an `Authenticator` and an `Authorizor` (non-public) APIs.
The Shiro security mechanism is an integration with Apache Shiro that implements both interfaces.
[TIP]
@@ -102,7 +102,7 @@ Another option alternative is the xref:security:shiro-realm-ldap:about.adoc[LDAP
As noted above, as well as realms many other aspects of configuration can be specified in this file:
* enable caching for performance; discussed <<caching,below>>
-* leverage Apache Isis' <<enhanced-wildcard-permission,enhanced wildcard permissions>>, by specifying the Apache Isis permission resolver; discussed <<permission-resolver-configuration,below>>.
+* leverage Apache Causeway' <<enhanced-wildcard-permission,enhanced wildcard permissions>>, by specifying the Apache Causeway permission resolver; discussed <<permission-resolver-configuration,below>>.
[#shiro-ini-realm]
@@ -213,7 +213,7 @@ myapp # ditto
[TIP]
====
-The format of the permissions string is configurable in Shiro, and Apache Isis uses this to provide an extended wildcard format, described xref:security:shiro:about.adoc#enhanced-wildcard-permission[here].
+The format of the permissions string is configurable in Shiro, and Apache Causeway uses this to provide an extended wildcard format, described xref:security:shiro:about.adoc#enhanced-wildcard-permission[here].
====
@@ -280,8 +280,8 @@ Instead, the corresponding sections from for `realm1.ini` are used instead.
[#enhanced-wildcard-permission]
== Enhanced Wildcard Permission
-If using the text-based xref:security:shiro:about.adoc#shiro-ini-realm[IniRealm] or xref:security:shiro-realm-ldap:about.adoc[Apache Isis' LDAP realm], then note that Shiro also allows the string representation of the permissions to be mapped (resolved) to alternative `Permission` instances.
-Apache Isis provides its own `IsisPermission` which introduces the concept of a "veto".
+If using the text-based xref:security:shiro:about.adoc#shiro-ini-realm[IniRealm] or xref:security:shiro-realm-ldap:about.adoc[Apache Causeway' LDAP realm], then note that Shiro also allows the string representation of the permissions to be mapped (resolved) to alternative `Permission` instances.
+Apache Causeway provides its own `IsisPermission` which introduces the concept of a "veto".
A vetoing permission is one that prevents access to a feature, rather than grants it.
This is useful in some situations where most users have access to most features, and only a small number of features are particularly sensitive.
@@ -332,7 +332,7 @@ The net effect is therefore what we would want: that a user with both `admin_rol
[[permission-resolver-configuration]]
=== Configuration
-To configure Apache Isis' extended permission support requires that a custom permission resolver is specified in `shiro.ini` file:
+To configure Apache Causeway' extended permission support requires that a custom permission resolver is specified in `shiro.ini` file:
[source,ini]
----
diff --git a/security/spring/src/main/adoc/modules/spring/pages/about.adoc b/security/spring/src/main/adoc/modules/spring/pages/about.adoc
index d086278f5c..a102bbadb7 100644
--- a/security/spring/src/main/adoc/modules/spring/pages/about.adoc
+++ b/security/spring/src/main/adoc/modules/spring/pages/about.adoc
@@ -4,7 +4,7 @@
:page-partial:
-This guide describes the configuration of the Spring implementation of Apache Isis' xref:refguide:core:index/security/authentication/Authenticator.adoc[Authenticator] SPI.
+This guide describes the configuration of the Spring implementation of Apache Causeway' xref:refguide:core:index/security/authentication/Authenticator.adoc[Authenticator] SPI.
It does _not_ however provide any implementation of xref:refguide:core:index/security/authorization/Authorizor.adoc[Authorizor] SPI.
You will therefore need to configure an alternative implementation, eg the xref:bypass:about.adoc[Bypass] implementation (to disable authorisation checks completely), or use the xref:secman:about.adoc[SecMan] implementation (see xref:security:secman:setting-up-with-spring-oauth2.adoc[here for details]).
@@ -126,7 +126,7 @@ public class SecurityConfig extends WebSecurityConfigurerAdapter
<.> at least one role must be assigned to each user.
Next, we configure the necessary components (including `SecurityConfig`, above).
-As discussed <<_update-appmanifest,above>>, we need to reference Apache Isis' Spring security module and also an implementation of xref:refguide:core:index/security/authorization/Authorizor.adoc[Authorizor] SPI, eg the xref:bypass:about.adoc[Bypass] implementation:
+As discussed <<_update-appmanifest,above>>, we need to reference Apache Causeway' Spring security module and also an implementation of xref:refguide:core:index/security/authorization/Authorizor.adoc[Authorizor] SPI, eg the xref:bypass:about.adoc[Bypass] implementation:
[source,java]
.AppManifest.java
@@ -175,7 +175,7 @@ image::spring-security-login.png[width=300px]
[#authenticatorconverter-spi]
== AuthenticatorConverter SPI
-The module provides a number of implementations of xref:refguide:security:index/spring/authconverters/AuthenticationConverter.adoc[AuthenticationConverter] that (attempt to) convert a Spring `Authentication` object into an Apache Isis `UserMemento`.
+The module provides a number of implementations of xref:refguide:security:index/spring/authconverters/AuthenticationConverter.adoc[AuthenticationConverter] that (attempt to) convert a Spring `Authentication` object into an Apache Causeway `UserMemento`.
Several implementations are provided by default for most of the common representations of a user principal, including support for link:https://docs.spring.io/spring-security/site/docs/current/api/org/springframework/security/core/userdetails/UserDetails.html[UserDetails] (as returned in the <<walk-through-in-memory,in-memory walk through above>>) and link:https://docs.spring.io/spring-security/site/docs/current/api/org/springframework/security/oauth2/core/user/OAuth2User.html[OAuth2User].
This SPI does though provide additional flexibility for other security technologies that may be supported by link:https://spring.io/projects/spring-security[Spring].
diff --git a/starters/adoc/modules/parent-pom/pages/about.adoc b/starters/adoc/modules/parent-pom/pages/about.adoc
index 443908cf5b..2a73e27fe0 100644
--- a/starters/adoc/modules/parent-pom/pages/about.adoc
+++ b/starters/adoc/modules/parent-pom/pages/about.adoc
@@ -3,7 +3,7 @@
: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 [...]
-The starter app parent POM is provided as a convenience to act as the `<parent>` for Apache Isis applications.
+The starter app parent POM is provided as a convenience to act as the `<parent>` for Apache Causeway applications.
It builds upon a similar POM provided by the Spring Boot framework, which ensures a consistent set of dependencies, as well as configuring various build plugins.
== Usage
@@ -35,7 +35,7 @@ As the diagram shows, the parent POM inherits two Spring Boot parent POMs: direc
* `spring-boot-starter-parent` configures various `<build>/<plugins>` and `<resources>`, while
* `spring-boot-dependencies` the second defines numerous `xxx.version` properties for various third party applications (validated as being compatible with each other by the Spring Boot team), and sets up corresponding `<dependencyManagement>/<dependencies>`.
-The parent POM also import (using `scope=import, type=pom`) each of the "bill of material" POMs provided by Apache Isis framework:
+The parent POM also import (using `scope=import, type=pom`) each of the "bill of material" POMs provided by Apache Causeway framework:
* `org.apache.causeway.core:causeway` -
+
@@ -55,7 +55,7 @@ For the `causeway-testing-xxx` modules (fixture scripts, unit test support, inte
* `o.a.i.legacy:causeway-legacy`
-These all set up `<dependencyManagement>/<dependencies>` entries for all of the modules, meaning that there's only one place to update the version to Apache Isis (the reference to the parent POM).
+These all set up `<dependencyManagement>/<dependencies>` entries for all of the modules, meaning that there's only one place to update the version to Apache Causeway (the reference to the parent POM).
[#surefire-configuration]
diff --git a/starters/adoc/modules/starters/pages/helloworld.adoc b/starters/adoc/modules/starters/pages/helloworld.adoc
index a1de35b396..8caea69698 100644
--- a/starters/adoc/modules/starters/pages/helloworld.adoc
+++ b/starters/adoc/modules/starters/pages/helloworld.adoc
@@ -3,14 +3,14 @@
: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 [...]
-The quickest way to start learning about Apache Isis is to use the `helloworld` starter app.
+The quickest way to start learning about Apache Causeway is to use the `helloworld` starter app.
There are two variations of the application (and so two branches in the git repo).
One variation uses JDO as the ORM, the other uses JPA, so you can focus on whichever ORM you prefer.
The application is also deployed online for you to try out, link:https://helloworld.jdo.causeway.incode.work[here (jdo)] and link:https://helloworld.jpa.causeway.incode.work[here (jpa)].
-Using the instructions <<Downloading & Running,below>>, you can download a minimal Apache Isis app, consisting of a single domain entity (`HelloWorldObject`) with supporting domain services.
+Using the instructions <<Downloading & Running,below>>, you can download a minimal Apache Causeway app, consisting of a single domain entity (`HelloWorldObject`) with supporting domain services.
Both the business logic and supporting bootstrapping classes are in a single Maven module.
[TIP]
@@ -22,11 +22,11 @@ It also creates a minimal application, but provides more structure along with te
== Prerequisites
-Apache Isis is a Java based framework, so in terms of prerequisites, you'll need to install:
+Apache Causeway is a Java based framework, so in terms of prerequisites, you'll need to install:
* Java 11 JDK (or later)
+
-Apache Isis itself is compatible with Java 11, and the helloworld app itself is configured for Java 11.
+Apache Causeway itself is compatible with Java 11, and the helloworld app itself is configured for Java 11.
* link:http://maven.apache.org[Apache Maven] 3.5+
@@ -198,7 +198,7 @@ image::helloworld/using/250-retrieve-object-using-rest-api-response.png[width="6
The Swagger UI is provided as a convenience; the REST API is actually a complete hypermedia API (in other words you can follow the links to access all the behaviour exposed in the regular Wicket app).
-The REST API implemented by Apache Isis is specified in the link:http://www.restfulobjects.org[Restful Object spec].
+The REST API implemented by Apache Causeway is specified in the link:http://www.restfulobjects.org[Restful Object spec].
@@ -239,7 +239,7 @@ src/main/java/
Change as required.
<.> Defines the 'hello' module.
-Apache Isis can be used for both microservice and monolithic architectures, but for the latter it encourages "modular monoliths" from the start.
+Apache Causeway can be used for both microservice and monolithic architectures, but for the latter it encourages "modular monoliths" from the start.
<.> The `dom` package holds the "domain object model" for this module.
Modules may have other packages, common ones include ``types`` (as below), also ``api``s, ``contribution``s, ``fixture``s, ``spi``s
@@ -254,7 +254,7 @@ The associated `.layout.xml` and `.png` are optional but provide metadata/resour
<.> `HelloWorldModule` is a Spring link:https://docs.spring.io/spring-framework/docs/current/javadoc-api/org/springframework/context/annotation/Configuration.html[@Configuration] which allows the domain services and entities of the module to be located. +
This is discussed in more detail xref:#helloworldmodule[below].
-<.> `AppManifest` is the top-level Spring link:https://docs.spring.io/spring-framework/docs/current/javadoc-api/org/springframework/context/annotation/Configuration.html[@Configuration] that specifies the components of Apache Isis to use, along with the modules making up the application itself (ie `HelloWorldModule`). +
+<.> `AppManifest` is the top-level Spring link:https://docs.spring.io/spring-framework/docs/current/javadoc-api/org/springframework/context/annotation/Configuration.html[@Configuration] that specifies the components of Apache Causeway to use, along with the modules making up the application itself (ie `HelloWorldModule`). +
This is discussed in more detail xref:#appmanifest[below].
<.> `HelloWorldApp` is the link:https://docs.spring.io/spring-boot/docs/current/api/org/springframework/boot/autoconfigure/SpringBootApplication.html[@SpringBootApplication] used to bootstrap the app.
@@ -267,7 +267,7 @@ This is discussed in more detail xref:#helloworldapp[below].
[#helloworldmodule]
==== HelloWorldModule
-Every module within an Apache Isis application should have a module class.
+Every module within an Apache Causeway application should have a module class.
Its purpose is to define a package to scan from, and optionally to declare any transitive dependencies.
In the case of `HelloWorldModule`, it is extremely simple:
@@ -297,7 +297,7 @@ If there were, these would be expressed in terms of module classes (each being a
<.> for `jpa` branch only, to automatically discover JPA entities
-The scanning mechanism is also leveraged by Apache Isis to pick up three types of classes:
+The scanning mechanism is also leveraged by Apache Causeway to pick up three types of classes:
* all domain services
+
@@ -351,7 +351,7 @@ public class AppManifest {
}
----
-<.> Mandatory - specifies the core of the Apache Isis framework
+<.> Mandatory - specifies the core of the Apache Causeway framework
<.> Enables the Shiro security mechanism.
There are several security implementations, precisely one must be selected
@@ -443,7 +443,7 @@ Typically this just holds JDBC connection strings, etc.
<.> The `banner.txt` is shown when bootstrapping.
-<.> The `log4j2-spring.xml` configures log4j2 (the logging system used by Apache Isis)
+<.> The `log4j2-spring.xml` configures log4j2 (the logging system used by Apache Causeway)
<.> The `menubars.layout.xml` arranges the actions of the domain services into menus.
@@ -468,7 +468,7 @@ JQuery is available by default.
=== No src/main/webapp
-Note that there is no `src/main/webapp/` or `WEB-INF/web.xml` - the servlets and filters are configured by Apache Isis automatically.
+Note that there is no `src/main/webapp/` or `WEB-INF/web.xml` - the servlets and filters are configured by Apache Causeway automatically.
=== No src/test/java
@@ -497,7 +497,7 @@ This means:
* the set of third party dependencies declared have been validated as compatible by Spring Boot team
* build plugins are declared and configured appropriately
-* imports to the Apache Isis dependencies are declared via `<dependencyManagement>`
+* imports to the Apache Causeway dependencies are declared via `<dependencyManagement>`
diff --git a/starters/adoc/modules/starters/pages/simpleapp.adoc b/starters/adoc/modules/starters/pages/simpleapp.adoc
index 16fc3cfd14..6230c111e0 100644
--- a/starters/adoc/modules/starters/pages/simpleapp.adoc
+++ b/starters/adoc/modules/starters/pages/simpleapp.adoc
@@ -9,7 +9,7 @@ One variation uses JDO as the ORM, the other uses JPA, so you can focus on which
The application is also deployed online for you to try out, link:https://simpleapp.jdo.causeway.incode.work[here (jdo)] and link:https://simpleapp.jpa.causeway.incode.work[here (jpa)].
-As with the xref:docs:starters:helloworld.adoc[HelloWorld] starter app, the instructions <<Downloading & Running,below>> will download a minimal Apache Isis app consisting of a single entity (`SimpleObject`) with supporting domain services.
+As with the xref:docs:starters:helloworld.adoc[HelloWorld] starter app, the instructions <<Downloading & Running,below>> will download a minimal Apache Causeway app consisting of a single entity (`SimpleObject`) with supporting domain services.
However, unlike HelloWorld, this app also provides more structure to assist you as your application grows, with business logic placed in a separate Maven module (`simpleapp-...-module-simple`) to the module that bootstraps the webapp (`simpleapp-...-webapp`).
Replace "..." with either "jdo" or "jpa", as appropriate.
@@ -29,11 +29,11 @@ You can use them as a reference once your ideas have solidifid and you need to s
== Prerequisites
-Apache Isis is a Java based framework, so in terms of prerequisites, you'll need to install:
+Apache Causeway is a Java based framework, so in terms of prerequisites, you'll need to install:
* Java 11 JDK (or later)
+
-Apache Isis itself is compatible with Java 11, and the simpleapp itself is configured for Java 11.
+Apache Causeway itself is compatible with Java 11, and the simpleapp itself is configured for Java 11.
* link:http://maven.apache.org[Apache Maven] 3.5+
@@ -289,7 +289,7 @@ image::simpleapp/using/250-retrieve-object-using-rest-api-response.png[width="60
The Swagger UI is provided as a convenience; the REST API is actually a complete hypermedia API (in other words you can follow the links to access all the behaviour exposed in the regular Wicket app).
-The REST API implemented by Apache Isis is specified in the link:http://www.restfulobjects.org[Restful Object spec].
+The REST API implemented by Apache Causeway is specified in the link:http://www.restfulobjects.org[Restful Object spec].
@@ -352,7 +352,7 @@ For integration tests, this uses the link:https://docs.spring.io/spring-boot/doc
These two different annotations reference a (class annotated with) link:https://docs.spring.io/spring-framework/docs/current/javadoc-api/org/springframework/context/annotation/Configuration.html[@Configuration], which in turn can link:https://docs.spring.io/spring-framework/docs/current/javadoc-api/org/springframework/context/annotation/Import.html[@Import] other annotations.
-By convention, the top-level `@Configuration` in an Apache Isis application is called the "app manifest".
+By convention, the top-level `@Configuration` in an Apache Causeway application is called the "app manifest".
The link:{attachmentsdir}/simpleapp-modules-dependencies.pptx[diagram] below shows how classes fit together:
@@ -417,7 +417,7 @@ This is discussed in more detail below.
==== SimpleModule
-Every module within an Apache Isis application should have a module class.
+Every module within an Apache Causeway application should have a module class.
Its purpose is to define a package to scan from, and optionally to declare any transitive dependencies.
In the case of `SimpleModule`, it consists of:
@@ -484,7 +484,7 @@ Since the module dependency graph is known, this allows all data to be removed,
This Spring Boot feature is used by the framework, but can equally easily be used by application code.
The `@Name.Specification` class uses this configuration property.
-The scanning mechanism is also leveraged by Apache Isis to pick up three types of classes:
+The scanning mechanism is also leveraged by Apache Causeway to pick up three types of classes:
* all domain services
+
@@ -589,7 +589,7 @@ public abstract class SimpleModuleIntegTestAbstract
<.> Tests typically inherit from `IsisIntegrationTestAbstract`, which provides some convenience methods to inherit from.
In this case, the test inherits from the `IsisIntegrationTestAbstractWithFixtures` subclass which also adds in support for running fixtures.
-<.> Specifies the modules that make up Apache Isis framework itself.
+<.> Specifies the modules that make up Apache Causeway framework itself.
These include core, security set to the bypass implementation (effectively is ignored) and JDO/DataNucleus for persistence.
Note that no viewers are bootstrapped because the tests are run through Spring's integration testing framework, rather than (say) as Selenium tests.
@@ -662,11 +662,11 @@ This integrates with Spring Boot's link:https://docs.spring.io/spring-boot/docs/
+
Discussed in more detail below.
-<.> Demonstrates how to implement a custom REST controller, accessing the domain object model managed by Apache Isis.
+<.> Demonstrates how to implement a custom REST controller, accessing the domain object model managed by Apache Causeway.
-<.> Demonstrates how to run quartz as a background service, accessing the domain object model managed by Apache Isis.
+<.> Demonstrates how to run quartz as a background service, accessing the domain object model managed by Apache Causeway.
-<.> `AppManifest` is the top-level Spring link:https://docs.spring.io/spring-framework/docs/current/javadoc-api/org/springframework/context/annotation/Configuration.html[@Configuration] that specifies the components of Apache Isis to use, along with the modules making up the application itself (ie `ApplicationModule`, which depends in turn on `SimpleModule`, and `CustomModule`).
+<.> `AppManifest` is the top-level Spring link:https://docs.spring.io/spring-framework/docs/current/javadoc-api/org/springframework/context/annotation/Configuration.html[@Configuration] that specifies the components of Apache Causeway to use, along with the modules making up the application itself (ie `ApplicationModule`, which depends in turn on `SimpleModule`, and `CustomModule`).
+
This is discussed in more detail below
@@ -732,7 +732,7 @@ public class AppManifest {
}
----
-<.> Mandatory - specifies the core of the Apache Isis framework
+<.> Mandatory - specifies the core of the Apache Causeway framework
<.> Enables the Shiro security mechanism.
There are several security implementations, precisely one must be selected
@@ -829,7 +829,7 @@ This leverages a feature in Spring Boot's Flyway integration which allows differ
<.> The `banner.txt` is shown when bootstrapping.
-<.> The `log4j2-spring.xml` configures log4j2 (the logging system used by Apache Isis)
+<.> The `log4j2-spring.xml` configures log4j2 (the logging system used by Apache Causeway)
<.> The `menubars.layout.xml` arranges the actions of the domain services into menus.
@@ -854,7 +854,7 @@ JQuery is available by default.
=== No src/main/webapp
-Note that there is no `src/main/webapp/` or `WEB-INF/web.xml` - the servlets and filters are configured by Apache Isis automatically.
+Note that there is no `src/main/webapp/` or `WEB-INF/web.xml` - the servlets and filters are configured by Apache Causeway automatically.
[#integration-tests]
@@ -927,7 +927,7 @@ This means:
* the set of third party dependencies declared have been validated as compatible by Spring Boot team
* build plugins are declared and configured appropriately
-* imports to the Apache Isis dependencies are declared via `<dependencyManagement>`
+* imports to the Apache Causeway dependencies are declared via `<dependencyManagement>`
diff --git a/testing/adoc/modules/ROOT/pages/about.adoc b/testing/adoc/modules/ROOT/pages/about.adoc
index 768abe371e..00cdcd0510 100644
--- a/testing/adoc/modules/ROOT/pages/about.adoc
+++ b/testing/adoc/modules/ROOT/pages/about.adoc
@@ -2,10 +2,10 @@
: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 [...]
-If you are using Apache Isis to develop complex business-critical applications, then being able to write automated tests for those applications is massively important.
-As such Apache Isis treats the topic of testing very seriously.
+If you are using Apache Causeway to develop complex business-critical applications, then being able to write automated tests for those applications is massively important.
+As such Apache Causeway treats the topic of testing very seriously.
-This guide describes those features available to you for testing your Apache Isis application.
+This guide describes those features available to you for testing your Apache Causeway application.
== Unit tests vs Integ tests
@@ -34,7 +34,7 @@ Unit tests ensure that you are *_building the system right_*.
====
Integration tests leverage Spring Boot's integration testing infrastructure,in particular using link:https://docs.spring.io/spring-boot/docs/current/api/org/springframework/boot/test/context/SpringBootTest.html[@SpringBootTest].
-This configures and bootstraps the Apache Isis runtime, usually running against an in-memory database.
+This configures and bootstraps the Apache Causeway runtime, usually running against an in-memory database.
== Integ tests vs BDD Specs
@@ -59,8 +59,8 @@ But if you don't then you certainly should write integration tests: acceptance c
When we talk about integration tests/specs here, we mean tests that exercise the domain object logic, through to the actual database.
But we also want the tests to exercise the app from the users's perspective, which means including the user interface.
-For most other frameworks that would require having to test the application in a very heavy weight/fragile fashion using a tool such as link:http://docs.seleniumhq.org/[Selenium], driving a web browser to navigate . In this regard though, Apache Isis has a significant trick up its sleeve.
-Because Apache Isis implements the naked objects pattern, it means that the UI is generated automatically from declared domain-objects, -views and -services.
+For most other frameworks that would require having to test the application in a very heavy weight/fragile fashion using a tool such as link:http://docs.seleniumhq.org/[Selenium], driving a web browser to navigate . In this regard though, Apache Causeway has a significant trick up its sleeve.
+Because Apache Causeway implements the naked objects pattern, it means that the UI is generated automatically from declared domain-objects, -views and -services.
This therefore allows for other implementations of the UI.
The xref:refguide:applib:index/services/wrapper/WrapperFactory.adoc[WrapperFactory] domain service allows a test to wrap domain objects and thus to interact with said objects "as if" through the UI:
@@ -72,12 +72,12 @@ If the test invokes an action that is disabled, then the wrapper will throw an a
If the action is ok to invoke, it delegates through.
There's more discussion on the wrapper factory in the xref:testing:integtestsupport:about.adoc#wrapper-factory[integ test support] chapter.
-What this means is that an Apache Isis application can be tested end-to-end without having to deploy it onto a webserver; the whole app can be tested while running in-memory.
+What this means is that an Apache Causeway application can be tested end-to-end without having to deploy it onto a webserver; the whole app can be tested while running in-memory.
Although integration tests re (necessarily) slower than unit tests, they are not any harder to write (in fact, in some respects they are easier).
== Dependency Injection
-Spring Boot will automatically inject dependencies into integration tests and services, and Apache Isis extends this to also inject services into every domain object (entity or view model).
+Spring Boot will automatically inject dependencies into integration tests and services, and Apache Causeway extends this to also inject services into every domain object (entity or view model).
This is most useful when writing unit tests; simply mock out the service and inject into the domain object.
There are a number of syntaxes supported, but the simplest is to use `@javax.inject.Inject` annotation; for example:
@@ -89,7 +89,7 @@ CustomerRepository customers;
----
Domain services are discovered by Spring Boot, either explicitly referenced in the link:https://docs.spring.io/spring-framework/docs/current/javadoc-api/org/springframework/context/annotation/Import.html[@Import] annotation, or picked up from class path scanning of link:https://docs.spring.io/spring-framework/docs/current/javadoc-api/org/springframework/context/annotation/ComponentScan.html[@ComponentScan].
-Any service annotated or meta-annotated with link:https://docs.spring.io/spring-framework/docs/current/javadoc-api/org/springframework/stereotype/Component.html[@Component] can be discovered; this includes classes annotated with Apache Isis' xref:refguide:applib:index/annotation/DomainService.adoc[@DomainService].
+Any service annotated or meta-annotated with link:https://docs.spring.io/spring-framework/docs/current/javadoc-api/org/springframework/stereotype/Component.html[@Component] can be discovered; this includes classes annotated with Apache Causeway' xref:refguide:applib:index/annotation/DomainService.adoc[@DomainService].
== Given/When/Then
@@ -116,14 +116,14 @@ In the previous section we discussed using given/when/then as a form of organizi
For integration tests though it can be difficult to keep the "given" short; there could be a lot of prerequisite data that needs to exist before you can actually exercise your system.
Moreover, however we do set up that data, but we also want to do so in a way that is resilient to the system changing over time.
-The solution that Apache Isis provides is xref:testing:fixtures:about.adoc[fixture scripts], supported by a domain service (also) called xref:refguide:testing:index/fixtures/applib/fixturescripts/FixtureScripts.adoc[FixtureScripts].
+The solution that Apache Causeway provides is xref:testing:fixtures:about.adoc[fixture scripts], supported by a domain service (also) called xref:refguide:testing:index/fixtures/applib/fixturescripts/FixtureScripts.adoc[FixtureScripts].
This defines a pattern (command pattern and composite pattern) with supporting classes to help ensure that the "data setup" for your tests are reusable and maintainable over time.
== Fake data
include::testing:fakedata:partial$intro.adoc[]
-Apache Isis provides the xref:testing:fakedata:about.adoc[Fake Data] library to assist with this.
+Apache Causeway provides the xref:testing:fakedata:about.adoc[Fake Data] library to assist with this.
[TIP]
====
diff --git a/testing/archtestsupport/adoc/modules/archtestsupport/pages/about.adoc b/testing/archtestsupport/adoc/modules/archtestsupport/pages/about.adoc
index 09a04c0d99..d811b380bd 100644
--- a/testing/archtestsupport/adoc/modules/archtestsupport/pages/about.adoc
+++ b/testing/archtestsupport/adoc/modules/archtestsupport/pages/about.adoc
@@ -3,7 +3,7 @@
: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 [...]
-Apache Isis provides a library of link:https://www.archunit.org/[ArchUnit] tests to verify the structure of your domain applications.
+Apache Causeway provides a library of link:https://www.archunit.org/[ArchUnit] tests to verify the structure of your domain applications.
== Maven Configuration
@@ -239,7 +239,7 @@ For teams that insist on business keys in addition to surrogate keys
* Optional
-** ensure conformance of persistence vs Isis annotations
+** ensure conformance of persistence vs Causeway annotations
+
For teams that like to emphasise entities vs view models:
diff --git a/testing/fixtures/adoc/modules/fixtures/pages/about.adoc b/testing/fixtures/adoc/modules/fixtures/pages/about.adoc
index 8180332127..341686436e 100644
--- a/testing/fixtures/adoc/modules/fixtures/pages/about.adoc
+++ b/testing/fixtures/adoc/modules/fixtures/pages/about.adoc
@@ -13,11 +13,11 @@ If in the future the domain entities (and therefore corresponding database table
Even more significantly, there's no way to guarantee that the data that's being loaded is logically consistent with the business behaviour of the domain objects themselves.
That is, there's nothing to stop your test from putting data into the database that would be invalid if one attempted to add it through the app.
-The solution that Apache Isis provides is a small library called *_fixture scripts_*.
+The solution that Apache Causeway provides is a small library called *_fixture scripts_*.
A fixture script is basically a command object for executing arbitrary work, where the work in question is almost always invoking one or more business actions.
In other words, the database is populating through the functionality of the domain object model itself.
-There is another benefit to Apache Isis' fixture script approach; the fixtures can be (in prototyping mode) run from your application.
+There is another benefit to Apache Causeway' fixture script approach; the fixtures can be (in prototyping mode) run from your application.
This means that fixture scripts can actually help all the way through the development lifecycle:
* when specifying a new feature, you can write a fixture script to get the system into the "given" state, and then start exploring the required functionality with the domain expert actually _within_ the application +
diff --git a/testing/integtestsupport/adoc/modules/integtestsupport/pages/about.adoc b/testing/integtestsupport/adoc/modules/integtestsupport/pages/about.adoc
index edf95c3b86..e879101490 100644
--- a/testing/integtestsupport/adoc/modules/integtestsupport/pages/about.adoc
+++ b/testing/integtestsupport/adoc/modules/integtestsupport/pages/about.adoc
@@ -2,8 +2,8 @@
: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 [...]
-Apache Isis builds on top of Spring Boot's integration testing support, in particular using link:https://docs.spring.io/spring-boot/docs/current/api/org/springframework/boot/test/context/SpringBootTest.html[@SpringBootTest].
-This configures and bootstraps the Apache Isis runtime, usually running against an in-memory database.
+Apache Causeway builds on top of Spring Boot's integration testing support, in particular using link:https://docs.spring.io/spring-boot/docs/current/api/org/springframework/boot/test/context/SpringBootTest.html[@SpringBootTest].
+This configures and bootstraps the Apache Causeway runtime, usually running against an in-memory database.
On top of that, we usually:
@@ -94,7 +94,7 @@ public class AppManifest {
[#bootstrapping]
== Bootstrapping
-We typically put the bootstrapping of Apache Isis into a superclass, one for each Maven module.
+We typically put the bootstrapping of Apache Causeway into a superclass, one for each Maven module.
This allows an individual "slice" of the application to be tested, rather than as a monolith.
So, for the `module-simple` module, we have:
@@ -163,7 +163,7 @@ They both also force an in-memory database, with JDO/DataNucleus ORM configured
=== Faster bootstrapping
By default integration tests are run in "production" deployment mode.
-With the `causeway.core.meta-model.introspector.mode=` set to its default value, this results in full introspection of the Apache Isis metamodel.
+With the `causeway.core.meta-model.introspector.mode=` set to its default value, this results in full introspection of the Apache Causeway metamodel.
While this _does_ have the benefit that the metamodel will be validated, the downside is that the test takes longer to bootstrap.
@@ -228,7 +228,7 @@ public class SimpleObject
Properties are visible but unmodifiable by default
We therefore have two tests for each of these facts.
-NOTE: Non-editable properties is change from Isis v1.x.
+NOTE: Non-editable properties is change from Causeway v1.x.
Use the `causeway.applib.annotation.domain-object.editing` configuration property to pverride.
By convention, we group tests into nested static classes, so the corresponding integration test is:
@@ -477,7 +477,7 @@ This is usually done in the test's `setUp()` method.
. the test calls the methods on the wrapper rather than the domain object itself
-. the wrapper performs a reverse lookup from the method invoked (a regular `java.lang.reflect.Method` instance) into the Apache Isis metamodel
+. the wrapper performs a reverse lookup from the method invoked (a regular `java.lang.reflect.Method` instance) into the Apache Causeway metamodel
. (like a viewer), the wrapper then performs the "see it/use it/do it" checks, checking that the member is visible, that it is enabled and (if there are arguments) that the arguments are valid
diff --git a/testing/specsupport/adoc/modules/specsupport/pages/about.adoc b/testing/specsupport/adoc/modules/specsupport/pages/about.adoc
index e2f00b9cb6..88d5da2c93 100644
--- a/testing/specsupport/adoc/modules/specsupport/pages/about.adoc
+++ b/testing/specsupport/adoc/modules/specsupport/pages/about.adoc
@@ -12,7 +12,7 @@ The BDD tooling parses this text and uses it to actually interact with the syste
As a byproduct the BDD frameworks generate readable output of some form; this is often an annotated version of the original specification, marked up to indicate which specifications passed, which have failed.
This readable output is a form of "living documentation"; it captures the actual behaviour of the system, and so is guaranteed to be accurate.
-There are many BDD tools out there; Apache Isis provides an integration with link:https://cucumber.io/docs/installation/java/[Cucumber JVM] (see also the https://github.com/cucumber/cucumber-jvm[github site]):
+There are many BDD tools out there; Apache Causeway provides an integration with link:https://cucumber.io/docs/installation/java/[Cucumber JVM] (see also the https://github.com/cucumber/cucumber-jvm[github site]):
== How it works
diff --git a/testing/unittestsupport/adoc/modules/unittestsupport/pages/about.adoc b/testing/unittestsupport/adoc/modules/unittestsupport/pages/about.adoc
index d2969da92b..303b948902 100644
--- a/testing/unittestsupport/adoc/modules/unittestsupport/pages/about.adoc
+++ b/testing/unittestsupport/adoc/modules/unittestsupport/pages/about.adoc
@@ -2,7 +2,7 @@
: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 [...]
-Apache Isis provides a number of helpers to help unit test your domain objects.
+Apache Causeway provides a number of helpers to help unit test your domain objects.
== Maven Configuration
@@ -231,7 +231,7 @@ As here, it is often sufficient to provide a single instance (as it is compared
=== XML Marshalling Support
-Apache Isis' unit testing support provides the xref:refguide:testing:index/unittestsupport/applib/matchers/JaxbMatchers.adoc[JaxbMatchers] while the core applib also provides the useful xref:refguide:applib:index/util/JaxbUtil.adoc[JaxbUtil] class.
+Apache Causeway' unit testing support provides the xref:refguide:testing:index/unittestsupport/applib/matchers/JaxbMatchers.adoc[JaxbMatchers] while the core applib also provides the useful xref:refguide:applib:index/util/JaxbUtil.adoc[JaxbUtil] class.
These can be useful for example if you have example XML-serialized representations of the SOAP requests and response payloads and want to use these within your tests.
@@ -256,7 +256,7 @@ If using JMock then the interactions (in the "then") are checked automatically b
However, you probably will still have some state changes to assert upon.
-Apache Isis' unit test support provides `JUnitRuleMockery2` which is an extension to the link:http://www.jmock.org/[JMock]'s `JunitRuleMockery`.
+Apache Causeway' unit test support provides `JUnitRuleMockery2` which is an extension to the link:http://www.jmock.org/[JMock]'s `JunitRuleMockery`.
It provides a simpler API and also providing support for autowiring.
diff --git a/tooling/cli/adoc/modules/tooling-cli/pages/about.adoc b/tooling/cli/adoc/modules/tooling-cli/pages/about.adoc
index 665d03857e..a399392851 100644
--- a/tooling/cli/adoc/modules/tooling-cli/pages/about.adoc
+++ b/tooling/cli/adoc/modules/tooling-cli/pages/about.adoc
@@ -3,7 +3,7 @@
: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 [...]
-Command Line Interface for the _Apache Isis Tooling_ ecosystem, to generate documentation from program sources (`.java` files, `pom.xml`, etc).
+Command Line Interface for the _Apache Causeway Tooling_ ecosystem, to generate documentation from program sources (`.java` files, `pom.xml`, etc).
@@ -34,7 +34,7 @@ which (currently) generates the following:
[source]
----
Usage: cli [-hV] [-o=<outputPath>] [-p=<projectRootPath>] [COMMAND]
-CLI for the Apache Isis Tooling Ecosystem
+CLI for the Apache Causeway Tooling Ecosystem
-h, --help Show this help message and exit.
-w, --overview=<overviewPath>
path to write the overview file (default: NONE = write to std.out)
diff --git a/viewers/restfulobjects/adoc/modules/ROOT/pages/about.adoc b/viewers/restfulobjects/adoc/modules/ROOT/pages/about.adoc
index fa38a4a453..3254d0d7d7 100644
--- a/viewers/restfulobjects/adoc/modules/ROOT/pages/about.adoc
+++ b/viewers/restfulobjects/adoc/modules/ROOT/pages/about.adoc
@@ -3,9 +3,9 @@
: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 [...]
-Apache Isis' Restful Objects viewer is an implementation of the link:http://restfulobjects.org[Restful Objects spec], which defines a generic way to expose a domain model through a REST (or more precisely, hypermedia) API. Having a REST API opens up an Apache Isis domain model to a huge variety of applications, from bespoke single-page apps, through integration scenarios, through providing an API for bulk-upload/migration from an existing system.
+Apache Causeway' Restful Objects viewer is an implementation of the link:http://restfulobjects.org[Restful Objects spec], which defines a generic way to expose a domain model through a REST (or more precisely, hypermedia) API. Having a REST API opens up an Apache Causeway domain model to a huge variety of applications, from bespoke single-page apps, through integration scenarios, through providing an API for bulk-upload/migration from an existing system.
-The Restful Objects viewer also provides a number of extensions specific to Apache Isis.
+The Restful Objects viewer also provides a number of extensions specific to Apache Causeway.
Most significant of these is enhanced content negotiation support, making it easier to use the returned representations within bespoke clients using standard third-party configurations.
This component guide discuss features, configuration and also how to extend the Restful Objects viewer.
diff --git a/viewers/restfulobjects/adoc/modules/ROOT/pages/client.adoc b/viewers/restfulobjects/adoc/modules/ROOT/pages/client.adoc
index 7d54c6a8a7..498c069f50 100644
--- a/viewers/restfulobjects/adoc/modules/ROOT/pages/client.adoc
+++ b/viewers/restfulobjects/adoc/modules/ROOT/pages/client.adoc
@@ -2,7 +2,7 @@
: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 [...]
-This library is for integration scenario to programmatically invoke the xref:vro::about.adoc[REST API (Restful Objects Viewer)] of an Apache Isis application, using the link:http://restfulobjects.org[restfulobjects protocol].
+This library is for integration scenario to programmatically invoke the xref:vro::about.adoc[REST API (Restful Objects Viewer)] of an Apache Causeway application, using the link:http://restfulobjects.org[restfulobjects protocol].
A common use case would be to consume information from some external system, for example uploading a scanned PDF or a representation of an incoming invoice.
diff --git a/viewers/restfulobjects/adoc/modules/ROOT/pages/content-negotiation.adoc b/viewers/restfulobjects/adoc/modules/ROOT/pages/content-negotiation.adoc
index f05527a73e..2aa6ada1bb 100644
--- a/viewers/restfulobjects/adoc/modules/ROOT/pages/content-negotiation.adoc
+++ b/viewers/restfulobjects/adoc/modules/ROOT/pages/content-negotiation.adoc
@@ -18,7 +18,7 @@ If the entities were exposed directly then those REST clients will break.
Instead you need to create some sort of stable facade over your domain entities, one which you will preserve even if the domain entities change.
There are three ways in which you can do this:
-* first is to solve the problem at the domain layer by defining a regular Apache Isis xref:userguide:fun:overview.adoc#view-models[view model].
+* first is to solve the problem at the domain layer by defining a regular Apache Causeway xref:userguide:fun:overview.adoc#view-models[view model].
This is then surfaced by the RO viewer.
+
If the underlying entities change, then care must be taken to ensure that structure of the view model nevertheless is unchanged.
@@ -32,7 +32,7 @@ If the underlying tables change (as the result of a change in their correspondin
+
The `ContentNegotiationService` is responsible for inspecting the HTTP `Accept` header, and use this to select the correct representation to render.
+
-The Apache Isis framework provides three implementations of `ContentNegotiationService` which inspects different elements of the HTTP `Accept` header.
+The Apache Causeway framework provides three implementations of `ContentNegotiationService` which inspects different elements of the HTTP `Accept` header.
One of these implementations, `ContentNegotiationServiceXRoDomainType` will further delegate down to the companion xref:refguide:applib:index/services/conmap/ContentMappingService.adoc[ContentMappingService] service (if configured/available), based on the value of the "x-ro-domain-type" parameter of the header.
+
A typical implementation of `ContentMappingService` will convert the domain object into some sort of DTO (data transfer object) as specified by the "x-ro-domaintype".
@@ -54,7 +54,7 @@ xref:refguide:viewer:index/restfulobjects/rendering/service/conneg/ContentNegoti
If the implementation does not recognize the value of the header, if can simply return `null`.
+
The framework provides a number of implementations; an implementation that handles the
-xref:vro:ROOT:content-negotiation/apache-causeway-v2-profile.adoc[simplified representation] of the Apache Isis profile; an implementation that provides support for the `x-ro-domain-type` parameter, and a default/fallback implementation that returns the representations defined by the RO spec.
+xref:vro:ROOT:content-negotiation/apache-causeway-v2-profile.adoc[simplified representation] of the Apache Causeway profile; an implementation that provides support for the `x-ro-domain-type` parameter, and a default/fallback implementation that returns the representations defined by the RO spec.
* xref:refguide:applib:index/services/conmap/ContentMappingService.adoc[ContentMappingService]
+
diff --git a/viewers/restfulobjects/adoc/modules/ROOT/pages/content-negotiation/apache-isis-v2-profile.adoc b/viewers/restfulobjects/adoc/modules/ROOT/pages/content-negotiation/apache-isis-v2-profile.adoc
index c36bf43336..d508529145 100644
--- a/viewers/restfulobjects/adoc/modules/ROOT/pages/content-negotiation/apache-isis-v2-profile.adoc
+++ b/viewers/restfulobjects/adoc/modules/ROOT/pages/content-negotiation/apache-isis-v2-profile.adoc
@@ -1,5 +1,5 @@
[#apache-causeway-v2-profile-simplified-representation]
-= Apache Isis v2 Profile (Simplified Representation)
+= Apache Causeway v2 Profile (Simplified Representation)
: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 [...]
@@ -7,7 +7,7 @@
The representations defined by the RO spec are very rich and enable complex client-side applications to be built.
However, their sophistication can be an impediment to their use if one wishes to write a simple app using third-party components that expect to consume much simpler representations.
-Apache Isis also provides support for its own simplified representation for the most commonly-used representations.
+Apache Causeway also provides support for its own simplified representation for the most commonly-used representations.
This is implemented using the xref:refguide:viewer:index/restfulobjects/rendering/service/conneg/ContentNegotiationService.adoc[ContentNegotiationService] described in the
xref:vro:ROOT:content-negotiation.adoc[architecture] chapter.
diff --git a/viewers/restfulobjects/adoc/modules/ROOT/pages/content-negotiation/other-representations.adoc b/viewers/restfulobjects/adoc/modules/ROOT/pages/content-negotiation/other-representations.adoc
index e30d7adb6e..5ef7f2395d 100644
--- a/viewers/restfulobjects/adoc/modules/ROOT/pages/content-negotiation/other-representations.adoc
+++ b/viewers/restfulobjects/adoc/modules/ROOT/pages/content-negotiation/other-representations.adoc
@@ -8,7 +8,7 @@
Sometimes though you may want to extend or change the representations generated.
This might be because you want to write a RESTful client that uses a particular library (say a JavaScript library or web components) that can only handle representations in a certain form.
-Or, you might want to have Apache Isis generate representations according to some other "standard", of which there are many:
+Or, you might want to have Apache Causeway generate representations according to some other "standard", of which there are many:
* Mike Kelly's http://stateless.co/hal_specification.html[HAL] specification
* Mike Amundsen's http://amundsen.com/media-types/collection/[Collection+JSON] specification
@@ -28,7 +28,7 @@ The existing implementations can be used as a starting point.
[CAUTION]
====
-Any custom implementations will need to access the internal APIs for the Apache Isis metamodel.
+Any custom implementations will need to access the internal APIs for the Apache Causeway metamodel.
You should be aware that these are not formal API.
====
diff --git a/viewers/restfulobjects/adoc/modules/ROOT/pages/content-negotiation/simplified-representations/accept-header.adoc b/viewers/restfulobjects/adoc/modules/ROOT/pages/content-negotiation/simplified-representations/accept-header.adoc
index 96b192e309..46940b934f 100644
--- a/viewers/restfulobjects/adoc/modules/ROOT/pages/content-negotiation/simplified-representations/accept-header.adoc
+++ b/viewers/restfulobjects/adoc/modules/ROOT/pages/content-negotiation/simplified-representations/accept-header.adoc
@@ -15,7 +15,7 @@ Accept: application/json;profile="urn:org.restfulobjects:repr-types/xxx"
where "xxx" varies by resource.
The detail can be found in link:https://www.restfulobjects.org/spec/1.0/section-a/chapter-02.html#_2-4-1-representationtype-profile-parameter[section 2.4.1] of the RO spec.
-The "Isis" profile allows the client to request simplified representations for the most frequently accessed resources.
+The "Causeway" profile allows the client to request simplified representations for the most frequently accessed resources.
This is done by specifying an `Accept` header of:
[source]
diff --git a/viewers/restfulobjects/adoc/modules/ROOT/pages/content-negotiation/simplified-representations/configuration-properties.adoc b/viewers/restfulobjects/adoc/modules/ROOT/pages/content-negotiation/simplified-representations/configuration-properties.adoc
index 95db0fe6e4..72f3bed11b 100644
--- a/viewers/restfulobjects/adoc/modules/ROOT/pages/content-negotiation/simplified-representations/configuration-properties.adoc
+++ b/viewers/restfulobjects/adoc/modules/ROOT/pages/content-negotiation/simplified-representations/configuration-properties.adoc
@@ -7,9 +7,9 @@
If all that is required is a very simple representations (of objects), you can configure the Restful Objects viewer
to provide a simplified output, then this can be done with a number of (global) configuration properties.
-These configuration properties pre-date the support for the Apache Isis profile, and
+These configuration properties pre-date the support for the Apache Causeway profile, and
are limited by the fact that they are global configuration settings, so cannot be influenced on a request-by-request
-basis (as is the case with the `Accept` header used for the Apache Isis profile). They have therefore been
+basis (as is the case with the `Accept` header used for the Apache Causeway profile). They have therefore been
deprecated, and may be removed in the future.
Details can be found in xref:vro:ROOT:setup-and-configuration.adoc#deprecated[here].
diff --git a/viewers/restfulobjects/adoc/modules/ROOT/pages/content-negotiation/simplified-representations/domain-object.adoc b/viewers/restfulobjects/adoc/modules/ROOT/pages/content-negotiation/simplified-representations/domain-object.adoc
index 22e9fd9e99..4efa52f428 100644
--- a/viewers/restfulobjects/adoc/modules/ROOT/pages/content-negotiation/simplified-representations/domain-object.adoc
+++ b/viewers/restfulobjects/adoc/modules/ROOT/pages/content-negotiation/simplified-representations/domain-object.adoc
@@ -6,7 +6,7 @@
:dollar: $
-If a domain object resource (link:https://www.restfulobjects.org/spec/1.0/section-c/chapter-14.html[section 14]) is accessed with the Apache Isis profile, the resultant representation is a JSON object with simple key/value pairs for each property.
+If a domain object resource (link:https://www.restfulobjects.org/spec/1.0/section-c/chapter-14.html[section 14]) is accessed with the Apache Causeway profile, the resultant representation is a JSON object with simple key/value pairs for each property.
The contents of any collections are also eagerly returned, consisting of an array of elements of each referenced object.
Each such element contains key/value pairs of each property (in other words, a grid of data is returned).
diff --git a/viewers/restfulobjects/adoc/modules/ROOT/pages/hints-and-tips.adoc b/viewers/restfulobjects/adoc/modules/ROOT/pages/hints-and-tips.adoc
index 1afccd85a9..18f5f1b233 100644
--- a/viewers/restfulobjects/adoc/modules/ROOT/pages/hints-and-tips.adoc
+++ b/viewers/restfulobjects/adoc/modules/ROOT/pages/hints-and-tips.adoc
@@ -4,7 +4,7 @@
: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 [...]
-This chapter provides some solutions for problems we've encountered ourselves or have been raised on the Apache Isis mailing lists.
+This chapter provides some solutions for problems we've encountered ourselves or have been raised on the Apache Causeway mailing lists.
Since the Restful Objects viewer is designed for computer programs to interact with (rather than human beings), it can be a little difficult to explore and generally "grok" how it works.
diff --git a/viewers/restfulobjects/adoc/modules/ROOT/pages/hints-and-tips/restful-image-property.adoc b/viewers/restfulobjects/adoc/modules/ROOT/pages/hints-and-tips/restful-image-property.adoc
index a84cfca701..6556b05db9 100644
--- a/viewers/restfulobjects/adoc/modules/ROOT/pages/hints-and-tips/restful-image-property.adoc
+++ b/viewers/restfulobjects/adoc/modules/ROOT/pages/hints-and-tips/restful-image-property.adoc
@@ -4,10 +4,10 @@
: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 [...]
-From this link:http://markmail.org/message/4kcu7sml4ufdsah3[thread] on the Apache Isis users mailing list:
+From this link:http://markmail.org/message/4kcu7sml4ufdsah3[thread] on the Apache Causeway users mailing list:
* _I am trying to display an image in a JavaScript client app, the image comes from
- an Isis RO web service as a string, but it won't show.
+ an Causeway RO web service as a string, but it won't show.
Is there something I should do to change the message?_
diff --git a/viewers/restfulobjects/adoc/modules/ROOT/pages/layout-resources.adoc b/viewers/restfulobjects/adoc/modules/ROOT/pages/layout-resources.adoc
index b55445195d..f317354f0f 100644
--- a/viewers/restfulobjects/adoc/modules/ROOT/pages/layout-resources.adoc
+++ b/viewers/restfulobjects/adoc/modules/ROOT/pages/layout-resources.adoc
@@ -3,7 +3,7 @@
: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 [...]
-Apache Isis' Restful Objects viewer provides a number of additional resource endpoints (not defined in the xref:ro-spec.adoc[RO spec]) that provide representations of the object layout (as per xref:refguide:applib:index/services/grid/GridService.adoc[GridService]) and of the menu layout (as per xref:refguide:applib:index/services/menu/MenuBarsService.adoc[MenuBarsService]).
+Apache Causeway' Restful Objects viewer provides a number of additional resource endpoints (not defined in the xref:ro-spec.adoc[RO spec]) that provide representations of the object layout (as per xref:refguide:applib:index/services/grid/GridService.adoc[GridService]) and of the menu layout (as per xref:refguide:applib:index/services/menu/MenuBarsService.adoc[MenuBarsService]).
This chapter provides details of these resources, the link ``Rel``s to access them, and the resultant representations.
diff --git a/viewers/restfulobjects/adoc/modules/ROOT/pages/ro-spec.adoc b/viewers/restfulobjects/adoc/modules/ROOT/pages/ro-spec.adoc
index 6d142cee95..d16c023a08 100644
--- a/viewers/restfulobjects/adoc/modules/ROOT/pages/ro-spec.adoc
+++ b/viewers/restfulobjects/adoc/modules/ROOT/pages/ro-spec.adoc
@@ -37,13 +37,13 @@ The diagram below - taken from the Restful Objects spec - shows the various reso
image::restfulobjects/ro-spec-resources-and-representations.png[width="800px"]
-The resource URLs are always well-defined, but Apache Isis' implementation allows for different representations to be returned, using content negotiation.
+The resource URLs are always well-defined, but Apache Causeway' implementation allows for different representations to be returned, using content negotiation.
This is discussed further below.
-== Apache Isis' implementation
+== Apache Causeway' implementation
-The Restful Objects viewer is Apache Isis' implementation of the Restful Objects spec.
+The Restful Objects viewer is Apache Causeway' implementation of the Restful Objects spec.
It implements all the mandatory features of the specification.
It also implements some of the optional capabilities (as defined in link:https://www.restfulobjects.org/spec/1.0/section-a/chapter-03.html[section 3] of the RO spec, and as represented in the version resource, section 8.1):
@@ -84,7 +84,7 @@ The Restful Objects viewer also implements some of the "future ideas" that are o
=== Content Negotiation
-Apache Isis provides two levels of support for content negotiation (section link:http://www.restfulobjects.org/spec/1.0/section-e/chapter-34.html#34.1-content-negotiation[34.1])
+Apache Causeway provides two levels of support for content negotiation (section link:http://www.restfulobjects.org/spec/1.0/section-e/chapter-34.html#34.1-content-negotiation[34.1])
==== `x-ro-domain-type`
@@ -103,7 +103,7 @@ Accept: application/xml;x-ro-domain-type="com.mycompany.viewmodels.v2.CustomerVi
The server will use the xref:refguide:applib:index/services/conmap/ContentMappingService.adoc[ContentMappingService] to attempt to transform the domain object into the requested `x-ro-domain-type`.
The whole process is discussed in more detail in the xref:vro:ROOT:content-negotiation.adoc[architecture] chapter.
-==== Apache Isis profile
+==== Apache Causeway profile
The representations defined by the RO spec are very rich and enable complex client-side applications to be built.
However, their sophistication can be an impediment to their use if one wishes to write a simple app using third-party components that expect to consume much simpler representations.
@@ -119,7 +119,7 @@ chapter.
The Restful Objects viewer supports the `x-ro-follow-links` query parameter in a way very similar to that suggested in the RO spec (section link:https://www.restfulobjects.org/spec/1.0/section-e/chapter-34.html#34.4-minimizing-round-trips-(x-ro-follow-links)[34.4]), the main point being to avoid the "N+1" problem of too many (slow) network calls.
For example, using this feature one can load a grid of data in a single call.
-(That said, the xref:vro:ROOT:content-negotiation/apache-causeway-v2-profile.adoc[Apache Isis v2 simplified representation] supported by Restful Objects viewer also support this use case, albeit in way that deviates from the RO spec).
+(That said, the xref:vro:ROOT:content-negotiation/apache-causeway-v2-profile.adoc[Apache Causeway v2 simplified representation] supported by Restful Objects viewer also support this use case, albeit in way that deviates from the RO spec).
For example, with an app containing three entities, `Grandparent`, `Parent` and `ChildJdo` that define a hierarchy of 1:m relationships, we could define the following queries:
@@ -141,10 +141,10 @@ pass:[<pre>http://localhost:8080/restful/objects/CHILD/0?x-ro-follow-links=membe
==== Honor UI hints
-By default the representations generated by Restful Objects ignore any Apache Isis metamodel hints referring to the UI.
+By default the representations generated by Restful Objects ignore any Apache Causeway metamodel hints referring to the UI.
In particular, if a collection is annotated then `Render(EAGERLY)` then the contents of the collection are _not_ eagerly embedded in the object representation.
However, this behaviour can be overridden globally using the
xref:refguide:config:sections/causeway.viewer.restfulobjects.adoc#causeway.viewer.restfulobjects.honor-ui-hints[causeway.viewer.restfulobjects.honor-ui-hints] configuration property:
-This means that standard Apache Isis annotations can be used as a simple way to obtain follow-links (driven from the server model, though, rather than the requesting client).
+This means that standard Apache Causeway annotations can be used as a simple way to obtain follow-links (driven from the server model, though, rather than the requesting client).
diff --git a/viewers/restfulobjects/adoc/modules/ROOT/pages/setup-and-configuration.adoc b/viewers/restfulobjects/adoc/modules/ROOT/pages/setup-and-configuration.adoc
index 894a6aaac1..731c3bbf2d 100644
--- a/viewers/restfulobjects/adoc/modules/ROOT/pages/setup-and-configuration.adoc
+++ b/viewers/restfulobjects/adoc/modules/ROOT/pages/setup-and-configuration.adoc
@@ -53,7 +53,7 @@ Security is discussed in more detail xref:security.adoc[here].
These configuration properties that can be used to suppress or simplify the default RO-spec representations.
-These configuration properties pre-date the support for the link:content-negotiation/simplified-representations/[Apache Isis profile], and are limited by the fact that they are global configuration settings, so cannot be influenced on a request-by-request basis (as is the case with the `Accept` header used for the Apache Isis profile).
+These configuration properties pre-date the support for the link:content-negotiation/simplified-representations/[Apache Causeway profile], and are limited by the fact that they are global configuration settings, so cannot be influenced on a request-by-request basis (as is the case with the `Accept` header used for the Apache Causeway profile).
They have therefore been deprecated, and may be removed in the future.
Nevertheless, those configuration properties are:
@@ -75,7 +75,7 @@ Nevertheless, those configuration properties are:
[NOTE]
====
-If these configuration settings are set in conjunction with using the xref:vro:ROOT:content-negotiation/apache-causeway-v2-profile.adoc#apache-causeway-v2-profile-simplified-representation[Apache Isis profile], then the special `$$ro` property in the representations with reflect these settings.
+If these configuration settings are set in conjunction with using the xref:vro:ROOT:content-negotiation/apache-causeway-v2-profile.adoc#apache-causeway-v2-profile-simplified-representation[Apache Causeway profile], then the special `$$ro` property in the representations with reflect these settings.
====
diff --git a/viewers/restfulobjects/adoc/modules/ROOT/partials/module-nav.adoc b/viewers/restfulobjects/adoc/modules/ROOT/partials/module-nav.adoc
index 7d652b9dad..711c3e2215 100644
--- a/viewers/restfulobjects/adoc/modules/ROOT/partials/module-nav.adoc
+++ b/viewers/restfulobjects/adoc/modules/ROOT/partials/module-nav.adoc
@@ -3,7 +3,7 @@
* xref:vro:ROOT:setup-and-configuration.adoc[Setup and Configuration]
* xref:vro:ROOT:ro-spec.adoc[RO Spec]
* xref:vro:ROOT:content-negotiation.adoc[Content Negotiation]
-** xref:vro:ROOT:content-negotiation/apache-causeway-v2-profile.adoc[Apache Isis v2 Profile]
+** xref:vro:ROOT:content-negotiation/apache-causeway-v2-profile.adoc[Apache Causeway v2 Profile]
//** xref:vro:ROOT:content-negotiation/apache-causeway-v2-profile.INCOMPLETE.adoc[Simplified Representations v2]
** xref:vro:ROOT:content-negotiation/other-representations.adoc[Other Representations]
* xref:vro:ROOT:security.adoc[Security]
diff --git a/viewers/wicket/adoc/modules/ROOT/pages/about.adoc b/viewers/wicket/adoc/modules/ROOT/pages/about.adoc
index 2db2f4b32f..bade6e50b9 100644
--- a/viewers/wicket/adoc/modules/ROOT/pages/about.adoc
+++ b/viewers/wicket/adoc/modules/ROOT/pages/about.adoc
@@ -3,7 +3,7 @@
: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 [...]
:page-aliases: guides:ugvw:ugvw.adoc
-The Wicket Viewer automatically exposes an Apache Isis domain object model for use by end-users.
+The Wicket Viewer automatically exposes an Apache Causeway domain object model for use by end-users.
The viewer is implemented using link:http://wicket.apache.org[Apache Wicket].
This component guide discuss end-user features, configuration and customization of the Wicket viewer.
diff --git a/viewers/wicket/adoc/modules/ROOT/pages/customisation/about-page.adoc b/viewers/wicket/adoc/modules/ROOT/pages/customisation/about-page.adoc
index 24d63a62ce..bfe2767fe4 100644
--- a/viewers/wicket/adoc/modules/ROOT/pages/customisation/about-page.adoc
+++ b/viewers/wicket/adoc/modules/ROOT/pages/customisation/about-page.adoc
@@ -4,7 +4,7 @@
-Isis' Wicket viewer has an About page that, accessed by clicking on the application version in the footer.
+Causeway' Wicket viewer has an About page that, accessed by clicking on the application version in the footer.
image::about-page/about-page.png[width="800px"]
diff --git a/viewers/wicket/adoc/modules/ROOT/pages/customisation/custom-javascript.adoc b/viewers/wicket/adoc/modules/ROOT/pages/customisation/custom-javascript.adoc
index 80eba08e0b..17d8506e8c 100644
--- a/viewers/wicket/adoc/modules/ROOT/pages/customisation/custom-javascript.adoc
+++ b/viewers/wicket/adoc/modules/ROOT/pages/customisation/custom-javascript.adoc
@@ -17,7 +17,7 @@ If you wish to change the location of the file, use the xref:refguide:config:sec
[WARNING]
====
Just because something is possible, it doesn't necessarily mean we encourage it.
-Please be aware that there is no formal API for any custom JavaScript that you might implement to target; future versions of Apache Isis might break your code.
+Please be aware that there is no formal API for any custom JavaScript that you might implement to target; future versions of Apache Causeway might break your code.
As an alternative, consider using the `ComponentFactory` API described in the xref:vw:ROOT:extending.adoc[extending] chapter.
====
diff --git a/viewers/wicket/adoc/modules/ROOT/pages/customisation/embedded-view.adoc b/viewers/wicket/adoc/modules/ROOT/pages/customisation/embedded-view.adoc
index 4bf549b202..4e006bb53d 100644
--- a/viewers/wicket/adoc/modules/ROOT/pages/customisation/embedded-view.adoc
+++ b/viewers/wicket/adoc/modules/ROOT/pages/customisation/embedded-view.adoc
@@ -4,7 +4,7 @@
: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 [...]
-The Wicket viewer provides some support such that an Apache Isis application can be embedded within a host webapp, for example within an iframe.
+The Wicket viewer provides some support such that an Apache Causeway application can be embedded within a host webapp, for example within an iframe.
Currently this support consists simply of being able to suppress the header and/or footer.
== Screenshots
diff --git a/viewers/wicket/adoc/modules/ROOT/pages/extending/custom-bootstrap-theme.adoc b/viewers/wicket/adoc/modules/ROOT/pages/extending/custom-bootstrap-theme.adoc
index ab7455ba28..888bf48f89 100644
--- a/viewers/wicket/adoc/modules/ROOT/pages/extending/custom-bootstrap-theme.adoc
+++ b/viewers/wicket/adoc/modules/ROOT/pages/extending/custom-bootstrap-theme.adoc
@@ -5,7 +5,7 @@
-The Apache Isis Wicket viewer uses http://getbootstrap.com/[Bootstrap] styles and components, courtesy of the https://github.com/l0rdn1kk0n/wicket-bootstrap[Wicket Bootstrap] integration.
+The Apache Causeway Wicket viewer uses http://getbootstrap.com/[Bootstrap] styles and components, courtesy of the https://github.com/l0rdn1kk0n/wicket-bootstrap[Wicket Bootstrap] integration.
By default the viewer uses the default bootstrap theme.
It is possible to configure the Wicket viewer to allow the user to xref:vw:ROOT:setup-and-configuration.adoc#themes[select other themes] provided by http://bootswatch.com[bootswatch.com], and if required one of these can be xref:refguide:config:sections/causeway.viewer.wicket.adoc#causeway.viewer.wicket.themes.initial[set as the default].
diff --git a/viewers/wicket/adoc/modules/ROOT/pages/extending/custom-pages.adoc b/viewers/wicket/adoc/modules/ROOT/pages/extending/custom-pages.adoc
index 92a5447ba0..f4c061bcae 100644
--- a/viewers/wicket/adoc/modules/ROOT/pages/extending/custom-pages.adoc
+++ b/viewers/wicket/adoc/modules/ROOT/pages/extending/custom-pages.adoc
@@ -56,7 +56,7 @@ The Wicket viewer defines these page types (see the `org.apache.causeway.viewer.
The `PageClassList` interface declares which class (subclass of `org.apache.wicket.Page` is used to render for each of these types.
-For example, Apache Isis' `WicketSignInPage` renders the signin page.
+For example, Apache Causeway' `WicketSignInPage` renders the signin page.
To specify a different page class, create a new implementation of `PageClassList` and annotate with an earlier precedence than the default.
If you are just tweaking the defaults, then its easiest to override `PageClassListDefault`:
diff --git a/viewers/wicket/adoc/modules/ROOT/pages/extending/replacing-page-elements.adoc b/viewers/wicket/adoc/modules/ROOT/pages/extending/replacing-page-elements.adoc
index 01e918b8a7..c9c7de91f4 100644
--- a/viewers/wicket/adoc/modules/ROOT/pages/extending/replacing-page-elements.adoc
+++ b/viewers/wicket/adoc/modules/ROOT/pages/extending/replacing-page-elements.adoc
@@ -9,7 +9,7 @@ Replacing elements of the page is the most powerful general-purpose way to custo
Examples include the
xref:vw:gmap3:about.adoc[Gmap3], xref:vw:fullcalendar:about.adoc[Fullcalendar], xref:vw:exceldownload:about.adoc[Excel Download] and xref:vw:pdfjs:about.adoc[pdf.js] 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.
+The pages generated by Apache Causeway' 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.
The larger components delegate to the smaller, of course.
@@ -18,8 +18,8 @@ The larger components delegate to the smaller, of course.
== How the viewer selects components
-Components are created using Apache Isis' `ComponentFactory` interface, which are registered in turn through the `ComponentFactoryRegistrar` interface.
-Every component is categorizes by type (the `ComponentType` enum), and Apache Isis uses this to determine which `ComponentFactory` to use.
+Components are created using Apache Causeway' `ComponentFactory` interface, which are registered in turn through the `ComponentFactoryRegistrar` interface.
+Every component is categorizes by type (the `ComponentType` enum), and Apache Causeway uses this to determine which `ComponentFactory` to use.
For example, the `ComponentType.BOOKMARKED_PAGES` is used to locate the `ComponentFactory` that will build the bookmarked pages panel.
Each factory is also handed a model (an implementation of `org.apache.wicket.IModel`) appropriate to its `ComponentType`; this holds the data to be rendered.
@@ -45,7 +45,7 @@ There is one refinement to the above algorithm where multiple component factorie
== How to replace a component
This design (the http://en.wikipedia.org/wiki/Chain-of-responsibility_pattern[chain of responsibility] design pattern) makes it quite straightforward to change the rendering of any element of the page.
-For example, you might switch out Apache Isis' sliding bookmark panel and replace it with one that presents the bookmarks in some different fashion.
+For example, you might switch out Apache Causeway' sliding bookmark panel and replace it with one that presents the bookmarks in some different fashion.
First, you need to write a `ComponentFactory` and corresponding `Component`.
The recommended approach is to start with the source of the `Component` you want to switch out.
@@ -95,10 +95,10 @@ Your new component will be used instead of the default implementation.
[#additional-views-of-collections]
== Additional Views of Collections
-As explained above, in most cases Apache Isis' Wicket viewer will search for the first `ComponentFactory` that can render an element, and use it.
+As explained above, in most cases Apache Causeway' Wicket viewer will search for the first `ComponentFactory` that can render an element, and use it.
In the case of (either standalone or parented) collections, though, the viewer will show all available views.
-For example, out-of-the-box Apache Isis provides a table view, a summary view (totals/sums/averages of any data), and a collapsed view.
+For example, out-of-the-box Apache Causeway provides a table view, a summary view (totals/sums/averages of any data), and a collapsed view.
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; as illustrated by the xref:vw:gmap3:about.adoc[Gmap3], xref:vw:fullcalendar:about.adoc[Fullcalendar] and xref:vw:exceldownload:about.adoc[Excel Download] extensions.
@@ -113,7 +113,7 @@ Wicket itself has lots of components available at its http://wicketstuff.org[wic
== Custom object view (eg dashboard)
One further use case in particular is worth highlighting; the rendering of an entire entity.
-Normally for entities this is done using `Bs3GridPanelFactory`, this being the first `ComponentFactory` for the `ComponentType.ENTITY` that is registered in Apache Isis default `ComponentFactoryRegistrarDefault`.
+Normally for entities this is done using `Bs3GridPanelFactory`, this being the first `ComponentFactory` for the `ComponentType.ENTITY` that is registered in Apache Causeway default `ComponentFactoryRegistrarDefault`.
You could, though, register your own `ComponentFactory` for entities that is targeted at a particular class of entity - some sort of object representing a dashboard, for example.
It can use the `EntityModel` provided to it to determine the class of the entity, checking if it is of the appropriate type.
diff --git a/viewers/wicket/adoc/modules/ROOT/pages/features.adoc b/viewers/wicket/adoc/modules/ROOT/pages/features.adoc
index f1909f21ba..9b3e3c7540 100644
--- a/viewers/wicket/adoc/modules/ROOT/pages/features.adoc
+++ b/viewers/wicket/adoc/modules/ROOT/pages/features.adoc
@@ -3,7 +3,7 @@
: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 [...]
-This chapter highlights a number of features of the wicket viewer from the perspective of an end-user actually using your Apache Isis application.
+This chapter highlights a number of features of the wicket viewer from the perspective of an end-user actually using your Apache Causeway application.
diff --git a/viewers/wicket/adoc/modules/ROOT/pages/features/titles-in-tables.adoc b/viewers/wicket/adoc/modules/ROOT/pages/features/titles-in-tables.adoc
index d5f97c2f09..111a2c6f0c 100644
--- a/viewers/wicket/adoc/modules/ROOT/pages/features/titles-in-tables.adoc
+++ b/viewers/wicket/adoc/modules/ROOT/pages/features/titles-in-tables.adoc
@@ -65,7 +65,7 @@ Conversely, if a `Product` is viewed then its collection of ``Order``s would sup
[TIP]
====
This feature is a close cousin of the `@PropertyLayout(hidden=Where.REFERENCES_PARENT)` annotation, which will cause the property itself to be hidden as a column in the table.
-An Apache Isis idiom is therefore:
+An Apache Causeway idiom is therefore:
[source,java]
----
diff --git a/viewers/wicket/adoc/modules/ROOT/pages/features/user-registration.adoc b/viewers/wicket/adoc/modules/ROOT/pages/features/user-registration.adoc
index efe526e7a4..9371f348cc 100644
--- a/viewers/wicket/adoc/modules/ROOT/pages/features/user-registration.adoc
+++ b/viewers/wicket/adoc/modules/ROOT/pages/features/user-registration.adoc
@@ -20,7 +20,7 @@ To support this the framework requires three services to be registered and confi
* the xref:refguide:applib:index/services/userreg/EmailNotificationService.adoc[email notification service], which provides an API for to send the verification emails
* the xref:refguide:applib:index/services/email/EmailService.adoc[email service], that is used by the email notification service to actually send the email.
-The Apache Isis core framework provides a default implementation of both the email notification service and the email service.
+The Apache Causeway core framework provides a default implementation of both the email notification service and the email service.
The xref:security:ROOT:about.adoc[Security Manager] extension provides a partial implementation of xref:refguide:applib:index/services/userreg/UserRegistrationService.adoc[user registration service] that you can complete for your own applications.
diff --git a/viewers/wicket/adoc/modules/ROOT/pages/hints-and-tips/i18n-label-in-wicket-viewer.adoc b/viewers/wicket/adoc/modules/ROOT/pages/hints-and-tips/i18n-label-in-wicket-viewer.adoc
index 69e2b5e5e2..0b141bb3ae 100644
--- a/viewers/wicket/adoc/modules/ROOT/pages/hints-and-tips/i18n-label-in-wicket-viewer.adoc
+++ b/viewers/wicket/adoc/modules/ROOT/pages/hints-and-tips/i18n-label-in-wicket-viewer.adoc
@@ -5,7 +5,7 @@
-From link:http://causeway.markmail.org/thread/ctppmtcbsf4iskzi[this thread] on the Apache Isis users mailing list:
+From link:http://causeway.markmail.org/thread/ctppmtcbsf4iskzi[this thread] on the Apache Causeway users mailing list:
* _I am trying to internationalize the label descriptions of form actions, eg those in `ActionParametersFormPanel`.
Referencing those via their message id inside a .po file didn't work either.
diff --git a/viewers/wicket/adoc/modules/ROOT/pages/hints-and-tips/per-user-themes.adoc b/viewers/wicket/adoc/modules/ROOT/pages/hints-and-tips/per-user-themes.adoc
index 4bde33ee5d..1a007c9fb6 100644
--- a/viewers/wicket/adoc/modules/ROOT/pages/hints-and-tips/per-user-themes.adoc
+++ b/viewers/wicket/adoc/modules/ROOT/pages/hints-and-tips/per-user-themes.adoc
@@ -4,9 +4,9 @@
: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 [...]
-From link:http://causeway.markmail.org/thread/kb4442niwwbnghey[this thread] on the Apache Isis users mailing list:
+From link:http://causeway.markmail.org/thread/kb4442niwwbnghey[this thread] on the Apache Causeway users mailing list:
-* _Is it possible to have each of our resellers (using our Apache Isis application) use their own theme/branding with their own logo and colors?
+* _Is it possible to have each of our resellers (using our Apache Causeway application) use their own theme/branding with their own logo and colors?
Would this also be possible for the login page, possibly depending on the used host name?_
diff --git a/viewers/wicket/adoc/modules/ROOT/pages/setup-and-configuration.adoc b/viewers/wicket/adoc/modules/ROOT/pages/setup-and-configuration.adoc
index 407cd5cb2b..362c1d905f 100644
--- a/viewers/wicket/adoc/modules/ROOT/pages/setup-and-configuration.adoc
+++ b/viewers/wicket/adoc/modules/ROOT/pages/setup-and-configuration.adoc
@@ -143,7 +143,7 @@ causeway:
credit:
- url: http://causeway.apache.org
image: images/apache-causeway/logo-48x48.png
- name: Apache Isis
+ name: Apache Causeway
----
Up to three credits can be provided.
diff --git a/viewers/wicket/adoc/modules/ROOT/partials/security/pages.adoc b/viewers/wicket/adoc/modules/ROOT/partials/security/pages.adoc
index 3b7fce763a..f8f9094a28 100644
--- a/viewers/wicket/adoc/modules/ROOT/partials/security/pages.adoc
+++ b/viewers/wicket/adoc/modules/ROOT/partials/security/pages.adoc
@@ -24,7 +24,7 @@ In the sign-in page the viewer calls to the xref:refguide:core:index/security/au
It also adds in its special reserved role (per the annotation above) and then continues on to whichever page the user was attempting to access (usually the home page).
And that's really all there is to it.
-When the viewer renders a domain object it queries the Apache Isis metamodel, and suppresses from the view any object members (properties, actions etc) that are invisible.
+When the viewer renders a domain object it queries the Apache Causeway metamodel, and suppresses from the view any object members (properties, actions etc) that are invisible.
These may be invisible because the user has no (read ) permission, or they may be invisible because of domain object logic (eg a `hideXxx()` method).
The viewer neither knows nor cares.
diff --git a/viewers/wicket/adoc/modules/ROOT/partials/security/user-registration.adoc b/viewers/wicket/adoc/modules/ROOT/partials/security/user-registration.adoc
index 9e3fc22654..77542954a5 100644
--- a/viewers/wicket/adoc/modules/ROOT/partials/security/user-registration.adoc
+++ b/viewers/wicket/adoc/modules/ROOT/partials/security/user-registration.adoc
@@ -5,11 +5,11 @@
As well as providing a sign-in screen, the Wicket viewer also provides the ability for users to self-register.
-By and large this operates outside of Apache Isis' security mechanisms; indeed the various pages (sign-up, sign-up verification, password reset) are all rendered _without_ there being any current user session.
-These pages all "reach inside" Apache Isis framework in order to actually do their stuff.
+By and large this operates outside of Apache Causeway' security mechanisms; indeed the various pages (sign-up, sign-up verification, password reset) are all rendered _without_ there being any current user session.
+These pages all "reach inside" Apache Causeway framework in order to actually do their stuff.
User registration is only available if the xref:refguide:applib:index/services/userreg/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.
+Because Shiro realms are pluggable, the Apache Causeway framework does not provide default implementations of this service.
However, if you are using the xref:security:ROOT:about.adoc[SecMan extension], then this module _does_ provide an implementation (that, as you might expect, creates new "user" domain entities).