http://git-wip-us.apache.org/repos/asf/isis-site/blob/8b42f65e/content/migration-notes/migration-notes.html
----------------------------------------------------------------------
diff --git a/content/migration-notes/migration-notes.html 
b/content/migration-notes/migration-notes.html
index a76c41a..d1965cc 100644
--- a/content/migration-notes/migration-notes.html
+++ b/content/migration-notes/migration-notes.html
@@ -294,35 +294,32 @@ table.CodeRay td.code>pre{padding:0}
          </table> 
         </div> 
         <div class="sect2"> 
-         <h3 
id="_overriding_framework_services_a_href_https_issues_apache_org_jira_browse_isis_1611_isis_1611_a">Overriding
 framework services (<a 
href="https://issues.apache.org/jira/browse/ISIS-1611";>ISIS-1611</a>)</h3> 
+         <h3 
id="__code_isis_mavendeps_code_aggregator_poms"><code>isis-mavendeps</code> 
Aggregator POMs</h3> 
          <div class="paragraph"> 
-          <p>Domain services fall into three categories:</p> 
+          <p>To remove boilerplate in your application’s 
<code>pom.xml</code>, three new maven "aggregator projects have been 
defined:</p> 
          </div> 
          <div class="ulist"> 
           <ul> 
-           <li> <p>application services: written by the application developer 
and used only within the application</p> </li> 
-           <li> <p>SPI services: written by the application developer but 
called by the framework</p> </li> 
-           <li> <p>framework services: defined within the applib with a 
default implementation provided by the framework itself</p> </li> 
+           <li> 
<p><code>org.apache.isis.mavendeps:isis-mavendeps-testing</code><br></p> 
+            <div class="paragraph"> 
+             <p>aggregates dependencies for unit, integration and BDD 
tests</p> 
+            </div> </li> 
+           <li> 
<p><code>org.apache.isis.mavendeps:isis-mavendeps-webapp</code><br></p> 
+            <div class="paragraph"> 
+             <p>aggregates dependencies for running as a webapp</p> 
+            </div> </li> 
+           <li> 
<p><code>org.apache.isis.mavendeps:isis-mavendeps-intellij</code><br></p> 
+            <div class="paragraph"> 
+             <p>brings in a dependency on <code>isis-core-webserver</code> (to 
run the application from the command line using 
<code>org.apache.isis.WebServer</code>). This is defined in a profile which is 
actived only when running under the Intellij IDE.</p> 
+            </div> </li> 
           </ul> 
          </div> 
          <div class="paragraph"> 
-          <p>As described <a 
href="../guides/ugbtb/ugbtb.html#_ugbtb_hints-and-tips_replacing-default-service-implementations">here</a>,
 it is possible to override framework services so that the framework uses the 
replacement implementation. Previously this required explicitly setting either 
<a 
href="../guides/rgant/rgant.html#_rgant_DomainService_menuOrder"><code>@DomainService#menuOrder()</code></a>
 or <a 
href="../guides/rgant/rgant.html#_rgant_DomainServiceLayout_menuOrder"><code>@DomainServiceLayout#menuOrder()</code></a>.</p>
 
-         </div> 
-         <div class="paragraph"> 
-          <p>In 1.15.0, the default value for <code>menuOrder</code> has been 
set to a value lower than that of the framework-provided implementations, and 
so will a custom implementation will always take precedence over the framework 
implementations without having to remember to also set 
<code>menuOrder</code>.</p> 
-         </div> 
-        </div> 
-        <div class="sect2"> 
-         <h3 
id="_fix_to_config_variable_a_href_https_issues_apache_org_jira_browse_isis_1595_isis_1595_a">Fix
 to config variable (<a 
href="https://issues.apache.org/jira/browse/ISIS-1595";>ISIS-1595</a>)</h3> 
-         <div class="paragraph"> 
-          <p>The configuration property <a 
href="../guides/rgcfg/rgcfg.html#__rgcfg_configuring-core_metamodel-validation">[../guides/rgcfg/rgcfg#__rgcfg_configuring-core_metamodel-validation]</a>
 <code>isis.reflector.validator.jdoqlVariablesClause</code> was incorrectly 
named <code>variablesClause</code>. This has now been corrected.</p> 
-         </div> 
-         <div class="paragraph"> 
-          <p>Any applications that used this configuration property should be 
updated.</p> 
+          <p>The <a 
href="../ugfun/ugfun.html#_ugfun_getting-started_helloworld-archetype">HelloWorld</a>
 and <a 
href="../ugfun/ugfun.html#_ugfun_getting-started_simpleapp-archetype">SimpleApp</a>
 archetypes both make use of these new aggregators.</p> 
          </div> 
         </div> 
         <div class="sect2"> 
-         <h3 id="_rename_of_isis_viewer_wicket_artifacts">Rename of 
isis-viewer-wicket artifacts</h3> 
+         <h3 
id="_rename_of_isis_viewer_wicket_artifacts_a_href_https_issues_apache_org_jira_browse_isis_1528_isis_1528_a">Rename
 of isis-viewer-wicket artifacts (<a 
href="https://issues.apache.org/jira/browse/ISIS-1528";>ISIS-1528</a>)</h3> 
          <div class="paragraph"> 
           <p>The <code>&lt;groupId&gt;</code> and 
<code>&lt;artifactId&gt;</code> of the <a 
href="../guides/ugvw/ugvw.html">Wicket viewer</a> have been made consistent 
with other artifacts:</p> 
          </div> 
@@ -351,6 +348,114 @@ table.CodeRay td.code>pre{padding:0}
           </div> 
          </div> 
         </div> 
+        <div class="sect2"> 
+         <h3 
id="_overriding_framework_services_a_href_https_issues_apache_org_jira_browse_isis_1611_isis_1611_a">Overriding
 framework services (<a 
href="https://issues.apache.org/jira/browse/ISIS-1611";>ISIS-1611</a>)</h3> 
+         <div class="paragraph"> 
+          <p>Domain services fall into three categories:</p> 
+         </div> 
+         <div class="ulist"> 
+          <ul> 
+           <li> <p>application services: written by the application developer 
and used only within the application</p> </li> 
+           <li> <p>SPI services: written by the application developer but 
called by the framework</p> </li> 
+           <li> <p>framework services: defined within the applib with a 
default implementation provided by the framework itself.</p> </li> 
+          </ul> 
+         </div> 
+         <div class="paragraph"> 
+          <p>As described <a 
href="../guides/ugbtb/ugbtb.html#_ugbtb_hints-and-tips_replacing-default-service-implementations">here</a>,
 it is possible to override framework services so that the framework uses the 
replacement implementation. Previously this required explicitly setting either 
<a 
href="../guides/rgant/rgant.html#_rgant_DomainService_menuOrder"><code>@DomainService#menuOrder()</code></a>
 or <a 
href="../guides/rgant/rgant.html#_rgant_DomainServiceLayout_menuOrder"><code>@DomainServiceLayout#menuOrder()</code></a>.</p>
 
+         </div> 
+         <div class="paragraph"> 
+          <p>In 1.15.0, the default value for <code>menuOrder</code> has been 
set to a value lower than that of the framework-provided implementations, and 
so will a custom implementation will always take precedence over the framework 
implementations without having to remember to also set 
<code>menuOrder</code>.</p> 
+         </div> 
+         <div class="paragraph"> 
+          <p>Of course, your application can still override 
<code>menuOrder</code> if it wishes. A small change (made in (<a 
href="https://issues.apache.org/jira/browse/ISIS-1688";>ISIS-1688</a>) is that 
if both are set, then the minimum value is used.</p> 
+         </div> 
+        </div> 
+        <div class="sect2"> 
+         <h3 
id="_metamodel_validators_a_href_https_issues_apache_org_jira_browse_isis_1504_isis_1504_a_a_href_https_issues_apache_org_jira_browse_isis_1622_isis_1622_a_a_href_https_issues_apache_org_jira_browse_isis_1669_isis_1669_a">Metamodel
 validators (<a 
href="https://issues.apache.org/jira/browse/ISIS-1504";>ISIS-1504</a>, <a 
href="https://issues.apache.org/jira/browse/ISIS-1622";>ISIS-1622</a>, <a 
href="https://issues.apache.org/jira/browse/ISIS-1669";>ISIS-1669</a>)</h3> 
+         <div class="paragraph"> 
+          <p>The metamodel validator has been extended with several new checks 
relating to <a 
href="../ugfun.html#_ugfun_programming-model_view-models_jaxb">JAXB view 
models</a>:</p> 
+         </div> 
+         <div class="ulist"> 
+          <ul> 
+           <li> <p>that the view model can be instantiated:</p> 
+            <div class="ulist"> 
+             <ul> 
+              <li> <p>has a public, no-arg constructor</p> </li> 
+              <li> <p>is not abstract</p> </li> 
+              <li> <p>is not a member inner class (nested static class is 
ok)</p> </li> 
+             </ul> 
+            </div> </li> 
+           <li> <p>that JODA datetimes are annotated with the <a 
href="../ugfun/ugfun.html#_ugfun_programming-model_view-models_jaxb_joda-datatypes">appropriate
 implementation</a> of a JAXB <code>XmlAdapter</code></p> </li> 
+           <li> <p>that for references to persistent entities, that those 
persistent entities are annotated to use <a 
href="../ugfun/ugfun.html#_ugfun_programming-model_view-models_jaxb_referencing-domain-entities"><code>PersistentEntityAdapter</code></a>
 as their JAXB adapter.</p> </li> 
+          </ul> 
+         </div> 
+         <div class="paragraph"> 
+          <p>... in other words, that the view model can be instantiated.</p> 
+         </div> 
+         <div class="paragraph"> 
+          <p>These checks are enabled by default but can be disabled with a <a 
href="../rgcfg.html#__rgcfg_configuring-core_metamodel-validation">configuration
 property</a> if required.</p> 
+         </div> 
+        </div> 
+        <div class="sect2"> 
+         <h3 
id="_logging_workaround_a_href_https_issues_apache_org_jira_browse_isis_1613_isis_1613_a">Logging
 workaround (<a 
href="https://issues.apache.org/jira/browse/ISIS-1613";>ISIS-1613</a>)</h3> 
+         <div class="paragraph"> 
+          <p><code>ISIS-1613</code> improves the UI so that the framework does 
not repaint the entire page after a property edit or after invoking an action 
that returns the same object (<code>this</code>). The overall effect is a 
smoother user experience.</p> 
+         </div> 
+         <div class="paragraph"> 
+          <p>However, it also results in "WARN" messages being emitted by 
Apache Wicket. These are not harmful, but may pollute the log.</p> 
+         </div> 
+         <div class="paragraph"> 
+          <p>To remove them, add the following to 
<code>logging.properties</code>:</p> 
+         </div> 
+         <div class="listingblock"> 
+          <div class="content"> 
+           <pre class="CodeRay highlight"><code 
data-lang="properties">log4j.logger.org.apache.wicket.page.XmlPartialPageUpdate=ERROR,console
+log4j.additivity.org.apache.wicket.page.XmlPartialPageUpdate=false</code></pre>
 
+          </div> 
+         </div> 
+        </div> 
+        <div class="sect2"> 
+         <h3 
id="_less_boilerplate_when_bootstrapping_a_href_https_issues_apache_org_jira_browse_isis_1686_isis_1686_a">Less
 boilerplate when bootstrapping (<a 
href="https://issues.apache.org/jira/browse/ISIS-1686";>ISIS-1686</a></h3> 
+         <div class="paragraph"> 
+          <p>Bootstrapping the application can now be accomplished with less 
boilerplate, both for the regular webapp and in integration tests.</p> 
+         </div> 
+         <div class="paragraph"> 
+          <p>For more information, see the <a 
href="../ugtst/ugtst.html#_ugtst_integ-test-support_bootstrapping">testing 
guide</a> and <a 
href="../rgcms/rgcms.html#__rgcms_classes_AppManifest-bootstrapping_bootstrapping_AppManifestAbstract">reference
 guide for classes/methods/schema</a>.</p> 
+         </div> 
+        </div> 
+        <div class="sect2"> 
+         <h3 
id="_fix_to_config_variable_a_href_https_issues_apache_org_jira_browse_isis_1595_isis_1595_a">Fix
 to config variable (<a 
href="https://issues.apache.org/jira/browse/ISIS-1595";>ISIS-1595</a>)</h3> 
+         <div class="paragraph"> 
+          <p>The configuration property <a 
href="../guides/rgcfg/rgcfg.html#__rgcfg_configuring-core_metamodel-validation">[../guides/rgcfg/rgcfg#__rgcfg_configuring-core_metamodel-validation]</a>
 <code>isis.reflector.validator.jdoqlVariablesClause</code> was incorrectly 
named <code>variablesClause</code>. This has now been corrected.</p> 
+         </div> 
+         <div class="paragraph"> 
+          <p>Any applications that used this configuration property should be 
updated.</p> 
+         </div> 
+        </div> 
+        <div class="sect2"> 
+         <h3 
id="__code_postconstruct_code_always_called_a_href_https_issues_apache_org_jira_browse_isis_1690_isis_1690_a"><code>@PostConstruct</code>
 always called (<a 
href="https://issues.apache.org/jira/browse/ISIS-1690";>ISIS-1690</a>)</h3> 
+         <div class="paragraph"> 
+          <p>In previous versions, if any domain service threw an exception in 
their initialization method (annotated <code>@PostConstruct</code>) then none 
of the remaining domain services would be initialized. Even though the failing 
service would cause an error to be logged during start-up, this could still 
manifest as the application starting (in a fashion) but then failing in 
unrelated areas later on.</p> 
+         </div> 
+         <div class="paragraph"> 
+          <p>As of this version, the framework now always calls ensures that 
all services are initialized, even if one or more of them throw an exception. 
The first exception encountered is then re-thrown (to preserve similar 
behaviour as possible to earlier versions).</p> 
+         </div> 
+        </div> 
+        <div class="sect2"> 
+         <h3 id="__non_asf_incode_platform">(non-ASF) Incode Platform</h3> 
+         <div class="paragraph"> 
+          <p>(<strong>work in progress</strong>) The supporting (non-ASF) <a 
href="http://isisaddons.org";>Isis Addons</a> and <a 
href="http://catalog.incode.org";>Incode Catalog</a> have also been reorganised 
into a single <a href="http://platform.incode.org";>"Incode Platform"</a>.</p> 
+         </div> 
+         <div class="paragraph"> 
+          <p>While each module can still be consumed individually, the new 
platform versions consistently (a change in any one module will result in a 
re-release of all). This should make these modules easier to consume, and 
easier to maintain/develop.</p> 
+         </div> 
+         <div class="paragraph"> 
+          <p>All the modules remain open source, still licensed under the ASF 
v2.0 license.</p> 
+         </div> 
+         <div class="paragraph"> 
+          <p>As of this release, none of the <code>groupId</code>s or 
<code>artifactId</code>s have changed. They will be rationalized/made 
consistent in a future release; most probably to coincide with v2.0.0 of the 
framework.</p> 
+         </div> 
+        </div> 
        </div> 
       </div> 
       <div class="sect1"> 

Reply via email to