You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@isis.apache.org by da...@apache.org on 2015/06/29 08:19:56 UTC
[4/8] isis git commit: ISIS-1133: converting "Isis" to "Apache Isis"
in the docs.
http://git-wip-us.apache.org/repos/asf/isis/blob/fe19dc4b/adocs/documentation/src/main/asciidoc/guides/_ug_testing_bdd-spec-support_writing-a-bdd-spec.adoc
----------------------------------------------------------------------
diff --git a/adocs/documentation/src/main/asciidoc/guides/_ug_testing_bdd-spec-support_writing-a-bdd-spec.adoc b/adocs/documentation/src/main/asciidoc/guides/_ug_testing_bdd-spec-support_writing-a-bdd-spec.adoc
index 9412045..aff1186 100644
--- a/adocs/documentation/src/main/asciidoc/guides/_ug_testing_bdd-spec-support_writing-a-bdd-spec.adoc
+++ b/adocs/documentation/src/main/asciidoc/guides/_ug_testing_bdd-spec-support_writing-a-bdd-spec.adoc
@@ -45,11 +45,11 @@ The `@SimpleObjectsFixture` is a custom tag we've specified to indicate the prer
====
Although BDD specs are most commonly used for end-to-end tests (ie at the same scope as an integration test), the two concerns (expressability of a test to a business person vs granularity of the test) should not be conflated. There are a couple of http://silkandspinach.net/2013/01/18/a-testing-strategy/[good] blog http://claysnow.co.uk/the-testing-iceberg/[posts] discussing http://claysnow.co.uk/living-documentation-can-be-readable-and-fast/[this]. The basic idea is to avoid the overhead of a heavy-duty integration test if possible.
-Apache Isis does also support running BDD specs in unit test mode; by annotating the scenario with the `@unit` (rather than `@integration` tag). When running under unit-level scope, the Isis system is _not_ instantiated. Instead, the `ScenarioExecution` class returns JMock mocks (except for the `WrapperFactory`, if configured).
+Apache Isis does also support running BDD specs in unit test mode; by annotating the scenario with the `@unit` (rather than `@integration` tag). When running under unit-level scope, the Apache Isis system is _not_ instantiated. Instead, the `ScenarioExecution` class returns JMock mocks (except for the `WrapperFactory`, if configured).
-To support unit testing scope Isis provides the `InMemoryDB` class; a glorified hashmap of "persisted" objects. Use of this utility class is optional.
+To support unit testing scope Apache Isis provides the `InMemoryDB` class; a glorified hashmap of "persisted" objects. Use of this utility class is optional.
-Writing a BDD spec that supports both modes of operation therefore takes more effort and we expect most users interested in BDD will use integration-testing scope; for these reasons we have chosen _not_ to include unit-testing support in the xref:ug.adoc#_ug_getting-started_simpleapp-archetype[SimpleApp archetype]. For those who do require faster-executing test suite, it's worthwhile knowing that Isis can support this.
+Writing a BDD spec that supports both modes of operation therefore takes more effort and we expect most users interested in BDD will use integration-testing scope; for these reasons we have chosen _not_ to include unit-testing support in the xref:ug.adoc#_ug_getting-started_simpleapp-archetype[SimpleApp archetype]. For those who do require faster-executing test suite, it's worthwhile knowing that Apache Isis can support this.
====
@@ -74,7 +74,7 @@ public class RunSpecs {
The JSON formatter allows integration with enhanced reports, for example as provided by http://www.masterthought.net/section/cucumber-reporting[Masterthought.net] (screenshots at end of page). (Commented out) configuration for this is provided in the xref:ug.adoc#_ug_getting-started_simpleapp-archetype[SimpleApp archetype].
-The bootstrapping of Isis can be moved into a `BootstrappingGlue` step definition:
+The bootstrapping of Apache Isis can be moved into a `BootstrappingGlue` step definition:
[source,java]
----
http://git-wip-us.apache.org/repos/asf/isis/blob/fe19dc4b/adocs/documentation/src/main/asciidoc/guides/_ug_testing_fixture-scripts.adoc
----------------------------------------------------------------------
diff --git a/adocs/documentation/src/main/asciidoc/guides/_ug_testing_fixture-scripts.adoc b/adocs/documentation/src/main/asciidoc/guides/_ug_testing_fixture-scripts.adoc
index 2f311b7..a3f42dc 100644
--- a/adocs/documentation/src/main/asciidoc/guides/_ug_testing_fixture-scripts.adoc
+++ b/adocs/documentation/src/main/asciidoc/guides/_ug_testing_fixture-scripts.adoc
@@ -12,14 +12,14 @@ On a very simple system you could probably get away with using SQL to insert dir
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 Isis provides is a small library called *_fixture scripts_*. A fixture script is basically a wrapper for executing arbitrary work, but that work almost always invoking a business action.
+The solution that Apache Isis provides is a small library called *_fixture scripts_*. A fixture script is basically a wrapper for executing arbitrary work, but that work almost always invoking a business action.
[TIP]
====
If you want to learn more on this topic (with live coding!), check out this https://skillsmatter.com/skillscasts/5638-to-those-whom-much-is-given-much-is-expected[presentation] given at BDD Exchange 2014.
====
-There is another benefit to Isis' 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:
+There is another benefit to Apache Isis' 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 +
+
http://git-wip-us.apache.org/repos/asf/isis/blob/fe19dc4b/adocs/documentation/src/main/asciidoc/guides/_ug_testing_fixture-scripts_api-and-usage.adoc
----------------------------------------------------------------------
diff --git a/adocs/documentation/src/main/asciidoc/guides/_ug_testing_fixture-scripts_api-and-usage.adoc b/adocs/documentation/src/main/asciidoc/guides/_ug_testing_fixture-scripts_api-and-usage.adoc
index 450fa40..8fa4118 100644
--- a/adocs/documentation/src/main/asciidoc/guides/_ug_testing_fixture-scripts_api-and-usage.adoc
+++ b/adocs/documentation/src/main/asciidoc/guides/_ug_testing_fixture-scripts_api-and-usage.adoc
@@ -46,7 +46,7 @@ public class DomainAppFixturesService extends FixtureScripts { // <3>
<2> ... under the "Prototyping" menu
<3> inherit from `org.apache.isis.applib.fixturescripts.FixtureScripts`
<4> search for all fixture scripts under the "domainapp" package; in your code this would probably be "com.mycompany.myapp" or similar
-<5> if the same fixture script (class) is encountered more than once, then run anyway; more on this in <<Organizing Fixture scripts>>.
+<5> if the same fixture script (class) is encountered more than once, then run anyway; more on this in xref:ug.adoc#_ug_testing_fixture-scripts_api-and-usage_organizing[Organizing Fixture scripts]], below.
<6> (optional) specify a default fixture script to run, in this case `RecreateSimpleObjects` fixture script (see below)
<7> make all fixture scripts found available as a drop-down (by increasing the visibility of this method to `public`)
@@ -97,6 +97,9 @@ You are free, of course, to add additional "convenience" actions into it if you
Let's now look at the `FixtureScript` class, where there's a bit more going on.
+
+
+
== `FixtureScript`
A fixture script is ultimately just a block of code that can be executed, so it's up to you how you implement it to set up the system. However, we strongly recommend that you use it to invoke actions on business objects, in essence to replay what a real-life user would have done. That way, the fixture script will remain valid even if the underlying implementation of the system changes in the future.
@@ -252,6 +255,8 @@ public class SimpleObjectIntegTest extends SimpleAppIntegTest {
+
+[[_ug_testing_fixture-scripts_api-and-usage_organizing]]
== Organizing Fixture scripts
There are lots of ways to organize fixture scripts, but we've used them as either:
http://git-wip-us.apache.org/repos/asf/isis/blob/fe19dc4b/adocs/documentation/src/main/asciidoc/guides/_ug_testing_integ-test-support.adoc
----------------------------------------------------------------------
diff --git a/adocs/documentation/src/main/asciidoc/guides/_ug_testing_integ-test-support.adoc b/adocs/documentation/src/main/asciidoc/guides/_ug_testing_integ-test-support.adoc
index f103703..64f2eb4 100644
--- a/adocs/documentation/src/main/asciidoc/guides/_ug_testing_integ-test-support.adoc
+++ b/adocs/documentation/src/main/asciidoc/guides/_ug_testing_integ-test-support.adoc
@@ -7,7 +7,7 @@
As discussed in the introductory overview of this chapter, Apache Isis allows you to integration test your domain objects from within JUnit. There are several parts to this:
-* configuring the Isis runtime so it can be bootstrapped (mostly boilerplate)
+* configuring the Apache Isis runtime so it can be bootstrapped (mostly boilerplate)
* defining a base class to perform said bootstrapping
* using fixture scripts to set up the app
* using `WrapperFactory` so that the UI can be simulated.
http://git-wip-us.apache.org/repos/asf/isis/blob/fe19dc4b/adocs/documentation/src/main/asciidoc/guides/_ug_testing_integ-test-support_bootstrapping.adoc
----------------------------------------------------------------------
diff --git a/adocs/documentation/src/main/asciidoc/guides/_ug_testing_integ-test-support_bootstrapping.adoc b/adocs/documentation/src/main/asciidoc/guides/_ug_testing_integ-test-support_bootstrapping.adoc
index 41957ea..da5ca77 100644
--- a/adocs/documentation/src/main/asciidoc/guides/_ug_testing_integ-test-support_bootstrapping.adoc
+++ b/adocs/documentation/src/main/asciidoc/guides/_ug_testing_integ-test-support_bootstrapping.adoc
@@ -5,7 +5,7 @@
:_imagesdir: images/
-Integration tests instantiate an Isis "runtime" (as a singleton) within a JUnit test. Because (depending on the size of your app) it takes a little time to bootstrap Isis, the framework caches the runtime on a thread-local from one test to the next.
+Integration tests instantiate an Apache Isis "runtime" (as a singleton) within a JUnit test. Because (depending on the size of your app) it takes a little time to bootstrap Apache Isis, the framework caches the runtime on a thread-local from one test to the next.
Nevertheless, we do need to bootstrap the runtime for the very first test.
@@ -13,7 +13,7 @@ Since the integration tests don't depend on the `webapp` module, it's necessary
[NOTE]
====
-We hope to simplify the way this works in future versions of Isis.
+We hope to simplify the way this works in future versions of Apache Isis.
====
The example code in this section is taken from the app generated by the xref:ug.adoc#_ug_getting-started_simpleapp-archetype[SimpleApp archetype].
@@ -140,7 +140,7 @@ To remove a little bit of boilerplate, the `IsisConfigurationForJdoIntegTests` c
== System Initializer
-The builder is defined and used within a class we call the system initializer that is responsible for instantiating the Isis runtime, and binding it to a thread-local. This is performed within a static `initIsft()` method.
+The builder is defined and used within a class we call the system initializer that is responsible for instantiating the Apache Isis runtime, and binding it to a thread-local. This is performed within a static `initIsft()` method.
Here's the code:
@@ -161,7 +161,7 @@ public class SimpleAppSystemInitializer {
}
----
-<1> instantiates and initializes the Isis runtime (the `IsisSystemForTest` class)
+<1> instantiates and initializes the Apache Isis runtime (the `IsisSystemForTest` class)
<2> binds the runtime to a thread-local.
@@ -185,14 +185,14 @@ public abstract class SimpleAppIntegTest {
}
----
<1> ensure that logging messages don't get swallowed
-<2> initialize the Isis runtime
+<2> initialize the Apache Isis runtime
<3> primarily exists to support the writing of xref:ug.adoc#_ug_testing_bdd-spec-support[BDD specifications], but also enables finer-grained management of sessions/transactions (discussed below).
=== `IntegrationTestAbstract`
-In fact, we recommend that your base class inherit from Isis' `IntegrationTestAbstract` class:
+In fact, we recommend that your base class inherit from Apache Isis' `IntegrationTestAbstract` class:
[source,java]
----
@@ -218,8 +218,8 @@ Although not mandatory, this provides a number of helper/convenience methods and
public ExceptionRecognizerTranslate exceptionRecognizerTranslations = // <4>
ExceptionRecognizerTranslate.create();
----
-<1> ensures an Isis session/transaction running for each test
-<2> sets up a JMock context (using Isis' extension to JMock as described in <<JMock Extensions>>
+<1> ensures an Apache Isis session/transaction running for each test
+<2> sets up a JMock context (using Apache Isis' extension to JMock as described in xref:ug.adoc#_ug_testing_unit-test-support_jmock-extensions[JMock Extensions].
<3> standard JUnit rule for writing tests that throw exceptions
<4> to capture messages that require translation, as described in xref:ug.adoc#_ug_more-advanced_i18n[i18 support].
http://git-wip-us.apache.org/repos/asf/isis/blob/fe19dc4b/adocs/documentation/src/main/asciidoc/guides/_ug_testing_integ-test-support_typical-usage.adoc
----------------------------------------------------------------------
diff --git a/adocs/documentation/src/main/asciidoc/guides/_ug_testing_integ-test-support_typical-usage.adoc b/adocs/documentation/src/main/asciidoc/guides/_ug_testing_integ-test-support_typical-usage.adoc
index 66c9936..abb422f 100644
--- a/adocs/documentation/src/main/asciidoc/guides/_ug_testing_integ-test-support_typical-usage.adoc
+++ b/adocs/documentation/src/main/asciidoc/guides/_ug_testing_integ-test-support_typical-usage.adoc
@@ -33,7 +33,7 @@ public class ToDoItem ... {
}
----
-We typically put the bootstrapping of Isis into a superclass (`AbstractToDoIntegTest` below), then subclass as required.
+We typically put the bootstrapping of Apache Isis into a superclass (`AbstractToDoIntegTest` below), then subclass as required.
For this test (of the "completed()" action) we need an instance of a `ToDoItem` that is not yet complete. Here's the setup:
http://git-wip-us.apache.org/repos/asf/isis/blob/fe19dc4b/adocs/documentation/src/main/asciidoc/guides/_ug_testing_integ-test-support_wrapper-factory.adoc
----------------------------------------------------------------------
diff --git a/adocs/documentation/src/main/asciidoc/guides/_ug_testing_integ-test-support_wrapper-factory.adoc b/adocs/documentation/src/main/asciidoc/guides/_ug_testing_integ-test-support_wrapper-factory.adoc
index c298dc1..e9f5cdc 100644
--- a/adocs/documentation/src/main/asciidoc/guides/_ug_testing_integ-test-support_wrapper-factory.adoc
+++ b/adocs/documentation/src/main/asciidoc/guides/_ug_testing_integ-test-support_wrapper-factory.adoc
@@ -22,7 +22,7 @@ The mechanics are as follows:
. 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 Isis metamodel
+. the wrapper performs a reverse lookup from the method invoked (a regular `java.lang.reflect.Method` instance) into the Apache Isis 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
@@ -157,6 +157,6 @@ The wrapper will also fire domain events for properties (if annotated with `@Pro
[NOTE]
====
-It isn't possible to use the `WrapperFactory` in a unit test, because there needs to be a running instance of Isis that holds the metamodel.
+It isn't possible to use the `WrapperFactory` in a unit test, because there needs to be a running instance of Apache Isis that holds the metamodel.
====
http://git-wip-us.apache.org/repos/asf/isis/blob/fe19dc4b/adocs/documentation/src/main/asciidoc/guides/_ug_testing_unit-test-support_contract-tests.adoc
----------------------------------------------------------------------
diff --git a/adocs/documentation/src/main/asciidoc/guides/_ug_testing_unit-test-support_contract-tests.adoc b/adocs/documentation/src/main/asciidoc/guides/_ug_testing_unit-test-support_contract-tests.adoc
index 75f9447..54413dc 100644
--- a/adocs/documentation/src/main/asciidoc/guides/_ug_testing_unit-test-support_contract-tests.adoc
+++ b/adocs/documentation/src/main/asciidoc/guides/_ug_testing_unit-test-support_contract-tests.adoc
@@ -41,7 +41,7 @@ If using DataNucleus against an RDBMS (as you probably are) then we strongly rec
* second, `SortedSet` is preferable to `Set` because then the order is well-defined and predictable (to an end user, to the programmer). +
+
-The <<ObjectContracts>> utility class substantially simplifies the task of implementing `Comparable` in your domain classes.
+The xref:rg.adoc#_rg_classes_utility_manpage-ObjectContracts[`ObjectContracts`] utility class substantially simplifies the task of implementing `Comparable` in your domain classes.
* third, if the relationship is bidirectional then JDO/Objectstore will automatically maintain the relationship.
@@ -121,7 +121,7 @@ This contract test automatically checks that the `injectXxx(...)` method, to all
[NOTE]
====
-This contract test is semi-obsolete; most of the time you will want to use `@javax.inject.Inject` on fields rather than the `injectXxx()` method. The feature dates from a time before Isis supported the `@Inject` annotation.
+This contract test is semi-obsolete; most of the time you will want to use `@javax.inject.Inject` on fields rather than the `injectXxx()` method. The feature dates from a time before Apache Isis supported the `@Inject` annotation.
====
http://git-wip-us.apache.org/repos/asf/isis/blob/fe19dc4b/adocs/documentation/src/main/asciidoc/guides/_ug_tutorials_pet-clinic.adoc
----------------------------------------------------------------------
diff --git a/adocs/documentation/src/main/asciidoc/guides/_ug_tutorials_pet-clinic.adoc b/adocs/documentation/src/main/asciidoc/guides/_ug_tutorials_pet-clinic.adoc
index dccc025..a6fbbc1 100644
--- a/adocs/documentation/src/main/asciidoc/guides/_ug_tutorials_pet-clinic.adoc
+++ b/adocs/documentation/src/main/asciidoc/guides/_ug_tutorials_pet-clinic.adoc
@@ -197,7 +197,7 @@ Apache Isis applications are organized into several Maven modules. Within your I
== Testing
-Testing is of course massively important, and Isis makes both unit testing and (end-to-end) integration testing easy. Building the app from the Maven command line ("mvn clean install") will run all tests, but you should also run the tests from within the IDE.
+Testing is of course massively important, and Apache Isis makes both unit testing and (end-to-end) integration testing easy. Building the app from the Maven command line ("mvn clean install") will run all tests, but you should also run the tests from within the IDE.
* `myapp-dom` unit tests
* run
@@ -321,8 +321,8 @@ where:
<2> `@DatastoreIdentity` specify a surrogate `Id` column to be used as the primary key
<3> `@Version` provides support for optimistic locking
<4> `@Unique` enforces a uniqueness constraint so that no two `Pet`s can have the same name (unrealistic, but can refactor later)
-<5> `@ObjectType` is used by Isis for its own internal "OID" identifier; this also appears in the URL in Isis' Wicket viewer and REST API
-<6> `@Bookmarkable` indicates that the object can be automatically bookmarked in Isis' Wicket viewer
+<5> `@ObjectType` is used by Apache Isis for its own internal "OID" identifier; this also appears in the URL in Apache Isis' Wicket viewer and REST API
+<6> `@Bookmarkable` indicates that the object can be automatically bookmarked in Apache Isis' Wicket viewer
[NOTE]
====
http://git-wip-us.apache.org/repos/asf/isis/blob/fe19dc4b/adocs/documentation/src/main/asciidoc/guides/_ug_tutorials_stop-scaffolding-start-coding.adoc
----------------------------------------------------------------------
diff --git a/adocs/documentation/src/main/asciidoc/guides/_ug_tutorials_stop-scaffolding-start-coding.adoc b/adocs/documentation/src/main/asciidoc/guides/_ug_tutorials_stop-scaffolding-start-coding.adoc
index bbda412..6dcba2f 100644
--- a/adocs/documentation/src/main/asciidoc/guides/_ug_tutorials_stop-scaffolding-start-coding.adoc
+++ b/adocs/documentation/src/main/asciidoc/guides/_ug_tutorials_stop-scaffolding-start-coding.adoc
@@ -122,7 +122,7 @@ Apache Isis applications are organized into several Maven modules. Within your I
== Testing
-Testing is of course massively important, and Isis makes both unit testing and (end-to-end) integration testing easy. Building the app from the Maven command line ("mvn clean install") will run all tests, but you should also run the tests from within the IDE.
+Testing is of course massively important, and Apache Isis makes both unit testing and (end-to-end) integration testing easy. Building the app from the Maven command line ("mvn clean install") will run all tests, but you should also run the tests from within the IDE.
* `myapp-dom` unit tests
* run
@@ -204,7 +204,7 @@ Most domain objects in Apache Isis applications are persistent entities. In the
** for `Pet`, can leave `name` property as is
* specify a xref:ug.adoc#_ug_how-tos_ui-hints_object-titles-and-icons[title]
* specify an xref:ug.adoc#_ug_how-tos_ui-hints_object-titles-and-icons[icon]
-* make the entity bookmarkable by adding the <<__code_domainobjectlayout_code,@DomainObjectLayout(bookmarking=...)` annotation
+* make the entity bookmarkable by adding the xref:rg.adoc#_rg_annotations_manpage-DomainObjectLayout_bookmarking[`@DomainObjectLayout#bookmarking()`] attribute.
* confirm is available from bookmark panel (top-left of Wicket UI)
@@ -412,7 +412,7 @@ Or, more pithily: "see it, use it, do it"
* Use the xref:rg.adoc#_rg_annotations_manpage-Property_hidden[`Property(hidden=...)`] annotation to make properties invisible
** likewise xref:rg.adoc#_rg_annotations_manpage-Collection_hidden[`@Collection(hidden=...)`] for collections
-** the xref:rg.adoc#_rg_annotations_manpage-Programmatic[`@Programmatic`] annotation can also be used and in many cases is to be preferred; the difference is that the latter means the member is not part of the Isis metamodel.
+** the xref:rg.adoc#_rg_annotations_manpage-Programmatic[`@Programmatic`] annotation can also be used and in many cases is to be preferred; the difference is that the latter means the member is not part of the Apache Isis metamodel.
* Use the xref:rg.adoc#_rg_methods_prefixes_manpage-hide[`hide...()`] supporting method on properties, collections and actions to make a property/collection/action invisible according to some imperative rule
@@ -458,7 +458,7 @@ To ensure testability, there should be no dependencies on system time, for examp
== Using Contributions
-One of Isis' most powerful features is the ability for the UI to combine functionality from domain services into the representation of an entity. The effect is similar to traits or mix-ins in other languages, however the "mixing in" is done at runtime, within the Isis metamodel. In Isis' terminology, we say that the domain service action is contributed to the entity.
+One of Apache Isis' most powerful features is the ability for the UI to combine functionality from domain services into the representation of an entity. The effect is similar to traits or mix-ins in other languages, however the "mixing in" is done at runtime, within the Apache Isis metamodel. In Apache Isis' terminology, we say that the domain service action is contributed to the entity.
Any action of a domain service that has a domain entity type as one of its parameter types will (by default) be contributed. If the service action takes more than one argument, or does not have safe semantics, then it will be contributed as an entity action. If the service action has precisely one parameter type (that of the entity) and has safe semantics then it will be contributed either as a collection or as a property (dependent on whether it returns a collection of a scalar).
@@ -503,7 +503,7 @@ Finally, note that the layout of contributed actions/collections/properties can
Another way in which Apache Isis helps you keep your application nicely modularized is through its event bus. Each action invocation, or property modification, can be used to generate a succession of events that allows subscribers to veto the interaction (the see it/use it/do it rules) or, if the action is allowed, to perform work prior to the execution of the action or after the execution of the action.
-Under the covers Isis uses the https://code.google.com/p/guava-libraries/wiki/EventBusExplained[Guava event bus] and subscribers (always domain services) subscribe by writing methods annotated with `@com.google.common.eventbus.Subscribe` annotation.
+Under the covers Apache Isis uses the https://code.google.com/p/guava-libraries/wiki/EventBusExplained[Guava event bus] and subscribers (always domain services) subscribe by writing methods annotated with `@com.google.common.eventbus.Subscribe` annotation.
By default the events generated are `ActionDomainEvent.Default` (for actions) and `PropertyDomainEvent.Default` (for properties). Subclasses of these can be specified using the xref:rg.adoc#_rg_annotations_manpage-Action_domainEvent[`@Action(domainEvent=...)`] or xref:rg.adoc#_rg_annotations_manpage-Property_domainEvent[`Property(domainEvent=...)`] for properties.
@@ -601,9 +601,9 @@ In addition to providing Wicket viewer extensions, http://www.isisaddons.org/[Is
In most cases users can accomplish the business operations they need by invoking actions directly on domain entities. For some high-volume or specialized uses cases, though, there may be a requirement to bring together data or functionality that spans several entities.
-Also, if using Isis' REST API then the REST client may be a native application (on a smartphone or tablet, say) that is deployed by a third party. In these cases exposing the entities directly would be inadvisable because a refactoring of the domain entity would change the REST API and probably break that REST client.
+Also, if using Apache Isis' REST API then the REST client may be a native application (on a smartphone or tablet, say) that is deployed by a third party. In these cases exposing the entities directly would be inadvisable because a refactoring of the domain entity would change the REST API and probably break that REST client.
-To support these use cases, Isis therefore allows you to write a view model, either by annotating the class with xref:rg.adoc#_rg_annotations_manpage-ViewModel[`@ViewModel`] or (for more control) by implementing the xref:rg.adoc#_rg_classes_super_manpage-AbstractViewModel[`ViewModel`] interface.
+To support these use cases, Apache Isis therefore allows you to write a view model, either by annotating the class with xref:rg.adoc#_rg_annotations_manpage-ViewModel[`@ViewModel`] or (for more control) by implementing the xref:rg.adoc#_rg_classes_super_manpage-AbstractViewModel[`ViewModel`] interface.
* build a view model summarizing the state of the app (a "dashboard")
* write a new `@HomePage` domain service action returning this dashboard viewmodel (and remove the `@HomePage` annotation from any other domain service if present)
@@ -667,7 +667,7 @@ Isis has great support for writing xref:ug.adoc#_ug_testing_integ-test-support[i
== Customising the REST API
-The REST API generated by Isis conforms to the Restful Objects specification. Isis 1.8.0 provides experimental support to allow the representations to be customized.
+The REST API generated by Apache Isis conforms to the Restful Objects specification. Apache Isis 1.8.0 provides experimental support to allow the representations to be customized.
* as per xref:ug.adoc#_ug_restfulobjects-viewer_configuration-properties_simplified-object[the documentation], configure the Restful Objects viewer to generate a simplified object representation: +
+
http://git-wip-us.apache.org/repos/asf/isis/blob/fe19dc4b/adocs/documentation/src/main/asciidoc/guides/_ug_wicket-viewer.adoc
----------------------------------------------------------------------
diff --git a/adocs/documentation/src/main/asciidoc/guides/_ug_wicket-viewer.adoc b/adocs/documentation/src/main/asciidoc/guides/_ug_wicket-viewer.adoc
index 3706371..78698f3 100644
--- a/adocs/documentation/src/main/asciidoc/guides/_ug_wicket-viewer.adoc
+++ b/adocs/documentation/src/main/asciidoc/guides/_ug_wicket-viewer.adoc
@@ -6,7 +6,7 @@
This chapter describes end-user features, configuration and customization of the Wicket viewer.
-Note that extending the Wicket viewer is described in the <<Extending>> chapter.
+Note that extending the Wicket viewer is described in the xref:ug.adoc#_ug_extending[Extending] chapter.
include::_ug_wicket-viewer_features.adoc[leveloffset=+1]
http://git-wip-us.apache.org/repos/asf/isis/blob/fe19dc4b/adocs/documentation/src/main/asciidoc/guides/_ug_wicket-viewer_configuration-properties.adoc
----------------------------------------------------------------------
diff --git a/adocs/documentation/src/main/asciidoc/guides/_ug_wicket-viewer_configuration-properties.adoc b/adocs/documentation/src/main/asciidoc/guides/_ug_wicket-viewer_configuration-properties.adoc
index 2364cb5..eee155b 100644
--- a/adocs/documentation/src/main/asciidoc/guides/_ug_wicket-viewer_configuration-properties.adoc
+++ b/adocs/documentation/src/main/asciidoc/guides/_ug_wicket-viewer_configuration-properties.adoc
@@ -5,11 +5,11 @@
:_imagesdir: images/
-Wicket configuration properties alter the way in which Isis' Wicket viewer renders domain objects. They are typically stored in `WEB-INF/viewer_wicket.properties`.
+Wicket configuration properties alter the way in which Apache Isis' Wicket viewer renders domain objects. They are typically stored in `WEB-INF/viewer_wicket.properties`.
[NOTE]
====
-To tell Isis that the Wicket viewer is in use (and should therefore search for the `viewer_wicket.properties` file), add the following to `WEB-INF/web.xml`:
+To tell Apache Isis that the Wicket viewer is in use (and should therefore search for the `viewer_wicket.properties` file), add the following to `WEB-INF/web.xml`:
[source, xml]
----
@@ -45,7 +45,7 @@ If you prefer you can place all configuration properties into `WEB-INF/isis.prop
|`isis.viewer.wicket.` +
`disableModalDialogs`
| `true`,`false` (`_false_`)
-| By default the Isis Wicket viewer uses a modal dialog for action parameters. Before this feature was implemented (prior to 1.4.0), Isis rendered action parameters on its own page. This property re-enables the old behaviour.
+| By default the Apache Isis Wicket viewer uses a modal dialog for action parameters. Before this feature was implemented (prior to 1.4.0), Apache Isis rendered action parameters on its own page. This property re-enables the old behaviour.
Note that action pages are still used for bookmarked actions.
http://git-wip-us.apache.org/repos/asf/isis/blob/fe19dc4b/adocs/documentation/src/main/asciidoc/guides/_ug_wicket-viewer_configuration-properties_stripped-wicket-tags.adoc
----------------------------------------------------------------------
diff --git a/adocs/documentation/src/main/asciidoc/guides/_ug_wicket-viewer_configuration-properties_stripped-wicket-tags.adoc b/adocs/documentation/src/main/asciidoc/guides/_ug_wicket-viewer_configuration-properties_stripped-wicket-tags.adoc
index cb653bd..980d354 100644
--- a/adocs/documentation/src/main/asciidoc/guides/_ug_wicket-viewer_configuration-properties_stripped-wicket-tags.adoc
+++ b/adocs/documentation/src/main/asciidoc/guides/_ug_wicket-viewer_configuration-properties_stripped-wicket-tags.adoc
@@ -6,7 +6,7 @@
-By default the Isis Wicket viewer will always strip wicket tags. However, when running in prototype mode, this behaviour can be overridden using a configuration property:
+By default the Apache Isis Wicket viewer will always strip wicket tags. However, when running in prototype mode, this behaviour can be overridden using a configuration property:
[source,ini]
----
@@ -15,7 +15,7 @@ isis.viewer.wicket.stripWicketTags=false
[NOTE]
====
-In 1.7.0 and earlier, the behaviour is different; the Isis Wicket viewer will preserve wicket tags when running in Isis' prototype/development mode, but will still strip wicket tags in Isis' server/deployment mode.
+In 1.7.0 and earlier, the behaviour is different; the Apache Isis Wicket viewer will preserve wicket tags when running in Apache Isis' prototype/development mode, but will still strip wicket tags in Apache Isis' server/deployment mode.
We changed the behaviour in 1.8.0 because we found that Internet Explorer can be sensitive to the presence of Wicket tags.
====
http://git-wip-us.apache.org/repos/asf/isis/blob/fe19dc4b/adocs/documentation/src/main/asciidoc/guides/_ug_wicket-viewer_customisation_cheap-n-cheerful-theme.adoc
----------------------------------------------------------------------
diff --git a/adocs/documentation/src/main/asciidoc/guides/_ug_wicket-viewer_customisation_cheap-n-cheerful-theme.adoc b/adocs/documentation/src/main/asciidoc/guides/_ug_wicket-viewer_customisation_cheap-n-cheerful-theme.adoc
index b96cb73..d6c51ba 100644
--- a/adocs/documentation/src/main/asciidoc/guides/_ug_wicket-viewer_customisation_cheap-n-cheerful-theme.adoc
+++ b/adocs/documentation/src/main/asciidoc/guides/_ug_wicket-viewer_customisation_cheap-n-cheerful-theme.adoc
@@ -22,7 +22,7 @@ You can therefore use this CSS class as a way of building your own "theme" for t
[TIP]
====
-Alternatively you could "do it properly" and create your xref:ug.adoc#_ug_extending_wicket-viewer_custom-bootstrap-theme[own Bootstrap theme], as described in the <<Extending>> chapter.
+Alternatively you could "do it properly" and create your xref:ug.adoc#_ug_extending_wicket-viewer_custom-bootstrap-theme[own Bootstrap theme], as described in the xref:ug.adoc#_ug_extending[Extending] chapter.
====
http://git-wip-us.apache.org/repos/asf/isis/blob/fe19dc4b/adocs/documentation/src/main/asciidoc/guides/_ug_wicket-viewer_customisation_custom-javascript.adoc
----------------------------------------------------------------------
diff --git a/adocs/documentation/src/main/asciidoc/guides/_ug_wicket-viewer_customisation_custom-javascript.adoc b/adocs/documentation/src/main/asciidoc/guides/_ug_wicket-viewer_customisation_custom-javascript.adoc
index 908a1f2..85ce627 100644
--- a/adocs/documentation/src/main/asciidoc/guides/_ug_wicket-viewer_customisation_custom-javascript.adoc
+++ b/adocs/documentation/src/main/asciidoc/guides/_ug_wicket-viewer_customisation_custom-javascript.adoc
@@ -10,12 +10,12 @@ The Wicket viewer ships with embedded JQuery, so this can be leveraged to perfor
[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 Isis might break your code.
+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.
If possible, consider using the `ComponentFactory` API described in the xref:ug.adoc#_ug_extending_wicket-viewer[Extending] chapter.
====
-To register your Javascript code, adjusting the Guice bindings (part of Isis' bootstrapping) in your custom subclass of `IsisWicketApplication`:
+To register your Javascript code, adjusting the Guice bindings (part of Apache Isis' bootstrapping) in your custom subclass of `IsisWicketApplication`:
public class MyAppApplication extends IsisWicketApplication {
@Override
http://git-wip-us.apache.org/repos/asf/isis/blob/fe19dc4b/adocs/documentation/src/main/asciidoc/guides/_ug_wicket-viewer_customisation_default-theme.adoc
----------------------------------------------------------------------
diff --git a/adocs/documentation/src/main/asciidoc/guides/_ug_wicket-viewer_customisation_default-theme.adoc b/adocs/documentation/src/main/asciidoc/guides/_ug_wicket-viewer_customisation_default-theme.adoc
index 8746e09..8d7dfee 100644
--- a/adocs/documentation/src/main/asciidoc/guides/_ug_wicket-viewer_customisation_default-theme.adoc
+++ b/adocs/documentation/src/main/asciidoc/guides/_ug_wicket-viewer_customisation_default-theme.adoc
@@ -6,7 +6,7 @@
-The 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 Isis Wicket viewer uses http://getbootstrap.com/[Bootstrap] styles and components (courtesy of the https://github.com/l0rdn1kk0n/wicket-bootstrap[Wicket Bootstrap] integration).
Unless specified otherwise, the viewer uses the default bootstrap theme. However, this can be changed by overriding `init()` in the application's subclass of `IsisWicketApplication`. For example, to set the http://bootswatch.com/flatly/[bootswatch.com flatly] theme
as the default, use:
http://git-wip-us.apache.org/repos/asf/isis/blob/fe19dc4b/adocs/documentation/src/main/asciidoc/guides/_ug_wicket-viewer_customisation_using-different-css-file.adoc
----------------------------------------------------------------------
diff --git a/adocs/documentation/src/main/asciidoc/guides/_ug_wicket-viewer_customisation_using-different-css-file.adoc b/adocs/documentation/src/main/asciidoc/guides/_ug_wicket-viewer_customisation_using-different-css-file.adoc
index 118d831..c09e871 100644
--- a/adocs/documentation/src/main/asciidoc/guides/_ug_wicket-viewer_customisation_using-different-css-file.adoc
+++ b/adocs/documentation/src/main/asciidoc/guides/_ug_wicket-viewer_customisation_using-different-css-file.adoc
@@ -6,7 +6,7 @@
-If for some reason you wanted to name the CSS file differently (eg `stylesheets/myapp.css`), then adjust the Guice bindings (part of Isis' bootstrapping) in your custom subclass of `IsisWicketApplication`:
+If for some reason you wanted to name the CSS file differently (eg `stylesheets/myapp.css`), then adjust the Guice bindings (part of Apache Isis' bootstrapping) in your custom subclass of `IsisWicketApplication`:
[source,java]
----
http://git-wip-us.apache.org/repos/asf/isis/blob/fe19dc4b/adocs/documentation/src/main/asciidoc/guides/_ug_wicket-viewer_customisation_welcome-page.adoc
----------------------------------------------------------------------
diff --git a/adocs/documentation/src/main/asciidoc/guides/_ug_wicket-viewer_customisation_welcome-page.adoc b/adocs/documentation/src/main/asciidoc/guides/_ug_wicket-viewer_customisation_welcome-page.adoc
index bb3d26c..f1f83fb 100644
--- a/adocs/documentation/src/main/asciidoc/guides/_ug_wicket-viewer_customisation_welcome-page.adoc
+++ b/adocs/documentation/src/main/asciidoc/guides/_ug_wicket-viewer_customisation_welcome-page.adoc
@@ -6,7 +6,7 @@
-It's possible to customize the application name, welcome message and about message can also be customized. This is done by adjusting the Guice bindings (part of Isis' bootstrapping) in your custom subclass of `IsisWicketApplication`:
+It's possible to customize the application name, welcome message and about message can also be customized. This is done by adjusting the Guice bindings (part of Apache Isis' bootstrapping) in your custom subclass of `IsisWicketApplication`:
[source,java]
----
http://git-wip-us.apache.org/repos/asf/isis/blob/fe19dc4b/adocs/documentation/src/main/asciidoc/guides/_ug_wicket-viewer_features_user-registration.adoc
----------------------------------------------------------------------
diff --git a/adocs/documentation/src/main/asciidoc/guides/_ug_wicket-viewer_features_user-registration.adoc b/adocs/documentation/src/main/asciidoc/guides/_ug_wicket-viewer_features_user-registration.adoc
index c425960..13e8fb6 100644
--- a/adocs/documentation/src/main/asciidoc/guides/_ug_wicket-viewer_features_user-registration.adoc
+++ b/adocs/documentation/src/main/asciidoc/guides/_ug_wicket-viewer_features_user-registration.adoc
@@ -21,7 +21,7 @@ To support this the framework requires three services to be registered and confi
* the xref:rg.adoc#_rg_services-spi_manpage-EmailNotificationService[email notification service], which provides an API for to send the verification emails
* the xref:rg.adoc#_rg_services-api_manpage-EmailService[email service], that is used by the email notification service to actually send the email.
-The Isis core framework provides a default implementation of both the email notification service and the email service. If your application uses the https://github.com/isisaddons/isis-module-security[Isis addons security module] (not ASF) then an implementation is provided by that module; just add to the classpath. Otherwise you will need to provide your own implementation.
+The Apache Isis core framework provides a default implementation of both the email notification service and the email service. If your application uses the https://github.com/isisaddons/isis-module-security[Isis addons security module] (not ASF) then an implementation is provided by that module; just add to the classpath. Otherwise you will need to provide your own implementation.
[NOTE]
====
http://git-wip-us.apache.org/repos/asf/isis/blob/fe19dc4b/adocs/documentation/src/main/asciidoc/guides/_ug_wicket-viewer_isis-addons.adoc
----------------------------------------------------------------------
diff --git a/adocs/documentation/src/main/asciidoc/guides/_ug_wicket-viewer_isis-addons.adoc b/adocs/documentation/src/main/asciidoc/guides/_ug_wicket-viewer_isis-addons.adoc
index 5333990..5be6765 100644
--- a/adocs/documentation/src/main/asciidoc/guides/_ug_wicket-viewer_isis-addons.adoc
+++ b/adocs/documentation/src/main/asciidoc/guides/_ug_wicket-viewer_isis-addons.adoc
@@ -5,11 +5,11 @@
:_imagesdir: images/
-The (non-ASF) link:http://www.isisaddons.org[Isis Addons] website provides a number of extensions to the Wicket viewer (leveraging the APIs described in <<Extending the Wicket viewer>> section, later. While you are free to fork and adapt any of them to your needs, they are also intended for use "out-of-the-box".
+The (non-ASF) link:http://www.isisaddons.org[Isis Addons] website provides a number of extensions to the Wicket viewer (leveraging the APIs described in xref:ug.adoc#_ug_extending_wicket-viewer[Extending the Wicket viewer] section, later. While you are free to fork and adapt any of them to your needs, they are also intended for use "out-of-the-box".
[WARNING]
====
-Note that Isis addons, while maintained by Isis committers, are not part of the ASF.
+Note that Isis addons, while maintained by Apache Isis committers, are not part of the ASF.
====
This short section gives an overview of their capabilities. For full information, check out the README on their respective github repo. Each wicket extension also includes a demo app so you can (a) see what the extension does and (b) see how to use it within your own code.
http://git-wip-us.apache.org/repos/asf/isis/blob/fe19dc4b/adocs/documentation/src/main/asciidoc/guides/_ug_wicket-viewer_layout.adoc
----------------------------------------------------------------------
diff --git a/adocs/documentation/src/main/asciidoc/guides/_ug_wicket-viewer_layout.adoc b/adocs/documentation/src/main/asciidoc/guides/_ug_wicket-viewer_layout.adoc
index 327a345..f164959 100644
--- a/adocs/documentation/src/main/asciidoc/guides/_ug_wicket-viewer_layout.adoc
+++ b/adocs/documentation/src/main/asciidoc/guides/_ug_wicket-viewer_layout.adoc
@@ -15,7 +15,7 @@ Dynamic reloading is automatically supported when running in xref:ug.adoc#_ug_ru
====
To pick up a change, edit the `.layout.json` file in the IDE and rebuild. Then click on the title of the object _*twice*_.
-The first click will cause Isis to pick up the new metadata, but too late in the process to adjust the rendering. The second click will re-render the object with the new metadata.
+The first click will cause Apache Isis to pick up the new metadata, but too late in the process to adjust the rendering. The second click will re-render the object with the new metadata.
====
@@ -92,6 +92,6 @@ Therefore, make sure the following is added to the dom project's `pom.xml`:
</resources>
----
-If using an Isis xref:ug.adoc#_ug_getting-started_simpleapp-archetype[SimpleApp archetype], then the POM is already correctly configured.
+If using an Apache Isis xref:ug.adoc#_ug_getting-started_simpleapp-archetype[SimpleApp archetype], then the POM is already correctly configured.
http://git-wip-us.apache.org/repos/asf/isis/blob/fe19dc4b/adocs/documentation/src/main/asciidoc/introducing-apache-isis/isis-in-pictures/isis-in-pictures.adoc
----------------------------------------------------------------------
diff --git a/adocs/documentation/src/main/asciidoc/introducing-apache-isis/isis-in-pictures/isis-in-pictures.adoc b/adocs/documentation/src/main/asciidoc/introducing-apache-isis/isis-in-pictures/isis-in-pictures.adoc
index 9b6e8de..57f840d 100644
--- a/adocs/documentation/src/main/asciidoc/introducing-apache-isis/isis-in-pictures/isis-in-pictures.adoc
+++ b/adocs/documentation/src/main/asciidoc/introducing-apache-isis/isis-in-pictures/isis-in-pictures.adoc
@@ -1,5 +1,5 @@
[[isis-in-pictures]]
-= Isis in Pictures
+= Apache Isis 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 agreed to in writing, software distributed under the License is distributed on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the License for the specific language governing permissions and limitations under the License.
:_basedir: ../../
:_imagesdir: images/
http://git-wip-us.apache.org/repos/asf/isis/blob/fe19dc4b/adocs/documentation/src/main/asciidoc/key-generation.adoc
----------------------------------------------------------------------
diff --git a/adocs/documentation/src/main/asciidoc/key-generation.adoc b/adocs/documentation/src/main/asciidoc/key-generation.adoc
index 013be2e..aa8ca53 100644
--- a/adocs/documentation/src/main/asciidoc/key-generation.adoc
+++ b/adocs/documentation/src/main/asciidoc/key-generation.adoc
@@ -504,7 +504,7 @@ Finally, commit your changes.
=== Save to `KEYS`
-The armored representation of the public key should be saved to Isis' `KEYS` file, http://www.apache.org/dist/isis/KEYS[http://www.apache.org/dist/isis/KEYS] (that is, in the ASF distribution directory for Isis).
+The armored representation of the public key should be saved to Apache Isis' `KEYS` file, http://www.apache.org/dist/isis/KEYS[http://www.apache.org/dist/isis/KEYS] (that is, in the ASF distribution directory for Apache Isis).
First, in a new directory, checkout this file:
http://git-wip-us.apache.org/repos/asf/isis/blob/fe19dc4b/adocs/documentation/src/main/asciidoc/pmc-notes.adoc
----------------------------------------------------------------------
diff --git a/adocs/documentation/src/main/asciidoc/pmc-notes.adoc b/adocs/documentation/src/main/asciidoc/pmc-notes.adoc
index 50e0fbe..8ccbadb 100644
--- a/adocs/documentation/src/main/asciidoc/pmc-notes.adoc
+++ b/adocs/documentation/src/main/asciidoc/pmc-notes.adoc
@@ -50,7 +50,7 @@ to list committers
list_committee.pl isis
----
-to list the PMC committee members (in Isis, every committer should be on the PMC committee)
+to list the PMC committee members (in Apache Isis, every committer should be on the PMC committee)
To change membership of either the committers or the PMC, use:
http://git-wip-us.apache.org/repos/asf/isis/blob/fe19dc4b/adocs/documentation/src/main/asciidoc/powered-by.adoc
----------------------------------------------------------------------
diff --git a/adocs/documentation/src/main/asciidoc/powered-by.adoc b/adocs/documentation/src/main/asciidoc/powered-by.adoc
index 054745c..cc473f9 100644
--- a/adocs/documentation/src/main/asciidoc/powered-by.adoc
+++ b/adocs/documentation/src/main/asciidoc/powered-by.adoc
@@ -10,11 +10,11 @@
pass:[<br/><br/>]
-Here are some freely accessible (and sometimes open source) applications that are powered by Isis.
+Here are some freely accessible (and sometimes open source) applications that are powered by Apache Isis.
[TIP]
====
-If you have written an app in Isis that you'd like to share, please mention it on the link:./support.html[mailing list].
+If you have written an app in Apache Isis that you'd like to share, please mention it on the link:./support.html[mailing list].
====
@@ -31,7 +31,7 @@ image::{_imagesdir}powered-by/estatio-1.png[width="900px",link="{_imagesdir}powe
-Much of Isis' recent development has been driven out by the requirements of this application, so you can see for yourself how many of the features in Isis are used in real life.
+Much of Apache Isis' recent development has been driven out by the requirements of this application, so you can see for yourself how many of the features in Isis are used in real life.
Estatio is being deployed by [Eurocommercial Properties](http://www.eurocommercialproperties.com/), who sponsored the development of the framework in order to make Estatio a reality. Our heart-felt thanks to them for their investment.
@@ -82,8 +82,8 @@ The author, Christian Steinebach, wrote this demo part-time over the course of a
He went on:
-* Because this is a demo, there is a lot of room for improvement, but it does show how a relatively simple domain model can be brought 'alive' using Isis.
+* Because this is a demo, there is a lot of room for improvement, but it does show how a relatively simple domain model can be brought 'alive' using Apache Isis.
-The source code is available link:https://www.assembla.com/code/transportplanner/git/nodes[here] (note: it was written against a snapshot version of Isis).
+The source code is available link:https://www.assembla.com/code/transportplanner/git/nodes[here] (note: it was written against a snapshot version of Apache Isis).
http://git-wip-us.apache.org/repos/asf/isis/blob/fe19dc4b/adocs/documentation/src/main/asciidoc/release-notes.adoc
----------------------------------------------------------------------
diff --git a/adocs/documentation/src/main/asciidoc/release-notes.adoc b/adocs/documentation/src/main/asciidoc/release-notes.adoc
index f007185..1057b5e 100644
--- a/adocs/documentation/src/main/asciidoc/release-notes.adoc
+++ b/adocs/documentation/src/main/asciidoc/release-notes.adoc
@@ -182,7 +182,7 @@ Isis 1.8.0 incorporates the Wicket viewer, which was previously a separately rel
* link:https://issues.apache.org/jira/browse/ISIS-755[ISIS-755] - Allow external system data to be integrated and managed with an Apache Isis domain object
* link:https://issues.apache.org/jira/browse/ISIS-779[ISIS-779] - Refactor EventBusService as a @RequestScoped service, and have it own the guava EventBus as a field.
* link:https://issues.apache.org/jira/browse/ISIS-903[ISIS-903] - side locale.
-* link:https://issues.apache.org/jira/browse/ISIS-931[ISIS-931] - Make Isis faster to start.
+* link:https://issues.apache.org/jira/browse/ISIS-931[ISIS-931] - Make Apache Isis faster to start.
* link:https://issues.apache.org/jira/browse/ISIS-934[ISIS-934] - printed if running in prototype mode.
* link:https://issues.apache.org/jira/browse/ISIS-935[ISIS-935] - RO viewer should return a 404 exception if object not found.
* link:https://issues.apache.org/jira/browse/ISIS-936[ISIS-936] - memory) into core (metamodel and runtime)
@@ -312,7 +312,7 @@ Isis 1.8.0 incorporates the Wicket viewer, which was previously a separately rel
Moved to (non-ASF) link:http://isisaddons.org[Isis Addons]
-* link:https://issues.apache.org/jira/browse/ISIS-851[ISIS-851] - Remove modules from Isis core (available instead through isisaddons).
+* link:https://issues.apache.org/jira/browse/ISIS-851[ISIS-851] - Remove modules from Apache Isis core (available instead through isisaddons).
* link:https://issues.apache.org/jira/browse/ISIS-887[ISIS-887] - xxx modules, as now in isisaddons.
@@ -409,7 +409,7 @@ Isis core 1.6.0 also incorporates the Restful Objects viewer, Shiro Security and
* link:https://issues.apache.org/jira/browse/ISIS-796[ISIS-796] - lifecycle callback "updating()" is not firing
* link:https://issues.apache.org/jira/browse/ISIS-797[ISIS-797] - 'Restful objects' decodes json request body while this is not
* link:https://issues.apache.org/jira/browse/ISIS-801[ISIS-801] - Action method taking domain object paramater gets triggered automatically whenever instances of that object type is accessed
-* link:https://issues.apache.org/jira/browse/ISIS-812[ISIS-812] - Isis 1.5 blob mapping broken for PostgreSQL (when set to null)
+* link:https://issues.apache.org/jira/browse/ISIS-812[ISIS-812] - Apache Isis 1.5 blob mapping broken for PostgreSQL (when set to null)
* link:https://issues.apache.org/jira/browse/ISIS-818[ISIS-818] - wrapSkipRules does not execute action due to being hidden
* link:https://issues.apache.org/jira/browse/ISIS-821[ISIS-821] - Precision gets lost when double values are use in BigDecimal attributes
* link:https://issues.apache.org/jira/browse/ISIS-824[ISIS-824] - Generic repository is broken
@@ -502,7 +502,7 @@ Isis core 1.6.0 also incorporates the Restful Objects viewer, Shiro Security and
==== Task
* link:https://issues.apache.org/jira/browse/ISIS-751[ISIS-751] - Update NOTICE copyright dates
-* link:https://issues.apache.org/jira/browse/ISIS-792[ISIS-792] - up tasks for Isis 1.5.0 release
+* link:https://issues.apache.org/jira/browse/ISIS-792[ISIS-792] - up tasks for Apache Isis 1.5.0 release
@@ -529,7 +529,7 @@ Isis core 1.6.0 also incorporates the Restful Objects viewer, Shiro Security and
==== Task
-* link:https://issues.apache.org/jira/browse/ISIS-792[ISIS-792] - up tasks for Isis 1.5.0 release
+* link:https://issues.apache.org/jira/browse/ISIS-792[ISIS-792] - up tasks for Apache Isis 1.5.0 release
@@ -537,7 +537,7 @@ Isis core 1.6.0 also incorporates the Restful Objects viewer, Shiro Security and
==== Task
-* link:https://issues.apache.org/jira/browse/ISIS-792[ISIS-792] - up tasks for Isis 1.5.0 release
+* link:https://issues.apache.org/jira/browse/ISIS-792[ISIS-792] - up tasks for Apache Isis 1.5.0 release
@@ -552,7 +552,7 @@ Isis core 1.6.0 also incorporates the Restful Objects viewer, Shiro Security and
==== Task
* link:https://issues.apache.org/jira/browse/ISIS-751[ISIS-751] - Update NOTICE copyright dates
-* link:https://issues.apache.org/jira/browse/ISIS-792[ISIS-792] - up tasks for Isis 1.5.0 release
+* link:https://issues.apache.org/jira/browse/ISIS-792[ISIS-792] - up tasks for Apache Isis 1.5.0 release
@@ -562,7 +562,7 @@ Isis core 1.6.0 also incorporates the Restful Objects viewer, Shiro Security and
* link:https://issues.apache.org/jira/browse/ISIS-750[ISIS-750] - For consistency with CommandJdo, allow the serializedForm to be stored as a clob (rather than as a zipped byte array)
* link:https://issues.apache.org/jira/browse/ISIS-754[ISIS-754] - BDD tests speed improvement with DN options, through a new IsisConfigurationForTests
-* link:https://issues.apache.org/jira/browse/ISIS-788[ISIS-788] - Delete the Isis Blob/Clob Converter classes for JDO, since redundant.
+* link:https://issues.apache.org/jira/browse/ISIS-788[ISIS-788] - Delete the Apache Isis Blob/Clob Converter classes for JDO, since redundant.
==== Bug
@@ -575,7 +575,7 @@ Isis core 1.6.0 also incorporates the Restful Objects viewer, Shiro Security and
==== Task
* link:https://issues.apache.org/jira/browse/ISIS-751[ISIS-751] - Update NOTICE copyright dates
-* link:https://issues.apache.org/jira/browse/ISIS-792[ISIS-792] - up tasks for Isis 1.5.0 release
+* link:https://issues.apache.org/jira/browse/ISIS-792[ISIS-792] - up tasks for Apache Isis 1.5.0 release
@@ -637,7 +637,7 @@ Isis core 1.6.0 also incorporates the Restful Objects viewer, Shiro Security and
* link:https://issues.apache.org/jira/browse/ISIS-662[ISIS-662] - Provide a "contributions" service to add a PublishedEvents contributed collection for the Interaction entity.
* link:https://issues.apache.org/jira/browse/ISIS-663[ISIS-663] - Provide a "contributions" service for AuditEntry, so that audit entries are shown as a contributed collection to the Interaction entity.
* link:https://issues.apache.org/jira/browse/ISIS-664[ISIS-664] - Provide an abstract class for running "sudo" scheduler jobs
-* link:https://issues.apache.org/jira/browse/ISIS-673[ISIS-673] - AbstractIsisSessionTemplate as a way to run arbitrary 'runnable' in an Isis session
+* link:https://issues.apache.org/jira/browse/ISIS-673[ISIS-673] - AbstractIsisSessionTemplate as a way to run arbitrary 'runnable' in an Apache Isis session
* link:https://issues.apache.org/jira/browse/ISIS-685[ISIS-685] - Add new @Command(async=true|false) flag, so that Command is automatically scheduled to run in the background
* link:https://issues.apache.org/jira/browse/ISIS-696[ISIS-696] - Extra overload for BookmarkService for lookup with downcast (making more consistent with API of MementoService).
* link:https://issues.apache.org/jira/browse/ISIS-697[ISIS-697] - Extend DeveloperUtilitiesService to be able to refresh services (for contributed actions)
@@ -694,7 +694,7 @@ Isis core 1.6.0 also incorporates the Restful Objects viewer, Shiro Security and
==== Task
-* link:https://issues.apache.org/jira/browse/ISIS-695[ISIS-695] - up tasks for Isis 1.4.0 release
+* link:https://issues.apache.org/jira/browse/ISIS-695[ISIS-695] - up tasks for Apache Isis 1.4.0 release
@@ -740,7 +740,7 @@ Isis core 1.6.0 also incorporates the Restful Objects viewer, Shiro Security and
==== Bug
* link:https://issues.apache.org/jira/browse/ISIS-429[ISIS-429] - coded dependency to WicketSignInPage in PageAbstract...
-* link:https://issues.apache.org/jira/browse/ISIS-617[ISIS-617] - Wicket viewer throws NPE when rendering Isis DateTime in a collection
+* link:https://issues.apache.org/jira/browse/ISIS-617[ISIS-617] - Wicket viewer throws NPE when rendering Apache Isis DateTime in a collection
* link:https://issues.apache.org/jira/browse/ISIS-620[ISIS-620] - When editing an entity twice a concurrency exception is thrown
* link:https://issues.apache.org/jira/browse/ISIS-621[ISIS-621] - Improve the Wicket viewer's parsing of numbers
* link:https://issues.apache.org/jira/browse/ISIS-629[ISIS-629] - Selecting a different option from a dropdown resets other fields
@@ -756,7 +756,7 @@ Isis core 1.6.0 also incorporates the Restful Objects viewer, Shiro Security and
==== Task
-* link:https://issues.apache.org/jira/browse/ISIS-695[ISIS-695] - up tasks for Isis 1.4.0 release
+* link:https://issues.apache.org/jira/browse/ISIS-695[ISIS-695] - up tasks for Apache Isis 1.4.0 release
@@ -764,7 +764,7 @@ Isis core 1.6.0 also incorporates the Restful Objects viewer, Shiro Security and
==== Task
-* link:https://issues.apache.org/jira/browse/ISIS-695[ISIS-695] - up tasks for Isis 1.4.0 release
+* link:https://issues.apache.org/jira/browse/ISIS-695[ISIS-695] - up tasks for Apache Isis 1.4.0 release
@@ -779,7 +779,7 @@ Isis core 1.6.0 also incorporates the Restful Objects viewer, Shiro Security and
==== Task
-* link:https://issues.apache.org/jira/browse/ISIS-695[ISIS-695] - up tasks for Isis 1.4.0 release
+* link:https://issues.apache.org/jira/browse/ISIS-695[ISIS-695] - up tasks for Apache Isis 1.4.0 release
@@ -823,7 +823,7 @@ Isis core 1.6.0 also incorporates the Restful Objects viewer, Shiro Security and
==== Bug
* link:https://issues.apache.org/jira/browse/ISIS-632[ISIS-632] - PublishingService's PublishedEvent id has an incorrect max length
-* link:https://issues.apache.org/jira/browse/ISIS-644[ISIS-644] - Update FrameworkSynchronizer to avoid the "Object not yet known to Isis" exception
+* link:https://issues.apache.org/jira/browse/ISIS-644[ISIS-644] - Update FrameworkSynchronizer to avoid the "Object not yet known to Apache Isis" exception
==== Dependency upgrade
@@ -834,7 +834,7 @@ Isis core 1.6.0 also incorporates the Restful Objects viewer, Shiro Security and
==== Task
-* link:https://issues.apache.org/jira/browse/ISIS-695[ISIS-695] - up tasks for Isis 1.4.0 release
+* link:https://issues.apache.org/jira/browse/ISIS-695[ISIS-695] - up tasks for Apache Isis 1.4.0 release
@@ -862,7 +862,7 @@ Isis core 1.6.0 also incorporates the Restful Objects viewer, Shiro Security and
==== Task
-* link:https://issues.apache.org/jira/browse/ISIS-581[ISIS-581] - Release tasks for Isis wicket viewer v1.3.1
+* link:https://issues.apache.org/jira/browse/ISIS-581[ISIS-581] - Release tasks for Apache Isis wicket viewer v1.3.1
@@ -958,7 +958,7 @@ Isis core 1.6.0 also incorporates the Restful Objects viewer, Shiro Security and
==== Task
-* link:https://issues.apache.org/jira/browse/ISIS-437[ISIS-437] - up tasks for Isis 1.3.0 and associated components.
+* link:https://issues.apache.org/jira/browse/ISIS-437[ISIS-437] - up tasks for Apache Isis 1.3.0 and associated components.
@@ -1001,11 +1001,11 @@ Isis core 1.6.0 also incorporates the Restful Objects viewer, Shiro Security and
* link:https://issues.apache.org/jira/browse/ISIS-520[ISIS-520] - type cmd line arg.
* link:https://issues.apache.org/jira/browse/ISIS-521[ISIS-521] - Xxx.layout.json is not read for abstract classes (as used for parented collections)
* link:https://issues.apache.org/jira/browse/ISIS-523[ISIS-523] - If max length of title in collections is 0, then suppress the title label also.
-* link:https://issues.apache.org/jira/browse/ISIS-525[ISIS-525] - Wicket tags should be stripped by default, overridable with an Isis property.
+* link:https://issues.apache.org/jira/browse/ISIS-525[ISIS-525] - Wicket tags should be stripped by default, overridable with an Apache Isis property.
* link:https://issues.apache.org/jira/browse/ISIS-527[ISIS-527] - focus on first field when edit an object or on action parameter.
* link:https://issues.apache.org/jira/browse/ISIS-530[ISIS-530] - ui
* link:https://issues.apache.org/jira/browse/ISIS-538[ISIS-538] - Improve performance of rendering lists (in Wicket viewer)
-* link:https://issues.apache.org/jira/browse/ISIS-547[ISIS-547] - Provide better error logging from the Wicket applicaiton init() method if Isis fails to boot.
+* link:https://issues.apache.org/jira/browse/ISIS-547[ISIS-547] - Provide better error logging from the Wicket applicaiton init() method if Apache Isis fails to boot.
* link:https://issues.apache.org/jira/browse/ISIS-558[ISIS-558] - When bulk action is invoked, the action that generated the collection should be resubmitted (so that a full refresh takes place).
@@ -1062,7 +1062,7 @@ Isis core 1.6.0 also incorporates the Restful Objects viewer, Shiro Security and
==== Improvement
-<li>Updated to run against Isis Core 1.3.0
+<li>Updated to run against Apache Isis Core 1.3.0
* link:https://issues.apache.org/jira/browse/ISIS-362[ISIS-362] - Upgrade to JMock 2.6.0
* link:https://issues.apache.org/jira/browse/ISIS-509[ISIS-509] - Tidy up and rationalize Util classes in core (and all dependents)
@@ -1078,7 +1078,7 @@ Isis core 1.6.0 also incorporates the Restful Objects viewer, Shiro Security and
* link:https://issues.apache.org/jira/browse/ISIS-427[ISIS-427] - specific), with JDO implementation.
* link:https://issues.apache.org/jira/browse/ISIS-450[ISIS-450] - session interaction between entities.
* link:https://issues.apache.org/jira/browse/ISIS-459[ISIS-459] - Enhance IsisJdoSupport service to support integration testing (execute arbitrary SQL, delete all instances of an entity)
-* link:https://issues.apache.org/jira/browse/ISIS-488[ISIS-488] - Derive Isis' MandatoryFacet from JDO @Column(allowNulls=) annotation, and provide @Mandatory annotation as override
+* link:https://issues.apache.org/jira/browse/ISIS-488[ISIS-488] - Derive Apache Isis' MandatoryFacet from JDO @Column(allowNulls=) annotation, and provide @Mandatory annotation as override
* link:https://issues.apache.org/jira/browse/ISIS-553[ISIS-553] - Provide view model support, as sketched out in the Restful Objects spec
@@ -1112,7 +1112,7 @@ Isis core 1.6.0 also incorporates the Restful Objects viewer, Shiro Security and
==== Task
-* link:https://issues.apache.org/jira/browse/ISIS-437[ISIS-437] - up tasks for Isis 1.3.0 and associated components.
+* link:https://issues.apache.org/jira/browse/ISIS-437[ISIS-437] - up tasks for Apache Isis 1.3.0 and associated components.
@@ -1135,7 +1135,7 @@ Isis core 1.6.0 also incorporates the Restful Objects viewer, Shiro Security and
* link:https://issues.apache.org/jira/browse/ISIS-360[ISIS-360] - About page on wicket viewer should show version, build number and other details.
* link:https://issues.apache.org/jira/browse/ISIS-367[ISIS-367] - Refactor to support JTA transactions
* link:https://issues.apache.org/jira/browse/ISIS-377[ISIS-377] - Publishing Service implementation that writes to a queue (using JDO).
-* link:https://issues.apache.org/jira/browse/ISIS-378[ISIS-378] - a service for prototyping that allows access into the internals of the Isis runtime
+* link:https://issues.apache.org/jira/browse/ISIS-378[ISIS-378] - a service for prototyping that allows access into the internals of the Apache Isis runtime
* link:https://issues.apache.org/jira/browse/ISIS-380[ISIS-380] - Enhance BookmarkService API to allow objects to be looked up directly (rather than by dint of a BookmarkHolder)
* link:https://issues.apache.org/jira/browse/ISIS-407[ISIS-407] - Annotation to automatically adjust end dates of ranges so that they are shown as inclusive vs exclusive.
* link:https://issues.apache.org/jira/browse/ISIS-409[ISIS-409] - Move the 'wrapper' progmodel component into core, reworked as an optional service
@@ -1174,7 +1174,7 @@ Isis core 1.6.0 also incorporates the Restful Objects viewer, Shiro Security and
==== New Feature
-* link:https://issues.apache.org/jira/browse/ISIS-328[ISIS-328] - Wicket viewer should shutdown Isis core on completion
+* link:https://issues.apache.org/jira/browse/ISIS-328[ISIS-328] - Wicket viewer should shutdown Apache Isis core on completion
* link:https://issues.apache.org/jira/browse/ISIS-344[ISIS-344] - Automatically exclude "parent references" from parented collections.
* link:https://issues.apache.org/jira/browse/ISIS-351[ISIS-351] - fatal, for rendering to the user.
* link:https://issues.apache.org/jira/browse/ISIS-360[ISIS-360] - About page on wicket viewer should show version, build number and other details.
@@ -1347,7 +1347,7 @@ Isis core 1.6.0 also incorporates the Restful Objects viewer, Shiro Security and
==== New Feature
-* link:https://issues.apache.org/jira/browse/ISIS-370[ISIS-370] - Provide a service to allow all @PersistenceCapable entities to be eagerly registered with Isis (and therefore with DataNucleus)
+* link:https://issues.apache.org/jira/browse/ISIS-370[ISIS-370] - Provide a service to allow all @PersistenceCapable entities to be eagerly registered with Apache Isis (and therefore with DataNucleus)
* link:https://issues.apache.org/jira/browse/ISIS-377[ISIS-377] - Publishing Service implementation that writes to a queue (using JDO).
* link:https://issues.apache.org/jira/browse/ISIS-379[ISIS-379] - Move AuditingService out of the ToDo app demo and into JDO objectstore as a service impl.
@@ -1417,7 +1417,7 @@ Isis core 1.6.0 also incorporates the Restful Objects viewer, Shiro Security and
==== Improvement
-* link:https://issues.apache.org/jira/browse/ISIS-89[ISIS-89] - Finish off updating documentation post the first (pre 1.0) release of Isis.
+* link:https://issues.apache.org/jira/browse/ISIS-89[ISIS-89] - Finish off updating documentation post the first (pre 1.0) release of Apache Isis.
* link:https://issues.apache.org/jira/browse/ISIS-131[ISIS-131] - Archive off (and no longer support) the default runtime's client/server remoting
* link:https://issues.apache.org/jira/browse/ISIS-188[ISIS-188] - 1.0.0 release.
* link:https://issues.apache.org/jira/browse/ISIS-192[ISIS-192] - based authorization
@@ -1438,7 +1438,7 @@ Isis core 1.6.0 also incorporates the Restful Objects viewer, Shiro Security and
* link:https://issues.apache.org/jira/browse/ISIS-261[ISIS-261] - Remove obsolete code (Enumeration interface, AnnotationBasedFacetFactory)
* link:https://issues.apache.org/jira/browse/ISIS-262[ISIS-262] - Real composite for ResourceSourceStream
* link:https://issues.apache.org/jira/browse/ISIS-267[ISIS-267] - Handle "recreating" object adapters which are already resolved
-* link:https://issues.apache.org/jira/browse/ISIS-274[ISIS-274] - Simplify the bootstrapping of Isis so that there are fewer configuration properties to set in isis.properties
+* link:https://issues.apache.org/jira/browse/ISIS-274[ISIS-274] - Simplify the bootstrapping of Apache Isis so that there are fewer configuration properties to set in isis.properties
* link:https://issues.apache.org/jira/browse/ISIS-280[ISIS-280] - More consistent support for @Prototype and @Exploration, by utilizing the existing HidingInteractionAdvisor API
* link:https://issues.apache.org/jira/browse/ISIS-281[ISIS-281] - Provide support for integration testing using a JUnit rule.
* link:https://issues.apache.org/jira/browse/ISIS-283[ISIS-283] - Provide the ability to use fixtures as domain objects, eg within demo apps
http://git-wip-us.apache.org/repos/asf/isis/blob/fe19dc4b/adocs/documentation/src/main/asciidoc/release-process.adoc
----------------------------------------------------------------------
diff --git a/adocs/documentation/src/main/asciidoc/release-process.adoc b/adocs/documentation/src/main/asciidoc/release-process.adoc
index 6e419bd..72d19a6 100644
--- a/adocs/documentation/src/main/asciidoc/release-process.adoc
+++ b/adocs/documentation/src/main/asciidoc/release-process.adoc
@@ -190,9 +190,9 @@ For example, if releasing `core` version `1.9.0`, the POM should read:
<version>1.9.0</version>
----
-=== Update parent (Isis Core)
+=== Update parent (Apache Isis Core)
-If releasing Isis Core, check (via link:http://search.maven.org/#search%7Cga%7C1%7Cg%3A%22org.apache%22%20a%3A%22apache%22[search.maven.org]) whether there is a newer version of the Apache parent `org.apache:apache`.
+If releasing Apache Isis Core, check (via link:http://search.maven.org/#search%7Cga%7C1%7Cg%3A%22org.apache%22%20a%3A%22apache%22[search.maven.org]) whether there is a newer version of the Apache parent `org.apache:apache`.
If there is, update the `<version>` in the `<parent>` element in the parent POM to match the newer version:
@@ -232,14 +232,14 @@ vi `/bin/find . -name pom.xml | grep -v target | sort`
[TIP]
====
-Obviously, don't update Isis' `SNAPSHOT` references; these get updated by the `mvn release:prepare` command we run later.
+Obviously, don't update Apache Isis' `SNAPSHOT` references; these get updated by the `mvn release:prepare` command we run later.
====
=== Update plugin versions
-The `maven-versions-plugin` should be used to determine if there are newer versions of any of the plugins used to build Isis. Since this goes off to the internet, it may take a minute or two to run:
+The `maven-versions-plugin` should be used to determine if there are newer versions of any of the plugins used to build Apache Isis. Since this goes off to the internet, it may take a minute or two to run:
[source,bash]
----
@@ -423,7 +423,7 @@ Next, delete all Isis artifacts from your local Maven repo:
rm -rf ~/.m2/repository/org/apache/isis
----
-Next, build the component, though without the offline flag. Maven should pull down the component's dependencies from the Maven central repo, including the non-spshot of Isis core:
+Next, build the component, though without the offline flag. Maven should pull down the component's dependencies from the Maven central repo, including the non-spshot of Apache Isis core:
[source,bash]
----
@@ -486,13 +486,13 @@ $ mvn release:prepare -P apache-release -D dryRun=true
[INFO] Reactor Build Order:
[INFO]
[INFO] Apache Isis Core
-[INFO] Isis Core AppLib
-[INFO] Isis Core Unit Test Support
-[INFO] Isis Core MetaModel
-[INFO] Isis Core Runtime
-[INFO] Isis Core WebServer
+[INFO] Apache Isis Core AppLib
+[INFO] Apache Isis Core Unit Test Support
+[INFO] Apache Isis Core MetaModel
+[INFO] Apache Isis Core Runtime
+[INFO] Apache Isis Core WebServer
...
-[INFO] Isis Core Integration Testing Support
+[INFO] Apache Isis Core Integration Testing Support
[INFO]
[INFO] ------------------------------------------------------------------------
[INFO] Building Apache Isis Core 1.9.0
@@ -727,7 +727,7 @@ Note that the email also references the procedure for other committers to link:v
Once the vote has completed, post the results to the isis-dev mailing list.
-For example, use the following subject for a vote on Isis Core:
+For example, use the following subject for a vote on Apache Isis Core:
[source,bash]
----
@@ -850,7 +850,7 @@ This moves the release artifacts into an Apache releases repository; from there
As described in the http://www.apache.org/dev/release-publishing.html#distribution_dist[Apache documentation], each Apache TLP has a `release/TLP-name` directory in the distribution Subversion repository at https://dist.apache.org/repos/dist[https://dist.apache.org/repos/dist]. Once a release vote passes, the release manager should `svn add` the artifacts (plus signature and hash files) into this location. The release is then automatically pushed to http://www.apache.org/dist/[http://www.apache.org/dist/] by `svnpubsub`. 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 Isis reflects the directory structure in our git source code repo:
+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:
[source]
----
@@ -900,13 +900,13 @@ If any of the tickets closed are tasks/subtasks, then please edit the contents o
=== Mark the JIRA versions as released
-In JIRA, go to the administration section for the Isis project and update the versions as released.
+In JIRA, go to the administration section for the Apache Isis project and update the versions as released.
=== Update ISIS website
-Update the Isis CMS website:
+Update the Apache Isis CMS website:
-* Using the JIRA-generated release notes as a guide, update the relevant page of the Isis site. +
+* Using the JIRA-generated release notes as a guide, update the relevant page of the Apache Isis site. +
+
Use this regex to convert links. From:
+
@@ -940,7 +940,7 @@ to:
Typically this be will a new page in the core section or for one of the components. Make a note of the URL of this new page (for use in the mailing list announcement).
-For example, a new release of Isis Core would require:
+For example, a new release of Apache Isis Core would require:
* Do a search for `x.y.0-SNAPSHOT` and replace with `x.y.0`
@@ -957,7 +957,7 @@ In addition:
For more information on DOAP files, see these http://projects.apache.org/doap.html[Apache policy docs].
-* The `STATUS` file (in root of Isis' source) should be updated with details of the new release.
+* The `STATUS` file (in root of Apache Isis' source) should be updated with details of the new release.
@@ -976,14 +976,14 @@ And use the following body (summarizing the main points as required):
[source]
----
-The Isis teamEnum is pleased to announce the release of:
+The Apache Isis team is pleased to announce the release of:
* Apache Isis Core version 1.9.0
* SimpleApp Archetype 1.9.0
New features in this release include:
- ...
-Full release notes are available on the Isis website at [1].
+Full release notes are available on the Apache Isis website at [1].
Note that:
* ...
@@ -993,7 +993,7 @@ or download the release and build it from source [3].
Enjoy!
---The Isis teamEnum
+--The Apache Isis team
[1] http://isis.apache.org/core/release-notes/isis-1.9.0.html
[2] http://search.maven.org
http://git-wip-us.apache.org/repos/asf/isis/blob/fe19dc4b/adocs/documentation/src/main/asciidoc/screencasts.adoc
----------------------------------------------------------------------
diff --git a/adocs/documentation/src/main/asciidoc/screencasts.adoc b/adocs/documentation/src/main/asciidoc/screencasts.adoc
index a772c2d..df3207d 100644
--- a/adocs/documentation/src/main/asciidoc/screencasts.adoc
+++ b/adocs/documentation/src/main/asciidoc/screencasts.adoc
@@ -21,7 +21,7 @@ We've prepared some screencasts to help you quickly see what Apache Isis has to
_How Apache Isis builds a webapp from the underlying domain object model_
-_This screencast is for Isis v1.1.0 (ie very out of date)_
+_This screencast is for Apache Isis v1.1.0 (ie very out of date)_
|video::ludOLyi6VyY[youtube,width="420px",height="315px"]
@@ -109,7 +109,7 @@ Learn more at the (non-ASF) Isis addons' http://github.com/isisaddons/isis-modul
-|Bulk updates in Isis (v1.5.0) +
+|Bulk updates in Apache Isis (v1.5.0) +
_Using the (non-ASF) http://github.com/isisaddons/isis-module-excel[Isis addons' excel] module and view models to perform bulk updates)._
http://git-wip-us.apache.org/repos/asf/isis/blob/fe19dc4b/adocs/documentation/src/main/asciidoc/simpleapp-archetype.adoc
----------------------------------------------------------------------
diff --git a/adocs/documentation/src/main/asciidoc/simpleapp-archetype.adoc b/adocs/documentation/src/main/asciidoc/simpleapp-archetype.adoc
index 6dd2b37..978e966 100644
--- a/adocs/documentation/src/main/asciidoc/simpleapp-archetype.adoc
+++ b/adocs/documentation/src/main/asciidoc/simpleapp-archetype.adoc
@@ -9,7 +9,7 @@
pass:[<br/><br/>]
-The quickest way to get started with Apache Isis is to run the simple archetype. This will generate a very simple one-class domain model, called `SimpleObject`, with a single property `name`. There is also a corresponding `SimpleObjectRepository` domain service. From this you can easily rename these initial classes, and extend to build up your own Isis domain application.
+The quickest way to get started with Apache Isis is to run the simple archetype. This will generate a very simple one-class domain model, called `SimpleObject`, with a single property `name`. There is also a corresponding `SimpleObjectRepository` domain service. From this you can easily rename these initial classes, and extend to build up your own Apache Isis domain application.
@@ -46,7 +46,7 @@ The archetype generation process will then run; it only takes a few seconds.
=== Snapshot release
-We also maintain the archetype for the most current `-SNAPSHOT`; an app generated with this archetype will contain the latest features of Isis, but the usual caveats apply: some features still in development may be unstable.
+We also maintain the archetype for the most current `-SNAPSHOT`; an app generated with this archetype will contain the latest features of Apache Isis, but the usual caveats apply: some features still in development may be unstable.
The process is almost identical to that for stable releases, however the `archetype:generate` goal is called with slightly different arguments:
@@ -71,7 +71,7 @@ where as before:
but also:
-- `archetypeVersion` is the SNAPSHOT version of Isis.
+- `archetypeVersion` is the SNAPSHOT version of Apache Isis.
- `archetypeRepository` specifies the location of our snapshot repo (hosted on [CloudBees](http://www.cloudbees.com)), and
The archetype generation process will then run; it only takes a few seconds.
@@ -100,7 +100,7 @@ The `simpleapp` archetype generates a single WAR file, configured to run both th
Once you've built the app, you can run the WAR in a variety of ways.
-The recommended approach when getting started is to run the self-hosting version of the WAR, allowing Isis to run as a standalone app; for example:
+The recommended approach when getting started is to run the self-hosting version of the WAR, allowing Apache Isis to run as a standalone app; for example:
[source,bash]
----
@@ -177,7 +177,7 @@ If you use IntelliJ or Eclipse, you'll also want to set up your IDE; this is als
== App Structure
-As noted above, the generated app is a very simple application consisting of a single domain object that can be easily renamed and extended. The intention is not to showcase all of Isis' capabilities; rather it is to allow you to very easily modify the generated application (eg rename `SimpleObject` to `Customer`) without having to waste time deleting lots of generated code.
+As noted above, the generated app is a very simple application consisting of a single domain object that can be easily renamed and extended. The intention is not to showcase all of Apache Isis' capabilities; rather it is to allow you to very easily modify the generated application (eg rename `SimpleObject` to `Customer`) without having to waste time deleting lots of generated code.
.Table caption
http://git-wip-us.apache.org/repos/asf/isis/blob/fe19dc4b/adocs/documentation/src/main/asciidoc/snapshot-process.adoc
----------------------------------------------------------------------
diff --git a/adocs/documentation/src/main/asciidoc/snapshot-process.adoc b/adocs/documentation/src/main/asciidoc/snapshot-process.adoc
index e233111..e0ed5c6 100644
--- a/adocs/documentation/src/main/asciidoc/snapshot-process.adoc
+++ b/adocs/documentation/src/main/asciidoc/snapshot-process.adoc
@@ -55,9 +55,9 @@ First, delete all Isis artifacts from your local Maven repo:
rm -rf ~/.m2/repository/org/apache/isis
----
-Next, check that the releasable module builds independently. The build process depends on whether the artifact is of Isis core or of one of its components:
+Next, check that the releasable module builds independently. The build process depends on whether the artifact is of Apache Isis core or of one of its components:
-* For Isis core, build using the `-o` offline flag: +
+* For Apache Isis core, build using the `-o` offline flag: +
+
[source,bash]
----
@@ -66,7 +66,7 @@ mvn clean install -o
+
Confirm that the versions of the Isis artifacts now cached in your local repository are correct.
-* For an Isis component, build without the offline flag; Maven should pull down the component's dependencies from the Maven central repo: +
+* For an Apache Isis component, build without the offline flag; Maven should pull down the component's dependencies from the Maven central repo: +
+
[source,bash]
----
http://git-wip-us.apache.org/repos/asf/isis/blob/fe19dc4b/adocs/documentation/src/main/asciidoc/verifying-releases-script.adoc
----------------------------------------------------------------------
diff --git a/adocs/documentation/src/main/asciidoc/verifying-releases-script.adoc b/adocs/documentation/src/main/asciidoc/verifying-releases-script.adoc
index b9e91d7..256990c 100644
--- a/adocs/documentation/src/main/asciidoc/verifying-releases-script.adoc
+++ b/adocs/documentation/src/main/asciidoc/verifying-releases-script.adoc
@@ -8,7 +8,7 @@
pass:[<br/><br/>]
-To save some time in verifying an Isis release we've assembled a script to automate the process. The script is tested on Mac OSX and Linux. Windows users can use Cygwin or http://msysgit.github.io/[msysgit].
+To save some time in verifying an Apache Isis release we've assembled a script to automate the process. The script is tested on Mac OSX and Linux. Windows users can use Cygwin or http://msysgit.github.io/[msysgit].
It's _recommended_ that you start this process in an empty directory:
@@ -53,7 +53,7 @@ _unpack(){
unzip -q '*.zip'
}
_build(){
- echo 'Removing Isis from local repo '$module
+ echo 'Removing Apache Isis from local repo '$module
rm -rf ~/.m2/repository/org/apache/isis
COUNTER=0
for module in ./*/
@@ -92,7 +92,7 @@ chmod +x verify-isis-release.sh
== Create an input file
-The input file is a plain `.txt` file containing all urls to the packages to be verified. Here's a sample of the release of Isis 1.8.0:
+The input file is a plain `.txt` file containing all urls to the packages to be verified. Here's a sample of the release of Apache Isis 1.8.0:
[source]
----
@@ -105,7 +105,7 @@ The actual list of packages to be verified will be provided through the mailing
-== Clean out Isis from your local Maven repo
+== Clean out Apache Isis from your local Maven repo
[source,bash]
----
http://git-wip-us.apache.org/repos/asf/isis/blob/fe19dc4b/adocs/documentation/src/main/asciidoc/verifying-releases.adoc
----------------------------------------------------------------------
diff --git a/adocs/documentation/src/main/asciidoc/verifying-releases.adoc b/adocs/documentation/src/main/asciidoc/verifying-releases.adoc
index 3b83a58..680186e 100644
--- a/adocs/documentation/src/main/asciidoc/verifying-releases.adoc
+++ b/adocs/documentation/src/main/asciidoc/verifying-releases.adoc
@@ -24,9 +24,9 @@ Note that the binaries are _not_ an ASF release, they merely exist on the Maven
== Prerequisites
-To verify the source ZIP files, you will need to have imported the public keys used for signing Isis releases. These can be downloaded from the root of the Isis source tree.
+To verify the source ZIP files, you will need to have imported the public keys used for signing Apache Isis releases. These can be downloaded from the root of the Apache Isis source tree.
-Since the Isis source is mirrored on github.com, you can just use:
+Since the Apache Isis source is mirrored on github.com, you can just use:
[source,bash]
----
@@ -68,14 +68,14 @@ rm -rf ~/.m2/repository/org/apache/isis
----
-To build Isis core, first download any dependencies:
+To build Apache Isis core, first download any dependencies:
[source]
----
mvn dependency:go-offline
----
-Check that no Isis artifacts have yet been downloaded, ie there is no `~/.m2/org/repository/org/apache/isis` directory. If there are, it could indicate that the release being verified incorrectly references previous versions of Isis core.
+Check that no Isis artifacts have yet been downloaded, ie there is no `~/.m2/org/repository/org/apache/isis` directory. If there are, it could indicate that the release being verified incorrectly references previous versions of Apache Isis core.
Assuming all is ok, build using the `-o` offline flag: