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:14 UTC
[2/4] isis-site git commit: ISIS-1133: convert 'Isis' to 'Apache Isis'
http://git-wip-us.apache.org/repos/asf/isis-site/blob/5b2b7c5e/content/guides/ug.html
----------------------------------------------------------------------
diff --git a/content/guides/ug.html b/content/guides/ug.html
index 94322c0..9398d33 100644
--- a/content/guides/ug.html
+++ b/content/guides/ug.html
@@ -646,7 +646,7 @@ table.CodeRay td.code>pre{padding:0}
</p></div></p>
</div>
<div class="paragraph">
-<p>You can learn much more about the pattern in the book, <a href="http://www.amazon.com/exec/obidos/ISBN=0470844205/">Naked Objects</a>, also freely available to <a href="http://www.nakedobjects.org/book/">read online</a>. Richard co-wrote the book with one of Isis' committers, Robert Matthews, who was in turn the author of the Naked Objects Framework for Java (the original codebase of of Apache Isis).</p>
+<p>You can learn much more about the pattern in the book, <a href="http://www.amazon.com/exec/obidos/ISBN=0470844205/">Naked Objects</a>, also freely available to <a href="http://www.nakedobjects.org/book/">read online</a>. 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 of Apache Isis).</p>
</div>
<div class="paragraph">
<p>You might also want to read Richard’s <a href="resources/core-concepts/Pawson-Naked-Objects-thesis.pdf">PhD on the subject</a>.</p>
@@ -762,13 +762,13 @@ table.CodeRay td.code>pre{padding:0}
<p>Associated with each port can be an <strong><em>adapter</em></strong> (in fact, Cockburn’s alternative name for this architecture is <strong><em>ports and adapters</em></strong>). An adapter is a device (piece of software) that talks in the protocol (or <em>API</em>) of the port. Each port could have several adapters.</p>
</div>
<div class="paragraph">
-<p>Apache Isis maps very nicely onto the <strong>hexagonal architecture</strong>. Isis' viewers act as user-side adapters and use the Isis 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 ORM implementing the JDO API. Most of the time this will be DataNucleus configured to persist to an RDBMS, but DataNucleus can also support other object stores, for example Neo4J. Alternatively Isis can be configured to persist using some other JDO implementation, for example Google App Engine.</p>
+<p>Apache Isis maps very nicely onto the <strong>hexagonal architecture</strong>. Apache Isis' viewers act as user-side adapters and use the Apache Isis 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 ORM implementing the JDO API. Most of the time this will be DataNucleus configured to persist to an RDBMS, but DataNucleus can also support other object stores, for example Neo4J. Alternatively Apache Isis can be configured to persist using some other JDO implementation, for example Google App Engine.</p>
</div>
</div>
<div class="sect3">
<h4 id="_ug_core-concepts_philosophy_aop">1.1.4. Aspect Oriented</h4>
<div class="paragraph">
-<p>Although not a book about object modelling, Evans' "Domain Driven Design" does use object orientation as its primary modelling tool; and many tend to think of <a href="#_ug_core-concepts_philosophy_domain-driven-design,DDD>> as an updated treatise on good object modelling">in the same vein as Rebecca Wirf Brock’s <a href="http://en.wikipedia.org/wiki/Responsibility-driven_design">Responsibility Driven Design</a>, say. Meanwhile the <<_naked_objects_pattern, naked objects pattern</a> very much comes from an OO background (it even has 'object' in its name); and Richard Pawson lists Alan Kay as a key influence.</p>
+<p>Although not a book about object modelling, Evans' "Domain Driven Design" does use object orientation as its primary modelling tool; and many tend to think of <a href="#_ug_core-concepts_philosophy_domain-driven-design,DDD>> as an updated treatise on good object modelling">in the same vein as Rebecca Wirf Brock’s <a href="http://en.wikipedia.org/wiki/Responsibility-driven_design">Responsibility Driven Design</a>, say. Meanwhile the xref:ug.adoc#_ug_core-concepts_philosophy_naked-objects-pattern[naked objects pattern</a> very much comes from an OO background (it even has 'object' in its name); and Richard Pawson lists Alan Kay as a key influence.</p>
</div>
<div class="paragraph">
<p>It’s certainly true that to develop an Apache Isis application you will need to have 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.</p>
@@ -789,7 +789,7 @@ table.CodeRay td.code>pre{padding:0}
</div>
</div>
<div class="sect4">
-<h5 id="_realization_within_isis">Realization within Isis</h5>
+<h5 id="_realization_within_apache_isis">Realization within Apache Isis</h5>
<div class="paragraph">
<p>What has all this to do with Apache Isis, then?</p>
</div>
@@ -806,10 +806,10 @@ table.CodeRay td.code>pre{padding:0}
<p>Apache Isis also has an internal event bus (you can switch between an underlying implementation of Gauva or Axon). 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 Isis applications are maintainable, and we discuss it in depth in the section on <a href="#_ug_more-advanced_decoupling">Decoupling</a>. But fundamentally its relying on this AOP concept of interceptors.</p>
</div>
<div class="paragraph">
-<p>Finally, Isis also a feature that is akin to AOP mix-ins. A "contributed action" is one that is implemented on a domain service but that appears to be a behaviour of rendered domain object. In other words, we can dissociate behaviour from data. That’s not always the right thing to do of course. In Richard Pawson’s description of the <a href="#_ug_core-concepts_philosophy_naked-objects-pattern">naked objects pattern</a> he talks about "behaviourally rich" objects, in other words where the business functionality encapsulated the data. But on the other hand sometimes the behaviour and data structures change at different rates. The <a href="http://en.wikipedia.org/wiki/Single_responsibility_principle">single responsibility principle</a> says we should only lump code together that changes at the same rate. Isis' support for contributions (not only contributed actions, but also contributed properties and contributed collections) enables this. And again, to loop bac
k to the topic of this section, it’s an AOP concept that being implemented by the framework.</p>
+<p>Finally, Isis also a feature that is akin to AOP mix-ins. A "contributed action" is one that is implemented on a domain service but that appears to be a behaviour of rendered domain object. In other words, we can dissociate behaviour from data. That’s not always the right thing to do of course. In Richard Pawson’s description of the <a href="#_ug_core-concepts_philosophy_naked-objects-pattern">naked objects pattern</a> he talks about "behaviourally rich" objects, in other words where the business functionality encapsulated the data. But on the other hand sometimes the behaviour and data structures change at different rates. The <a href="http://en.wikipedia.org/wiki/Single_responsibility_principle">single responsibility principle</a> 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. And again, to l
oop back to the topic of this section, it’s an AOP concept that being implemented by the framework.</p>
</div>
<div class="paragraph">
-<p>The nice thing about aspect orientation is that for the most part you can ignore these cross-cutting concerns and - at least initially at least - 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 Isis' AOP support for mixins (<a href="#_ug_more-advanced_decoupling_contributions">contributions</a>) and interceptors (the <a href="#_ug_more-advanced_decoupling_event-bus">event bus</a>) to ensure that your codebase remains maintainable.</p>
+<p>The nice thing about aspect orientation is that for the most part you can ignore these cross-cutting concerns and - at least initially at least - 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 mixins (<a href="#_ug_more-advanced_decoupling_contributions">contributions</a>) and interceptors (the <a href="#_ug_more-advanced_decoupling_event-bus">event bus</a>) to ensure that your codebase remains maintainable.</p>
</div>
</div>
</div>
@@ -836,7 +836,7 @@ challenges that <em>DDD</em> throws up and see how Apache Isis (and its impleme
<p>The word to pick up on here is <strong>conscious</strong>. It takes a conscious effort by the entire team to develop the ubiquitous language. 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.</p>
</div>
<div class="paragraph">
-<p>With Apache Isis, though, the ubiquitous language evolves with scarcely any effort at all. For the business experts, the Isis 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 work on.</p>
+<p>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. 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 work on.</p>
</div>
</div>
<div class="sect4">
@@ -881,7 +881,7 @@ challenges that <em>DDD</em> throws up and see how Apache Isis (and its impleme
<p>Because of Apache Isis' generic <em>OOUI</em>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 <strong>must</strong> be in the domain model because there is nowhere else to put it.</p>
</div>
<div class="paragraph">
-<p>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 Naked Objects and then deploy it on some other <em>J(2)EE</em> architecture, with a custom <em>UI</em> if you want. Isis guarantees that your domain model is complete.</p>
+<p>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 Naked Objects and then deploy it on some other <em>J(2)EE</em> architecture, with a custom <em>UI</em> if you want. Apache Isis guarantees that your domain model is complete.</p>
</div>
</div>
<div class="sect4">
@@ -1001,7 +1001,7 @@ WIP
</div>
</div>
<div class="sect3">
-<h4 id="_ug_core-concepts_principles_isis-itself">1.2.2. Isis itself</h4>
+<h4 id="_ug_core-concepts_principles_isis-itself">1.2.2. Apache Isis itself</h4>
<div class="paragraph">
<p>This section discusses some of the principles and values we apply to the development of the Apache Isis framework itself.</p>
</div>
@@ -1040,7 +1040,7 @@ TODO
<div class="ulist">
<ul>
<li>
-<p>Isis is at heart a metamodel with runtime, and coordinates interations using an AOP set of principles</p>
+<p>Apache Isis is at heart a metamodel with runtime, and coordinates interations using an AOP set of principles</p>
</li>
<li>
<p>Apache Isis vs Isis Addons</p>
@@ -1076,7 +1076,7 @@ TODO
<p>We’re working hard to remove duplication, reuse existing open source/JEE, and simplify.</p>
</div>
<div class="paragraph">
-<p>The areas of Isis we consider mature are those that have been developed in support of real-world applications implemented by the committers. Foremost among these is Estatio.</p>
+<p>The areas of Apache Isis we consider mature are those that have been developed in support of real-world applications implemented by the committers. Foremost among these is Estatio.</p>
</div>
<div class="paragraph">
<p>Focus on enterprise / line-of-business applications, for use by internal staff.</p>
@@ -1108,13 +1108,13 @@ do they compare to Apache Isis?</p>
<p>These frameworks all use the classic <strong>model-view-controller</strong> ( <em>MVC</em>) pattern for web applications, with scaffolding, code-generation, and/or metaprogramming tools for the controllers and views, as well as convention over configuration to define how these components interact. The views provided out of the box by these frameworks tend to be simple <em>CRUD</em>-style interfaces. More sophisticated behavior is accomplished by customizing the generated controllers.</p>
</div>
<div class="paragraph">
-<p>The most obvious difference when developing an Apache Isis application is its deliberate lack of an explicit controller layer; non- <em>CRUD</em> behavior is automatically made available in its generic object-oriented _UI_s. More sophisticated UIs can be built either by <a href="#_ug_extending_wicket-viewer">extending Isis' Wicket viewer</a> or by writing a bespoke UI leveraging the REST (hypermedia) API automatically exposed by <a href="#_ug_restfulobjects-viewer">Isis' Restful Objects viewer</a>. Other frameworks can also be used to implement REST APIs, of course, but generally they require a significant amount of development to get anywhere near the level of sophistication provided automatically by Isis' REST API.</p>
+<p>The most obvious difference when developing an Apache Isis application is its deliberate lack of an explicit controller layer; non- <em>CRUD</em> behavior is automatically made available in its generic object-oriented _UI_s. More sophisticated UIs can be built either by <a href="#_ug_extending_wicket-viewer">extending Apache Isis' Wicket viewer</a> or by writing a bespoke UI leveraging the REST (hypermedia) API automatically exposed by <a href="#_ug_restfulobjects-viewer">Isis' Restful Objects viewer</a>. Other frameworks can also be used to implement REST APIs, of course, but generally they require a significant amount of development to get anywhere near the level of sophistication provided automatically by Apache Isis' REST API.</p>
</div>
<div class="paragraph">
-<p>Although these frameworks all provide their own ecosystems of extensions, Isis' equivalent <a href="http://www.isisaddons.org">Isis Addons</a> (non-ASF) tend to work at a higher-level of abstraction. For example, each of these frameworks will integrate with various security mechanism, but the <a href="http://github.com/isisaddons/isis-module-security">Isis addons' security module</a> provides a full subdomain of users, roles, features and permissions that can be plugged into any Isis application. Similarly, the <a href="http://github.com/isisaddons/isis-module-command">Isis addons' command</a> and <a href="http://github.com/isisaddons/isis-module-audit">Isis addons' audit</a> modules in combination provide a support for auditing and traceability that can also be used for out of the box profiling. Again, these addons can be plugged into any Isis app.</p>
+<p>Although these frameworks all provide their own ecosystems of extensions, Apache Isis' equivalent <a href="http://www.isisaddons.org">Isis Addons</a> (non-ASF) tend to work at a higher-level of abstraction. For example, each of these frameworks will integrate with various security mechanism, but the <a href="http://github.com/isisaddons/isis-module-security">Isis addons' security module</a> provides a full subdomain of users, roles, features and permissions that can be plugged into any Isis application. Similarly, the <a href="http://github.com/isisaddons/isis-module-command">Isis addons' command</a> and <a href="http://github.com/isisaddons/isis-module-audit">Isis addons' audit</a> modules in combination provide a support for auditing and traceability that can also be used for out of the box profiling. Again, these addons can be plugged into any Isis app.</p>
</div>
<div class="paragraph">
-<p>In terms of testing support, each of these other frameworks provide mechanisms to allow the webapp to be tested from within a JUnit test harness. Isis' support is similar. Where Isis differs though is that it enables end-to-end testing without the need for slow and fragile Selenium tests. Instead, Isis provides a "<a href="#_ug_testing_integ-test-support_wrapper-factory">WrapperFactory</a>" domain service that allows the generic UI provided to in essence be simulated. On a more pragmatic level, the <a href="http://github.com/isisaddons/isis-module-fakedata">Isis addons' fakedata</a> module does "what it says on the tin", allowing both unit- and integration-tests to focus on the salient data and fake out the rest.</p>
+<p>In terms of testing support, each of these other frameworks provide mechanisms to allow the webapp to be tested from within a JUnit test harness. Apache Isis' support is similar. Where Apache Isis differs though is that it enables end-to-end testing without the need for slow and fragile Selenium tests. Instead, Apache Isis provides a "<a href="#_ug_testing_integ-test-support_wrapper-factory">WrapperFactory</a>" domain service that allows the generic UI provided to in essence be simulated. On a more pragmatic level, the <a href="http://github.com/isisaddons/isis-module-fakedata">Isis addons' fakedata</a> module does "what it says on the tin", allowing both unit- and integration-tests to focus on the salient data and fake out the rest.</p>
</div>
</div>
<div class="sect4">
@@ -1174,7 +1174,7 @@ TODO
<p>In contrast, Apache Isis is full-stack and does generate a complete UI; we then allow you to customize or extend this UI (as per the various <a href="http://www.isisaddons.org">Isis Addons</a> (non-ASF), and we also provide a full REST API through the <a href="#_ug_restfulobjects-viewer">Restful Objects viewer</a></p>
</div>
<div class="paragraph">
-<p>Also, it’s worth noting that MetaWidget does have an elegant pipeline architecture, with APIs to allow even its metamodel to be replaced. It would be feasible and probably quite straightforward to use Isis' own metamodel as an implementation of the MetaWidget API. This would allow MetaWidget to be able to render an Isis domain application.</p>
+<p>Also, it’s worth noting that MetaWidget does have an elegant pipeline architecture, with APIs to allow even its metamodel to be replaced. It would be feasible and probably quite straightforward to use Apache Isis' own metamodel as an implementation of the MetaWidget API. This would allow MetaWidget to be able to render an Apache Isis domain application.</p>
</div>
</div>
<div class="sect4">
@@ -1327,7 +1327,7 @@ TODO
<p>Domain services consist of a set of logically grouped actions, and as such follow the same conventions as for entities. However, a service cannot have (persisted) properties, nor can it have (persisted) collections.</p>
</div>
<div class="paragraph">
-<p>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. Isis will automatically inject services into every domain entity that requests them, and into each other.</p>
+<p>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. Apache Isis will automatically inject services into every domain entity that requests them, and into each other.</p>
</div>
<div class="paragraph">
<p>For convenience you can inherit from AbstractService or one of its subclasses, but this is not mandatory.</p>
@@ -1534,7 +1534,7 @@ TODO
</td>
<td class="content">
<div class="paragraph">
-<p>Note that Isis addons, while maintained by Isis committers, are not part of the ASF.</p>
+<p>Note that Isis addons, while maintained by Apache Isis committers, are not part of the ASF.</p>
</div>
</td>
</tr>
@@ -1548,7 +1548,7 @@ TODO
<li>
<p>modules that provide an implementations of API defined by Apache Isis<br></p>
<div class="paragraph">
-<p>where Isis has hooks to use the service if defined by provides no implementations of its own. The <a href="http://github.com/isisaddons/isis-module-command">command</a>, <a href="http://github.com/isisaddons/isis-module-audit">auditing</a>, <a href="http://github.com/isisaddons/isis-module-publishing">publishing</a>, <a href="http://github.com/isisaddons/isis-module-security">security</a> and <a href="http://github.com/isisaddons/isis-module-sessionlogger">sessionlogger</a> modules fall into this category. Typically the domain objects themselves wouldn’t interact with these services</p>
+<p>where Apache Isis has hooks to use the service if defined by provides no implementations of its own. The <a href="http://github.com/isisaddons/isis-module-command">command</a>, <a href="http://github.com/isisaddons/isis-module-audit">auditing</a>, <a href="http://github.com/isisaddons/isis-module-publishing">publishing</a>, <a href="http://github.com/isisaddons/isis-module-security">security</a> and <a href="http://github.com/isisaddons/isis-module-sessionlogger">sessionlogger</a> modules fall into this category. Typically the domain objects themselves wouldn’t interact with these services</p>
</div>
</li>
<li>
@@ -1581,12 +1581,12 @@ TODO
<p>Apache Isis 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.</p>
</div>
<div class="paragraph">
-<p>But there are other ways that you can make Isis work for you; in this chapter we explore a few of them.</p>
+<p>But there are other ways that you can make Apache Isis work for you; in this chapter we explore a few of them.</p>
</div>
<div class="sect3">
<h4 id="_deploy_to_production">1.6.1. Deploy to production</h4>
<div class="paragraph">
-<p>Let’s start though with the default use case for Isis: building line-of-business enterprise applications, on top of its Wicket viewer.</p>
+<p>Let’s start though with the default use case for Apache Isis: building line-of-business enterprise applications, on top of its Wicket viewer.</p>
</div>
<div class="paragraph">
<p>Apache Wicket, and therefore Apache Isis in this configuration, is a stateful architecture. As a platform it is certainly capable of supporting user bases of several thousand (with perhaps one or two hundred concurrent); however it isn’t an architecture that you should try to scale up to tens of thousands of concurrent users.</p>
@@ -1595,16 +1595,16 @@ TODO
<p>The UI UI generated by the Wicket viewer is well suited to many line-of-business apps, but it’s also worth knowing that (with a little knowledge of the Wicket APIs) it relatively straightforward to extend. As described in <a href="#_ug_core-concepts_add-ons">Isis addons</a> chapter, the viewer already has integrations with <a href="https://github.com/isisaddons/isis-wicket-gmap3">google maps</a>, <a href="https://github.com/isisaddons/isis-wicket-fullcalendar2">a full calendar</a> and an <a href="https://github.com/isisaddons/isis-wicket-excel">export to Excel</a> component. We are also aware of integrations with SVG images (for floor maps of shopping center) and of custom widgets displaying a catalogue (text and images) of medical diseases.</p>
</div>
<div class="paragraph">
-<p>Deploying on Isis means that the framework also manages object persistence. For many line-of-business applications this will mean using a relational database. It is also possible (courtesy of its integratinon with <a href="http://www.datanucleus.org">DataNucleus</a>) to deploy an Isis app to a NoSQL store such as Neo4J or MongoDB; and it is also possible to deploy to cloud platforms such as <a href="https://cloud.google.com/appengine/docs">Google App Engine (GAE)</a>.</p>
+<p>Deploying on Apache Isis means that the framework also manages object persistence. For many line-of-business applications this will mean using a relational database. It is also possible (courtesy of its integratinon with <a href="http://www.datanucleus.org">DataNucleus</a>) to deploy an Isis app to a NoSQL store such as Neo4J or MongoDB; and it is also possible to deploy to cloud platforms such as <a href="https://cloud.google.com/appengine/docs">Google App Engine (GAE)</a>.</p>
</div>
</div>
<div class="sect3">
<h4 id="_use_for_prototyping">1.6.2. Use for prototyping</h4>
<div class="paragraph">
-<p>Even if you don’t intend to deploy your application on top of Isis, there can be a lot of value in using Isis for prototyping. Because all you need do to get an app running is write domain objects, you can very quickly explore a domain object model and validate ideas with a domain expert.</p>
+<p>Even if you don’t intend to deploy your application on top of Apache Isis, there can be a lot of value in using Apache Isis for prototyping. Because all you need do to get an app running is write domain objects, you can very quickly explore a domain object model and validate ideas with a domain expert.</p>
</div>
<div class="paragraph">
-<p>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 teamEnum (business and technologists alike) have a shared understanding.</p>
+<p>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.</p>
</div>
<div class="paragraph">
<p>Once you’ve sketched out your domain model, you can then "start-over" using your preferred platform.</p>
@@ -1613,11 +1613,11 @@ TODO
<div class="sect3">
<h4 id="_deploy_on_your_own_platform">1.6.3. Deploy on your own platform</h4>
<div class="paragraph">
-<p>The programming model defined by Isis deliberately minimizes the dependencies on the rest of the framework. In fact, the only hard dependency that the domain model classes have on Isis is through the <code>org.apache.isis.applib</code> classes, mostly to pick up annotations such as <code>@Disabled</code>.
-So, if you have used Isis for prototyping (discussed above), then note that it’s quite feasible to take your domain model a the basis of your actual development effort; Isis' annotations and programming conventions will help ensure that any subtle semantics you might have captured in your prototyping are not lost.</p>
+<p>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 <code>org.apache.isis.applib</code> classes, mostly to pick up annotations such as <code>@Disabled</code>.
+So, if you have used Apache Isis for prototyping (discussed above), then note that it’s quite feasible to take your domain model a the basis of your actual development effort; Apache Isis' annotations and programming conventions will help ensure that any subtle semantics you might have captured in your prototyping are not lost.</p>
</div>
<div class="paragraph">
-<p>If you go this route, your deployment platform will of course need to provide similar capabilities to Isis. In particular, you’ll need to figure out a way to inject domain services into domain entities (eg using a JPA listener), and you’ll also need to reimplement any domain services you have used that Isis provides "out-of-the-box" (eg <a href="rg.html#_rg_services-api_manpage-QueryResultsCache"><code>QueryResultsCache</code></a> domain service).</p>
+<p>If you go this route, your deployment platform will of course need to provide similar capabilities to Apache Isis. In particular, you’ll need to figure out a way to inject domain services into domain entities (eg using a JPA listener), and you’ll also need to reimplement any domain services you have used that Apache Isis provides "out-of-the-box" (eg <a href="rg.html#_rg_services-api_manpage-QueryResultsCache"><code>QueryResultsCache</code></a> domain service).</p>
</div>
</div>
<div class="sect3">
@@ -1626,7 +1626,7 @@ So, if you have used Isis for prototyping (discussed above), then note that it&#
<p>REST (Representation State Transfer) is an architectural style for building highly scalable distributed systems, using the same principles as the World Wide Web. Many commercial web APIs (twitter, facebook, Amazon) are implemented as either pure REST APIs or some approximation therein.</p>
</div>
<div class="paragraph">
-<p>The <a href="http://restfulobjects.org">Restful Objects specification</a> defines a means by a domain object model can be exposed as RESTful resources using JSON representations over HTTP. Isis' <<_restfulobjects_viewer, Restful Objects viewer] is an implementation of that spec, making any Isis domain object automatically available via REST.</p>
+<p>The <a href="http://restfulobjects.org">Restful Objects specification</a> defines a means by a domain object model can be exposed as RESTful resources using JSON representations over HTTP. Apache Isis' <a href="#_ug_restfulobjects-viewer">RestfulObjects viewer</a> is an implementation of that spec, making any Apache Isis domain object automatically available via REST.</p>
</div>
<div class="paragraph">
<p>There are a number of use cases for deploying Isis as a REST API, including:</p>
@@ -1657,10 +1657,10 @@ So, if you have used Isis for prototyping (discussed above), then note that it&#
<div class="sect3">
<h4 id="_implement_your_own_viewer">1.6.5. Implement your own viewer</h4>
<div class="paragraph">
-<p>Isis' architecture was always designed to support multiple viewers; and indeed Isis out-of-the-box supports two: the Wicket viewer, and the Restful Objects viewer (or three, if one includes the Wrapper Factory).</p>
+<p>Isis' architecture was always designed to support multiple viewers; and indeed Apache Isis out-of-the-box supports two: the Wicket viewer, and the Restful Objects viewer (or three, if one includes the Wrapper Factory).</p>
</div>
<div class="paragraph">
-<p>While we mustn’t understate the effort involved here, it is feasible to implement your own viewers too. Indeed, one of Isis' committers does indeed have a (closed source) viewer, based on <a href="http://www.wavemaker.com/">Wavemaker</a>.</p>
+<p>While we mustn’t understate the effort involved here, it is feasible to implement your own viewers too. Indeed, one of Apache Isis' committers does indeed have a (closed source) viewer, based on <a href="http://www.wavemaker.com/">Wavemaker</a>.</p>
</div>
</div>
</div>
@@ -1673,7 +1673,7 @@ So, if you have used Isis for prototyping (discussed above), then note that it&#
<p>To get you up and running quickly, Apache Isis provides a <a href="#_ug_getting-started_simpleapp-archetype">SimpleApp archetype</a> to setup a simple application as the basis of your own apps. This is deliberately very minimal so that you won’t have to spend lots of time removing generated artifacts. On the other hand, it does set up a standard multi-module maven structure with unit- and integration tests pre-configured, as well as a webapp module so that you can easily run your app. We strongly recommend that you preserve this structure as you develop your own Isis application.</p>
</div>
<div class="paragraph">
-<p>In this chapter we also discuss the <a href="#_ug_getting-started_datanucleus-enhancer">DataNucleus enhancer</a>. <a href="http://www.datanucleus.org/">DataNucleus</a> is the reference implementation of the JDO (Java data objects) spec, and Isis integrates with DataNucleus as its persistence layer. The enhancer performs post-processing on the bytecode of your persistent domain entities, such that they can be persisted by Isis' JDO/DataNucleus objectstore.</p>
+<p>In this chapter we also discuss the <a href="#_ug_getting-started_datanucleus-enhancer">DataNucleus enhancer</a>. <a href="http://www.datanucleus.org/">DataNucleus</a> is the reference implementation of the JDO (Java data objects) spec, and Apache Isis integrates with DataNucleus as its persistence layer. The enhancer performs post-processing on the bytecode of your persistent domain entities, such that they can be persisted by Apache Isis' JDO/DataNucleus objectstore.</p>
</div>
<div class="admonitionblock note">
<table>
@@ -1683,7 +1683,7 @@ So, if you have used Isis for prototyping (discussed above), then note that it&#
</td>
<td class="content">
<div class="paragraph">
-<p>The <a href="#_ug_getting-started_simpleapp-archetype">SimpleApp archetype</a> automatically configures the enhancer, so there’s little you need to do at this stage. Even so we feel it’s a good idea to be aware of this critical part of Isis runtime; if the enhancer does not run, then you’ll find the app fails to start with (what will seem like) quite an obscure exception message.</p>
+<p>The <a href="#_ug_getting-started_simpleapp-archetype">SimpleApp archetype</a> automatically configures the enhancer, so there’s little you need to do at this stage. Even so we feel it’s a good idea to be aware of this critical part of Apache Isis runtime; if the enhancer does not run, then you’ll find the app fails to start with (what will seem like) quite an obscure exception message.</p>
</div>
</td>
</tr>
@@ -1705,7 +1705,7 @@ So, if you have used Isis for prototyping (discussed above), then note that it&#
</ul>
</div>
<div class="paragraph">
-<p>You’ll probably also want to use an IDE; the Isis committers use either IntelliJ or Eclipse; in the <a href="#_ug_appendices">appendices</a> we have detailed setup instructions for using these two IDEs. If you’re a NetBeans user you should have no problems as it too has strong support for Maven.</p>
+<p>You’ll probably also want to use an IDE; the Apache Isis committers use either IntelliJ or Eclipse; in the <a href="#_ug_appendices">appendices</a> we have detailed setup instructions for using these two IDEs. If you’re a NetBeans user you should have no problems as it too has strong support for Maven.</p>
</div>
<div class="paragraph">
<p>When building and running within an IDE, you’ll also need to configure the Datanucleus enhancer. This is implemented as a Maven plugin, so in the case of IntelliJ, it’s easy enough to run the enhancer as required. It should be just as straightforward for NetBeans too.</p>
@@ -1720,7 +1720,7 @@ So, if you have used Isis for prototyping (discussed above), then note that it&#
<p>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 <code>SimpleObject</code>, with a single property <code>name</code>.</p>
</div>
<div class="paragraph">
-<p>There is also a corresponding <code>SimpleObjectRepository</code> domain service. From this you can easily rename these initial classes, and extend to build up your own Isis domain application.</p>
+<p>There is also a corresponding <code>SimpleObjectRepository</code> domain service. From this you can easily rename these initial classes, and extend to build up your own Apache Isis domain application.</p>
</div>
<div class="sect3">
<h4 id="_generating_the_app">2.2.1. Generating the App</h4>
@@ -1762,7 +1762,7 @@ So, if you have used Isis for prototyping (discussed above), then note that it&#
<p>The archetype generation process will then run; it only takes a few seconds.</p>
</div>
<div class="paragraph">
-<p>We also maintain the archetype for the most current <code>-SNAPSHOT</code>; 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.</p>
+<p>We also maintain the archetype for the most current <code>-SNAPSHOT</code>; 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.</p>
</div>
<div class="paragraph">
<p>The process is almost identical to that for stable releases, however the <code>archetype:generate</code> goal is called with slightly different arguments:</p>
@@ -1802,7 +1802,7 @@ So, if you have used Isis for prototyping (discussed above), then note that it&#
<div class="ulist">
<ul>
<li>
-<p><code>archetypeVersion</code> is the SNAPSHOT version of Isis.</p>
+<p><code>archetypeVersion</code> is the SNAPSHOT version of Apache Isis.</p>
</li>
<li>
<p><code>archetypeRepository</code> specifies the location of our snapshot repo (hosted on <a href="http://www.cloudbees.com">CloudBees</a>), and</p>
@@ -2098,13 +2098,13 @@ script to be run.</p>
<p>Once you are familiar with the generated app, you’ll want to start modifying it. There is plenty of guidance on this site; check out the 'programming model how-tos' section on the main [documentation](../../documentation.html) page first).</p>
</div>
<div class="paragraph">
-<p>If you use Eclipse or IntelliJ IDEA, do also install the [Eclipse templates](../resources/editor-templates.html); these will help you follow the Isis naming conventions.</p>
+<p>If you use Eclipse or IntelliJ IDEA, do also install the [Eclipse templates](../resources/editor-templates.html); these will help you follow the Apache Isis naming conventions.</p>
</div>
</div>
<div class="sect3">
<h4 id="_app_structure">2.2.7. App Structure</h4>
<div class="paragraph">
-<p>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 <code>SimpleObject</code> to <code>Customer</code>) without having to waste time deleting lots of generated code.</p>
+<p>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 <code>SimpleObject</code> to <code>Customer</code>) without having to waste time deleting lots of generated code.</p>
</div>
<div class="paragraph">
<p><table class="table table-striped table-bordered table-condensed">
@@ -2124,7 +2124,7 @@ script to be run.</p>
<div class="sect2">
<h3 id="_ug_getting-started_datanucleus-enhancer">2.3. Datanucleus Enhancer</h3>
<div class="paragraph">
-<p><a href="http://www.datanucleus.org/">DataNucleus</a> is the reference implementation of the JDO (Java data objects) spec, and Isis integrates with DataNucleus as its persistence layer. Datanucleus is a very powerful library, allowing domain entities to be mapped not only to relational database tables, but also to NoSQL stores such as <a href="http://neo4j.com/">Neo4J</a>, <a href="http://www.mongodb.org/">MongoDB</a> and <a href="http://cassandra.apache.org/">Apache Cassandra</a>.</p>
+<p><a href="http://www.datanucleus.org/">DataNucleus</a> is the reference implementation of the JDO (Java data objects) spec, and Apache Isis integrates with DataNucleus as its persistence layer. Datanucleus is a very powerful library, allowing domain entities to be mapped not only to relational database tables, but also to NoSQL stores such as <a href="http://neo4j.com/">Neo4J</a>, <a href="http://www.mongodb.org/">MongoDB</a> and <a href="http://cassandra.apache.org/">Apache Cassandra</a>.</p>
</div>
<div class="paragraph">
<p>With such power comes a little bit of complexity to the development environment: all domain entities must be enhanced through the DataNucleus enhancer.</p>
@@ -2580,7 +2580,7 @@ every time, specify the following system properties:</p>
<div class="sect3">
<h4 id="_testing">3.1.7. Testing</h4>
<div class="paragraph">
-<p>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.</p>
+<p>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.</p>
</div>
<div class="ulist">
<ul>
@@ -2863,11 +2863,11 @@ every time, specify the following system properties:</p>
</tr>
<tr>
<td><i class="conum" data-value="5"></i><b>5</b></td>
-<td><code>@ObjectType</code> is used by Isis for its own internal "OID" identifier; this also appears in the URL in Isis' Wicket viewer and REST API</td>
+<td><code>@ObjectType</code> 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</td>
</tr>
<tr>
<td><i class="conum" data-value="6"></i><b>6</b></td>
-<td><code>@Bookmarkable</code> indicates that the object can be automatically bookmarked in Isis' Wicket viewer</td>
+<td><code>@Bookmarkable</code> indicates that the object can be automatically bookmarked in Apache Isis' Wicket viewer</td>
</tr>
</table>
</div>
@@ -3362,7 +3362,7 @@ mvn clean install</code></pre>
<div class="sect3">
<h4 id="_testing_2">3.2.7. Testing</h4>
<div class="paragraph">
-<p>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.</p>
+<p>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.</p>
</div>
<div class="ulist">
<ul>
@@ -3532,7 +3532,7 @@ mvn clean install</code></pre>
<p>specify an <a href="#_ug_how-tos_ui-hints_object-titles-and-icons">icon</a></p>
</li>
<li>
-<p>make the entity bookmarkable by adding the <<__code_domainobjectlayout_code,@DomainObjectLayout(bookmarking=…​)` annotation</p>
+<p>make the entity bookmarkable by adding the <a href="rg.html#_rg_annotations_manpage-DomainObjectLayout_bookmarking"><code>@DomainObjectLayout#bookmarking()</code></a> attribute.</p>
</li>
<li>
<p>confirm is available from bookmark panel (top-left of Wicket UI)</p>
@@ -4013,7 +4013,7 @@ mvn clean install</code></pre>
<p>likewise <a href="rg.html#_rg_annotations_manpage-Collection_hidden"><code>@Collection(hidden=…​)</code></a> for collections</p>
</li>
<li>
-<p>the <a href="rg.html#_rg_annotations_manpage-Programmatic"><code>@Programmatic</code></a> 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.</p>
+<p>the <a href="rg.html#_rg_annotations_manpage-Programmatic"><code>@Programmatic</code></a> 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.</p>
</li>
</ul>
</div>
@@ -4112,7 +4112,7 @@ mvn clean install</code></pre>
<div class="sect3">
<h4 id="_using_contributions">3.2.26. Using Contributions</h4>
<div class="paragraph">
-<p>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.</p>
+<p>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.</p>
</div>
<div class="paragraph">
<p>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).</p>
@@ -4238,7 +4238,7 @@ mvn clean install</code></pre>
<p>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.</p>
</div>
<div class="paragraph">
-<p>Under the covers Isis uses the <a href="https://code.google.com/p/guava-libraries/wiki/EventBusExplained">Guava event bus</a> and subscribers (always domain services) subscribe by writing methods annotated with <code>@com.google.common.eventbus.Subscribe</code> annotation.</p>
+<p>Under the covers Apache Isis uses the <a href="https://code.google.com/p/guava-libraries/wiki/EventBusExplained">Guava event bus</a> and subscribers (always domain services) subscribe by writing methods annotated with <code>@com.google.common.eventbus.Subscribe</code> annotation.</p>
</div>
<div class="paragraph">
<p>By default the events generated are <code>ActionDomainEvent.Default</code> (for actions) and <code>PropertyDomainEvent.Default</code> (for properties). Subclasses of these can be specified using the <a href="rg.html#_rg_annotations_manpage-Action_domainEvent"><code>@Action(domainEvent=…​)</code></a> or <a href="rg.html#_rg_annotations_manpage-Property_domainEvent"><code>Property(domainEvent=…​)</code></a> for properties.</p>
@@ -4414,10 +4414,10 @@ mvn clean install</code></pre>
<p>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.</p>
</div>
<div class="paragraph">
-<p>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.</p>
+<p>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.</p>
</div>
<div class="paragraph">
-<p>To support these use cases, Isis therefore allows you to write a view model, either by annotating the class with <a href="rg.html#_rg_annotations_manpage-ViewModel"><code>@ViewModel</code></a> or (for more control) by implementing the <a href="rg.html#_rg_classes_super_manpage-AbstractViewModel"><code>ViewModel</code></a> interface.</p>
+<p>To support these use cases, Apache Isis therefore allows you to write a view model, either by annotating the class with <a href="rg.html#_rg_annotations_manpage-ViewModel"><code>@ViewModel</code></a> or (for more control) by implementing the <a href="rg.html#_rg_classes_super_manpage-AbstractViewModel"><code>ViewModel</code></a> interface.</p>
</div>
<div class="ulist">
<ul>
@@ -4502,7 +4502,7 @@ mvn clean install</code></pre>
<div class="sect3">
<h4 id="_customising_the_rest_api">3.2.34. Customising the REST API</h4>
<div class="paragraph">
-<p>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.</p>
+<p>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.</p>
</div>
<div class="ulist">
<ul>
@@ -4530,7 +4530,7 @@ mvn clean install</code></pre>
<h2 id="_ug_how-tos">4. How tos</h2>
<div class="sectionbody">
<div class="paragraph">
-<p>This chapter provides instructions on how to go about actually developing Isis domain applications.</p>
+<p>This chapter provides instructions on how to go about actually developing Apache Isis domain applications.</p>
</div>
<div class="sect2">
<h3 id="_ug_how-tos_class-structure">4.1. Class Structure</h3>
@@ -4541,13 +4541,13 @@ mvn clean install</code></pre>
<p>In the automatically generated UI a property is rendered as a field. This can be either of a value type (a string, number, date, boolean etc) or can be a reference to another entity. A collection is generally rendered as a table.</p>
</div>
<div class="paragraph">
-<p>In order for Isis to build its metamodel the domain objects must follow some conventions: what we call the <em>Apache Isis Programming Model</em>. This is just an extension of the pojo / JavaBean standard of yesteryear: properties and collections are getters/setters, while actions are simply any remaining <code>public</code> methods.</p>
+<p>In order for Apache Isis to build its metamodel the domain objects must follow some conventions: what we call the <em>Apache Isis Programming Model</em>. This is just an extension of the pojo / JavaBean standard of yesteryear: properties and collections are getters/setters, while actions are simply any remaining <code>public</code> methods.</p>
</div>
<div class="paragraph">
<p>Additional metamodel semantics are inferred both imperatively from <em>supporting methods</em> and declaratively from annotations.</p>
</div>
<div class="paragraph">
-<p>In this section we discuss the mechanics of writing domain objects that comply with Isis programming model.</p>
+<p>In this section we discuss the mechanics of writing domain objects that comply with Apache Isis' programming model.</p>
</div>
<div class="admonitionblock tip">
<table>
@@ -4557,10 +4557,10 @@ mvn clean install</code></pre>
</td>
<td class="content">
<div class="paragraph">
-<p>In fact, Isis programming model is extensible; you can teach Isis 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.</p>
+<p>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. The only real fundamental that can’t be changed is the notion that objects consist of properties, collections and actions.</p>
</div>
<div class="paragraph">
-<p>You can learn more about extending Isis programming model <a href="#_ug_extending_programming-model">here</a>.</p>
+<p>You can learn more about extending Apache Isis programming model <a href="#_ug_extending_programming-model">here</a>.</p>
</div>
</td>
</tr>
@@ -4642,7 +4642,7 @@ WIP
<p>JDO/DataNucleus' default is that a property is assumed to be mandatory if it is a primitive type (eg <code>int</code>, <code>boolean</code>), but optional if a reference type (eg <code>String</code>, <code>BigDecimal</code> etc). To override optionality in JDO/DataNucleus the <code>@Column(allowsNull="…​")</code> annotations is used.</p>
</div>
<div class="paragraph">
-<p>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 Isis' own annotations, specifically <code>@Property(optionality=…​)</code>.</p>
+<p>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 <code>@Property(optionality=…​)</code>.</p>
</div>
<div class="paragraph">
<p>These different defaults can lead to incompatibilities between the two frameworks. To counteract that, Apache Isis also recognizes and honours JDO’s <code>@Column(allowsNull=…​)</code>.</p>
@@ -4718,7 +4718,7 @@ WIP
<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.</p>
</div>
<div class="paragraph">
-<p>In this situation we must tell JDO that the column is optional, but to Isis we want to enforce it being mandatory. This can be done using the <code>@Property(optionality=Optionality.MANDATORY)</code> annotation.</p>
+<p>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 <code>@Property(optionality=Optionality.MANDATORY)</code> annotation.</p>
</div>
<div class="paragraph">
<p>For example:</p>
@@ -4743,14 +4743,14 @@ WIP
</td>
<td class="content">
<div class="paragraph">
-<p>The <code>@Property(optionality=…​)</code> annotation is equivalent to the older but still supported <code>@Optional</code> annotation and <code>@Mandatory</code> annotations. Its benefit is that it lumps together all Isis' property metadata in a single annotation. Its downside is that it is rather verbose if the only semantic that needs to be specified — as is often the case — is optionality.</p>
+<p>The <code>@Property(optionality=…​)</code> annotation is equivalent to the older but still supported <code>@Optional</code> annotation and <code>@Mandatory</code> annotations. Its benefit is that it lumps together all Apache Isis' property metadata in a single annotation. Its downside is that it is rather verbose if the only semantic that needs to be specified — as is often the case — is optionality.</p>
</div>
</td>
</tr>
</table>
</div>
<div class="paragraph">
-<p>An alternative way to achieve this is to leave the JDO annotation on the field (where it is invisible to Isis), and rely on Isis' default, eg:</p>
+<p>An alternative way to achieve this is to leave the JDO annotation on the field (where it is invisible to Apache Isis), and rely on Isis' default, eg:</p>
</div>
<div class="listingblock">
<div class="content">
@@ -4758,7 +4758,7 @@ WIP
<span class="directive">public</span> <span class="type">class</span> <span class="class">SomeSubtype</span> <span class="directive">extends</span> SomeSuperType {
<span class="annotation">@javax</span>.jdo.annotations.Column(allowNulls=<span class="string"><span class="delimiter">"</span><span class="content">true</span><span class="delimiter">"</span></span>)
<span class="directive">private</span> LocalDate date;
- <span class="comment">// mandatory in Isis by default</span>
+ <span class="comment">// mandatory in Apache Isis by default</span>
<span class="directive">public</span> LocalDate getDate() { }
<span class="directive">public</span> <span class="type">void</span> setDate(LocalDate d) { }
}</code></pre>
@@ -4887,7 +4887,7 @@ TODO
</div>
</div>
<div class="paragraph">
-<p>The three <code>@javax.jdo.annotations.Column</code> annotations are required because the mapping classes that Isis provides (<a href="https://github.com/apache/isis/blob/isis-1.4.0/component/objectstore/jdo/jdo-datanucleus/src/main/java/org/apache/isis/objectstore/jdo/datanucleus/valuetypes/IsisBlobMapping.java#L59">IsisBlobMapping</a> and <a href="https://github.com/apache/isis/blob/isis-1.4.0/component/objectstore/jdo/jdo-datanucleus/src/main/java/org/apache/isis/objectstore/jdo/datanucleus/valuetypes/IsisClobMapping.java#L59">IsisClobMapping</a>) map to 3 columns. (It is not an error to omit these <code>@Column</code> annotations, but without them the names of the table columns are simply suffixed <code>_0</code>, <code>_1</code>, <code>_2</code> etc.</p>
+<p>The three <code>@javax.jdo.annotations.Column</code> annotations are required because the mapping classes that Apache Isis provides (<a href="https://github.com/apache/isis/blob/isis-1.4.0/component/objectstore/jdo/jdo-datanucleus/src/main/java/org/apache/isis/objectstore/jdo/datanucleus/valuetypes/IsisBlobMapping.java#L59">IsisBlobMapping</a> and <a href="https://github.com/apache/isis/blob/isis-1.4.0/component/objectstore/jdo/jdo-datanucleus/src/main/java/org/apache/isis/objectstore/jdo/datanucleus/valuetypes/IsisClobMapping.java#L59">IsisClobMapping</a>) map to 3 columns. (It is not an error to omit these <code>@Column</code> annotations, but without them the names of the table columns are simply suffixed <code>_0</code>, <code>_1</code>, <code>_2</code> etc.</p>
</div>
<div class="paragraph">
<p>If the <code>Blob</code> is mandatory, then use:</p>
@@ -4984,13 +4984,13 @@ WIP
</td>
<td class="content">
<div class="paragraph">
-<p>While Isis support collections of references, the framework (currently) does not support collections of values. That is, it isn’t possible to define a collection of type <code>Set<String></code>.</p>
+<p>While Apache Isis support collections of references, the framework (currently) does not support collections of values. That is, it isn’t possible to define a collection of type <code>Set<String></code>.</p>
</div>
<div class="paragraph">
-<p>Or, actually, you can, because that is a valid mapping supported by JDO/DataNucleus . However, Isis has no default visualization.</p>
+<p>Or, actually, you can, because that is a valid mapping supported by JDO/DataNucleus . However, Apache Isis has no default visualization.</p>
</div>
<div class="paragraph">
-<p>One workaround is to mark the collection as <a href="rg.html#_rg_annotations_manpage-Progammatic"><code>@Progammatic</code></a>. This ensures that the collection is ignored by Isis.</p>
+<p>One workaround is to mark the collection as <a href="rg.html#_rg_annotations_manpage-Progammatic"><code>@Progammatic</code></a>. This ensures that the collection is ignored by Apache Isis.</p>
</div>
<div class="paragraph">
<p>Another workaround is to wrap each value in a view model, as explained in this <a href="#_ug_more-advanced_tips-n-tricks_simulating-collections-of-values">tip</a>.</p>
@@ -5022,10 +5022,10 @@ TODO
</td>
<td class="content">
<div class="paragraph">
-<p>While Isis support actions whose parameters' types are scalar (values such as <code>String</code>, <code>int</code>, or references such as <code>Customer</code>), the framework (currently) does not support parameter types that are collections or maps.</p>
+<p>While Apache Isis support actions whose parameters' types are scalar (values such as <code>String</code>, <code>int</code>, or references such as <code>Customer</code>), the framework (currently) does not support parameter types that are collections or maps.</p>
</div>
<div class="paragraph">
-<p>The workaround is to mark the collection as <code>@Programmatic</code>, as described in <a href="#_ug_how-tos_class-structure_ignoring-methods">Ignoring Methods</a>. This ensures that the collection is ignored by Isis.</p>
+<p>The workaround is to mark the collection as <code>@Programmatic</code>, as described in <a href="#_ug_how-tos_class-structure_ignoring-methods">Ignoring Methods</a>. This ensures that the collection is ignored by Apache Isis.</p>
</div>
</td>
</tr>
@@ -5174,7 +5174,7 @@ public, and has a single parameter of the correct type.</p>
<div class="sect4">
<h5 id="_constructor_injection">Constructor injection</h5>
<div class="paragraph">
-<p>Simply to note that constructor injection is <em>not</em> supported by Isis (and is unlikely to be, because the JDO specification for entities requires a no-arg constructor).</p>
+<p>Simply to note that constructor injection is <em>not</em> supported by Apache Isis (and is unlikely to be, because the JDO specification for entities requires a no-arg constructor).</p>
</div>
</div>
</div>
@@ -5196,10 +5196,10 @@ WIP
<p>In many cases the value types of properties and of action parameters align. For example, a <code>Customer</code> entity might have a <code>surname</code> property, and there might also be corresponding <code>changeSurname</code>. Ideally we want the surname property and surname action parameter to use the same value type.</p>
</div>
<div class="paragraph">
-<p>Having first-class support for this is a goal of Isis, and it is already possible (by writing some plumbing and glue code using Isis and DataNucleus APIs) to get some way towards this ideal. However, in the vast majority of cases it is much easier and more practical to simply use standard value types such as <code>java.lang.String</code>.</p>
+<p>Having first-class support for this is a goal of Apache Isis, and it is already possible (by writing some plumbing and glue code using Isis and DataNucleus APIs) to get some way towards this ideal. However, in the vast majority of cases it is much easier and more practical to simply use standard value types such as <code>java.lang.String</code>.</p>
</div>
<div class="paragraph">
-<p>However, the JDO/DataNucleus annotations for specifying semantics such as optionality or maximum length are restricted to only apply to fields and to methods; they cannot be applied to action parameters. It is therefore necessary to use Isis' equivalent annotations for action parameters.</p>
+<p>However, the JDO/DataNucleus annotations for specifying semantics such as optionality or maximum length are restricted to only apply to fields and to methods; they cannot be applied to action parameters. It is therefore necessary to use Apache Isis' equivalent annotations for action parameters.</p>
</div>
<div class="paragraph">
<p>The table below summarises the equivalence of some of the most common cases.</p>
@@ -5257,7 +5257,7 @@ WIP
</table>
</div>
<div class="paragraph">
-<p>Sometimes you want to define a <code>public</code> method on a domain object that is not intended to be rendered in Isis' UI.</p>
+<p>Sometimes you want to define a <code>public</code> method on a domain object that is not intended to be rendered in Apache Isis' UI.</p>
</div>
<div class="paragraph">
<p>To exclude such methods, use the <a href="rg.html#_rg_annotations_manpage-Programmatic"><code>@Programmatic</code></a> annotation.</p>
@@ -5267,7 +5267,7 @@ WIP
<div class="sect2">
<h3 id="_ug_how-tos_ui-hints">4.2. UI Hints</h3>
<div class="paragraph">
-<p>The Isis programming model includes several mechanisms for a domain object to provide UI hints. These range from their title (so an end-user can distinguish one object from another) through to hints that can impact their CSS styling.</p>
+<p>The Apache Isis programming model includes several mechanisms for a domain object to provide UI hints. These range from their title (so an end-user can distinguish one object from another) through to hints that can impact their CSS styling.</p>
</div>
<div class="sect3">
<h4 id="_ug_how-tos_ui-hints_object-titles-and-icons">4.2.1. Object Titles and Icons</h4>
@@ -5701,7 +5701,7 @@ WIP - <a href="rg.html#_rg_annotations_manpage-ActionLayout_cssClass"><code>@Act
<div class="sect2">
<h3 id="_ug_how-tos_domain-services">4.3. Domain Services</h3>
<div class="paragraph">
-<p>It’s worth extending the <<_hexagonal_architecture, Hexagonal Architecture> to show where domain services — and in particular the domain services provided by <a href="http://www.isisaddons.org">Isis Addons</a> (non-ASF) — fit in:</p>
+<p>It’s worth extending the <a href="#_ug_core-concepts_philosophy_hexagonal-architecture">Hexagonal Architecture</a> to show where domain services — and in particular the domain services provided by <a href="http://www.isisaddons.org">Isis Addons</a> (non-ASF) — fit in:</p>
</div>
<div class="imageblock">
<div class="content">
@@ -5710,7 +5710,7 @@ WIP - <a href="rg.html#_rg_annotations_manpage-ActionLayout_cssClass"><code>@Act
<div class="title">Figure 2. The hexagonal architecture with Isis addons</div>
</div>
<div class="paragraph">
-<p>Here, we can see that the addons provide services both to the Isis framework (for example security, command and auditing) and also - by way of dependency injection - to the domain objects (eg tags, excel, settings). Of course, you can also write your own domain services as well, for example to interface with some external CMS system, say.</p>
+<p>Here, we can see that the addons provide services both to the Apache Isis framework (for example security, command and auditing) and also - by way of dependency injection - to the domain objects (eg tags, excel, settings). Of course, you can also write your own domain services as well, for example to interface with some external CMS system, say.</p>
</div>
<div class="paragraph">
<p>The Apache Isis framework also provides numerous in-built domain services. These are catalogued in the reference guide, see <a href="rg.html#_rg_services-api">here</a> and <a href="rg.html#_rg_services-spi">here</a>.</p>
@@ -5880,7 +5880,7 @@ WIP - update to new annotations, including @DomainService(nature=…​)
<p>Services can optionally declare lifecycle callbacks to initialize them (when the app is deployed) and to shut them down (when the app is undeployed).</p>
</div>
<div class="paragraph">
-<p>An Isis session <em>is</em> available when initialization occurs (so services can interact with the object store, for example).</p>
+<p>An Apache Isis session <em>is</em> available when initialization occurs (so services can interact with the object store, for example).</p>
</div>
<div class="paragraph">
<p>The framework will call any <code>public</code> method annotated with <a href="rg.html#_rg_annotations_manpage-PostConstruct"><code>@PostConstruct</code></a> with either no arguments of an argument of type <code>Map<String,String></code></p>
@@ -6060,10 +6060,10 @@ TODO
</td>
<td class="content">
<div class="paragraph">
-<p>If you don’t do this then you may (as of Isis 1.4.1) hit an NullPointerException. This may be a bug in DataNucleus, we are not completely sure, but the above idiom seems to fix the issue.</p>
+<p>If you don’t do this then you may (as of Apache Isis 1.4.1) hit an NullPointerException. This may be a bug in DataNucleus, we are not completely sure, but the above idiom seems to fix the issue.</p>
</div>
<div class="paragraph">
-<p>For more information, see <a href="http://isis.markmail.org/thread/ipu2lzqqikqdglox">this thread</a> on the Isis users mailing list, including this <a href="http://markmail.org/message/hblptpw675mlw723">message</a> with the above recommendation.</p>
+<p>For more information, see <a href="http://isis.markmail.org/thread/ipu2lzqqikqdglox">this thread</a> on the Apache Isis users mailing list, including this <a href="http://markmail.org/message/hblptpw675mlw723">message</a> with the above recommendation.</p>
</div>
</td>
</tr>
@@ -6644,7 +6644,7 @@ TODO - <a href="rg.html#_rg_annotations_manpage-DomainObject_bounded"><code>@Dom
reason about all the classes in that package/namespace as a single unit, or module.</p>
</div>
<div class="paragraph">
-<p>This section describes how to use Isis' features to ensure that your domain application remains decoupled. The techniques described here are also the ones that have been adopted by the various <a href="http://github.com/isisaddons">Isis Addons</a> modules (not ASF) for security, commands, auditing etc.</p>
+<p>This section describes how to use Apache Isis' features to ensure that your domain application remains decoupled. The techniques described here are also the ones that have been adopted by the various <a href="http://github.com/isisaddons">Isis Addons</a> modules (not ASF) for security, commands, auditing etc.</p>
</div>
<div class="paragraph">
<p>The following sections describe how to re-assemble an application, in particular where some modules are in-house but others are potentially third-party (eg the Isis Addons modules).</p>
@@ -6657,7 +6657,7 @@ reason about all the classes in that package/namespace as a single unit, or modu
</td>
<td class="content">
<div class="paragraph">
-<p>There is some overlap with OSGi and Java 9’s Jigsaw concepts of "module"; in the future we expect to refactor Isis to leverage these module systems.</p>
+<p>There is some overlap with OSGi and Java 9’s Jigsaw concepts of "module"; in the future we expect to refactor Apache Isis to leverage these module systems.</p>
</div>
</td>
</tr>
@@ -6736,7 +6736,7 @@ on the initialization of each class into the JDO metamodel.</p>
</td>
<td class="content">
<div class="paragraph">
-<p>Actually, the above statement isn’t quite true. In DN 3.2.x (as used by Isis up to v1.8.0) there was no support for schemas. As of Isis 1.9.0-SNAPSHOT and DN 4.0 there is now support. But we implemented this feature initially against DN 3.2.x, and it still works, so for now we’ve decided to leave it in.</p>
+<p>Actually, the above statement isn’t quite true. In DN 3.2.x (as used by Apache Isis up to v1.8.0) there was no support for schemas. As of Apache Isis 1.9.0-SNAPSHOT and DN 4.0 there is now support. But we implemented this feature initially against DN 3.2.x, and it still works, so for now we’ve decided to leave it in.</p>
</div>
</td>
</tr>
@@ -6835,7 +6835,7 @@ need to tweak it to support other RDBMS'. Any implementation must implement <co
</td>
<td class="content">
<div class="paragraph">
-<p>If you do extend Isis' <code>CreateSchemaObjectFromClassMetadata</code> class for some other database, please <a href="https://issues.apache.org/jira/browse/ISIS">contribute back</a> your improvements.</p>
+<p>If you do extend Apache Isis' <code>CreateSchemaObjectFromClassMetadata</code> class for some other database, please <a href="https://issues.apache.org/jira/browse/ISIS">contribute back</a> your improvements.</p>
</div>
</td>
</tr>
@@ -7226,15 +7226,15 @@ TODO - as used in <a href="http://github.com/estatio/estatio">Estatio</a>
<div class="sect2">
<h3 id="_ug_more-advanced_transactions-and-errors">5.6. Transactions and Errors</h3>
<div class="paragraph">
-<p>In Isis, every action invocation (in fact, every interaction) is automatically wrapped in a transaction, and any repository query automatically does a flush.</p>
+<p>In Apache Isis, every action invocation (in fact, every interaction) is automatically wrapped in a transaction, and any repository query automatically does a flush.</p>
</div>
<div class="paragraph">
-<p>What that means is that there’s no need to explicitly start or commit transactions in Isis; this will be done for you. Indeed, if you do try to manage transactions (eg by reaching into the JDO <code>PersistenceManager</code> exposed by the <a href="rg.html#_rg_services-api_manpage-IsisJdoSupport">IsisJdoSupport</a> domain service, then you are likely to confuse Isis and get a stack trace for your trouble.</p>
+<p>What that means is that there’s no need to explicitly start or commit transactions in Apache Isis; this will be done for you. Indeed, if you do try to manage transactions (eg by reaching into the JDO <code>PersistenceManager</code> exposed by the <a href="rg.html#_rg_services-api_manpage-IsisJdoSupport">IsisJdoSupport</a> domain service, then you are likely to confuse Isis and get a stack trace for your trouble.</p>
</div>
<div class="sect3">
<h4 id="_aborting_transactions">5.6.1. Aborting Transactions</h4>
<div class="paragraph">
-<p>If you want to abort Isis' transaction, this can be done by throwing <code>RecoverableException</code> (or any subclass, eg <code>ApplicationException</code>). The transaction will be aborted, and the exception message will be displayed to the user.</p>
+<p>If you want to abort Apache Isis' transaction, this can be done by throwing <code>RecoverableException</code> (or any subclass, eg <code>ApplicationException</code>). The transaction will be aborted, and the exception message will be displayed to the user.</p>
</div>
<div class="paragraph">
<p>If you throw any other exception (ie not a subclass of <code>RecoverableException</code>), then the users will see an error page (if Wicket viewer) or a 500 (if Restful Objects viewer).</p>
@@ -7327,7 +7327,7 @@ TODO - <a href="rg.html#_rg_services-spi_manpage-ExceptionRecognizer"><code>Exce
</td>
<td class="content">
<div class="paragraph">
-<p>Although Isis' implementation is modelled after GNU’s API, it does <em>not</em> 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).</p>
+<p>Although Apache Isis' implementation is modelled after GNU’s API, it does <em>not</em> 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).</p>
</div>
</td>
</tr>
@@ -7353,13 +7353,13 @@ TODO - <a href="rg.html#_rg_services-spi_manpage-ExceptionRecognizer"><code>Exce
</ul>
</div>
<div class="paragraph">
-<p>In Isis' implementation, if the translation is missing from the <code>.po</code> file then the original message text from the <code>.pot</code> file will be returned. In fact, it isn’t even necessary for there to be any <code>.po</code> files; <code>.po</code> translations can be added piecemeal as the need arises.</p>
+<p>In Apache Isis' implementation, if the translation is missing from the <code>.po</code> file then the original message text from the <code>.pot</code> file will be returned. In fact, it isn’t even necessary for there to be any <code>.po</code> files; <code>.po</code> translations can be added piecemeal as the need arises.</p>
</div>
</div>
<div class="sect3">
<h4 id="__code_translationservice_code">5.7.2. <code>TranslationService</code></h4>
<div class="paragraph">
-<p>The cornerstone of Isis' support for i18n is the <code>TranslationService</code> service. This is defined in the applib with the following API:</p>
+<p>The cornerstone of Apache Isis' support for i18n is the <code>TranslationService</code> service. This is defined in the applib with the following API:</p>
</div>
<div class="listingblock">
<div class="content">
@@ -7434,7 +7434,7 @@ TODO - <a href="rg.html#_rg_services-spi_manpage-ExceptionRecognizer"><code>Exce
<div class="sect3">
<h4 id="_imperative_messages">5.7.3. Imperative messages</h4>
<div class="paragraph">
-<p>The <code>TranslationService</code> is used internally by Isis when building up the metamodel; the name and description of every class, property, collection, action and action parameter is automatically translated. Thus the simple act of bootstrapping Isis will cause most of the messages requiring translation (that is: those for the Isis metamodel) to be captured by the <code>TranslationService</code>.</p>
+<p>The <code>TranslationService</code> is used internally by Apache Isis when building up the metamodel; the name and description of every class, property, collection, action and action parameter is automatically translated. Thus the simple act of bootstrapping Apache Isis will cause most of the messages requiring translation (that is: those for the Apache Isis metamodel) to be captured by the <code>TranslationService</code>.</p>
</div>
<div class="paragraph">
<p>However, for an application to be fully internationalized, any validation messages (from either <code>disableXxx()</code> or <code>validateXxx()</code> supporting methods) and also possibly an object’s title (from the <code>title()</code> method) will also require translation. Moreover, these messages must be captured in the <code>.pot</code> file such that they can be translated.</p>
@@ -7442,7 +7442,7 @@ TODO - <a href="rg.html#_rg_services-spi_manpage-ExceptionRecognizer"><code>Exce
<div class="sect4">
<h5 id="__code_translatablestring_code"><code>TranslatableString</code></h5>
<div class="paragraph">
-<p>The first part of the puzzle is tackled by an extension to Isis' programming model. Whereas previously the <code>disableXxx()</code> / <code>validateXxx()</code> / <code>title()</code> methods could only return a <code>java.lang.String</code>, they may now optionally return a <code>TranslatableString</code> (defined in Isis applib) instead.</p>
+<p>The first part of the puzzle is tackled by an extension to Apache Isis' programming model. Whereas previously the <code>disableXxx()</code> / <code>validateXxx()</code> / <code>title()</code> methods could only return a <code>java.lang.String</code>, they may now optionally return a <code>TranslatableString</code> (defined in Isis applib) instead.</p>
</div>
<div class="paragraph">
<p>Here’s a (silly) example from the <a href="#_ug_getting-started_simpleapp-archetype">SimpleApp archetype</a>:</p>
@@ -7624,7 +7624,7 @@ FixtureScripts fixtureScripts;
<p>Running this test will result in the framework calling the <code>validateUpdateName(…​)</code> method, and thus to record that a translation is required in the <code>.pot</code> file.</p>
</div>
<div class="paragraph">
-<p>When the integration tests are complete (that is, when Isis is shutdown), the <code>TranslationServicePo</code> will write out all captured translations to its log (more on this below). This will include all the translations captured from the Isis metamodel, along with all translations as exercised by the integration tests.</p>
+<p>When the integration tests are complete (that is, when Apache Isis is shutdown), the <code>TranslationServicePo</code> will write out all captured translations to its log (more on this below). This will include all the translations captured from the Apache Isis metamodel, along with all translations as exercised by the integration tests.</p>
</div>
<div class="paragraph">
<p>To ensure your app is fully internationalized app, you must therefore:</p>
@@ -7647,10 +7647,10 @@ FixtureScripts fixtureScripts;
</td>
<td class="content">
<div class="paragraph">
-<p>We make no apologies for this requirement: one of the reasons that we decided to implement Isis' i18n support in this way is because it encourages/requires the app to be properly tested.</p>
+<p>We make no apologies for this requirement: one of the reasons that we decided to implement Apache Isis' i18n support in this way is because it encourages/requires the app to be properly tested.</p>
</div>
<div class="paragraph">
-<p>Behind the scenes Isis uses a JUnit rule (<code>ExceptionRecognizerTranslate</code>) to intercept any exceptions that are thrown. These are simply passed through to the registered <a href="rg.html#_rg_services-spi_manpage-ExceptionRecognizer"><code>ExceptionRecognizer</code></a>s so that any messages are recorded as requiring translation.</p>
+<p>Behind the scenes Apache Isis uses a JUnit rule (<code>ExceptionRecognizerTranslate</code>) to intercept any exceptions that are thrown. These are simply passed through to the registered <a href="rg.html#_rg_services-spi_manpage-ExceptionRecognizer"><code>ExceptionRecognizer</code></a>s so that any messages are recorded as requiring translation.</p>
</div>
</td>
</tr>
@@ -7725,7 +7725,7 @@ log4j.additivity.org.apache.isis.core.runtime.services.i18n.po.PotWriter=false</
<div class="sect4">
<h5 id="_externalized_translation_files">Externalized translation files</h5>
<div class="paragraph">
-<p>Normally Isis configuration files are read from the <code>WEB-INF</code> file. However, Isis can be configured to read config files from an <a href="#_ug_deployment_externalized-configuration">external directory</a>; this is also supported for translations.</p>
+<p>Normally Apache Isis configuration files are read from the <code>WEB-INF</code> file. However, Apache Isis can be configured to read config files from an <a href="#_ug_deployment_externalized-configuration">external directory</a>; this is also supported for translations.</p>
</div>
<div class="paragraph">
<p>Thus, if in <code>web.xml</code> the external configuration directory has been set:</p>
@@ -7972,7 +7972,7 @@ TODO
<i class="fa icon-important" title="Important"></i>
</td>
<td class="content">
-WIP - easiest to simply store using DataNucleus' support for collections, marked as <a href="rg.html#_rg_annotations_manpage-Programmatic"><code>@Programmatic</code></a> so that it is ignored by Isis. Alternatively can store as json/xml in a varchar(4000) or clob and manually unpack.
+WIP - easiest to simply store using DataNucleus' support for collections, marked as <a href="rg.html#_rg_annotations_manpage-Programmatic"><code>@Programmatic</code></a> so that it is ignored by Apache Isis. Alternatively can store as json/xml in a varchar(4000) or clob and manually unpack.
</td>
</tr>
</table>
@@ -8039,7 +8039,7 @@ WIP - easiest to simply store using DataNucleus' support for collections, marke
<div class="sect3">
<h4 id="_ug_more-advanced_tips-n-tricks_per-user-themes">5.10.4. Per-user Themes</h4>
<div class="paragraph">
-<p>From the Isis mailing list is:</p>
+<p>From the Apache Isis mailing list is:</p>
</div>
<div class="ulist">
<ul>
@@ -8130,7 +8130,7 @@ WIP - easiest to simply store using DataNucleus' support for collections, marke
<div class="sect3">
<h4 id="_ug_more-advanced_tips-n-tricks_enhance-only">5.10.5. Enhance only (IntelliJ)</h4>
<div class="paragraph">
-<p>From the Isis mailing list is:</p>
+<p>From the Apache Isis mailing list is:</p>
</div>
<div class="ulist">
<ul>
@@ -8773,7 +8773,7 @@ value type (character large object), each of which also includes metadata about
</ul>
</div>
<div class="paragraph">
-<p>The Isis core framework provides a default implementation of both the email notification service and the email service. If your application uses the <a href="https://github.com/isisaddons/isis-module-security">Isis addons security module</a> (not ASF) then an implementation is provided by that module; just add to the classpath. Otherwise you will need to provide your own implementation.</p>
+<p>The Apache Isis core framework provides a default implementation of both the email notification service and the email service. If your application uses the <a href="https://github.com/isisaddons/isis-module-security">Isis addons security module</a> (not ASF) then an implementation is provided by that module; just add to the classpath. Otherwise you will need to provide your own implementation.</p>
</div>
<div class="admonitionblock note">
<table>
@@ -8867,7 +8867,7 @@ value type (character large object), each of which also includes metadata about
<div class="sect2">
<h3 id="_ug_wicket-viewer_configuration-properties">6.2. Configuration Properties</h3>
<div class="paragraph">
-<p>Wicket configuration properties alter the way in which Isis' Wicket viewer renders domain objects. They are typically stored in <code>WEB-INF/viewer_wicket.properties</code>.</p>
+<p>Wicket configuration properties alter the way in which Apache Isis' Wicket viewer renders domain objects. They are typically stored in <code>WEB-INF/viewer_wicket.properties</code>.</p>
</div>
<div class="admonitionblock note">
<table>
@@ -8877,7 +8877,7 @@ value type (character large object), each of which also includes metadata about
</td>
<td class="content">
<div class="paragraph">
-<p>To tell Isis that the Wicket viewer is in use (and should therefore search for the <code>viewer_wicket.properties</code> file), add the following to <code>WEB-INF/web.xml</code>:</p>
+<p>To tell Apache Isis that the Wicket viewer is in use (and should therefore search for the <code>viewer_wicket.properties</code> file), add the following to <code>WEB-INF/web.xml</code>:</p>
</div>
<div class="listingblock">
<div class="content">
@@ -8932,7 +8932,7 @@ value type (character large object), each of which also includes metadata about
<code>disableModalDialogs</code></p>
</div></div></td>
<td class="tableblock halign-left valign-top"><p class="tableblock"><code>true</code>,<code>false</code> (<code><em>false</em></code>)</p></td>
-<td class="tableblock halign-left valign-top"><p class="tableblock">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.
+<td class="tableblock halign-left valign-top"><p class="tableblock">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.
</p><p class="tableblock">Note that action pages are still used for bookmarked actions.</p></td>
</tr>
<tr>
@@ -9178,7 +9178,7 @@ isis.viewer.wicket.maxTitleLengthInParentedTables=8</code></pre>
<div class="sect3">
<h4 id="_ug_wicket-viewer_configuration-properties_stripped-wicket-tags">6.2.5. Stripped Wicket tags</h4>
<div class="paragraph">
-<p>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:</p>
+<p>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:</p>
</div>
<div class="listingblock">
<div class="content">
@@ -9193,7 +9193,7 @@ isis.viewer.wicket.maxTitleLengthInParentedTables=8</code></pre>
</td>
<td class="content">
<div class="paragraph">
-<p>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.</p>
+<p>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.</p>
</div>
<div class="paragraph">
<p>We changed the behaviour in 1.8.0 because we found that Internet Explorer can be sensitive to the presence of Wicket tags.</p>
@@ -9343,7 +9343,7 @@ property:</p>
<p>To pick up a change, edit the <code>.layout.json</code> file in the IDE and rebuild. Then click on the title of the object <em>*twice*</em>.</p>
</div>
<div class="paragraph">
-<p>The first click will cause Isis to pick up the new metadata, but too late in the process to adjust the ren
<TRUNCATED>