svn commit: r897379 - in /websites/staging/isis/trunk: cgi-bin/ content/ content/core/unittestsupport.html

[bu...@apache.org]

Author: buildbot
Date: Tue Feb 11 08:05:31 2014
New Revision: 897379

Log:
Staging update by buildbot for isis

Modified:
    websites/staging/isis/trunk/cgi-bin/   (props changed)
    websites/staging/isis/trunk/content/   (props changed)
    websites/staging/isis/trunk/content/core/unittestsupport.html

Propchange: websites/staging/isis/trunk/cgi-bin/
------------------------------------------------------------------------------
--- cms:source-revision (original)
+++ cms:source-revision Tue Feb 11 08:05:31 2014
@@ -1 +1 @@
-1566929
+1567005

Propchange: websites/staging/isis/trunk/content/
------------------------------------------------------------------------------
--- cms:source-revision (original)
+++ cms:source-revision Tue Feb 11 08:05:31 2014
@@ -1 +1 @@
-1566929
+1567005

Modified: websites/staging/isis/trunk/content/core/unittestsupport.html
==============================================================================
--- websites/staging/isis/trunk/content/core/unittestsupport.html (original)
+++ websites/staging/isis/trunk/content/core/unittestsupport.html Tue Feb 11 08:05:31 2014
@@ -318,7 +318,7 @@
 <li>First, <code>Set</code>s align more closely to the relational model than do <code>List</code>s.  A <code>List</code> must have an additional index to specify order.</li>
 <li>Second, <code>SortedSet</code> is preferable to <code>Set</code> because then the order is well-defined and predictable (to an end user, to the programmer).</p>
 
-<p>The <a href="../applib-guide/reference/Utility.html">ObjectContracts</a> utility class substantially simplifies the task of implementing <code>Comparable</code> in your domain classes. </li>
+<p>The <a href="../reference/Utility.html">ObjectContracts</a> utility class substantially simplifies the task of implementing <code>Comparable</code> in your domain classes. </li>
 <li>Third, if the relationship is bidirectional then JDO/Objectstore will automatically maintain the relationship.  See <a href="../components/objectstores/jdo/managed-1-to-m-relationships.html">here</a> for further discussion.    </li>
 </ul>
 
@@ -366,14 +366,10 @@
 
 <h2>Bidirectional Contract Test</h2>
 
-<p>This contract test automatically checks that bidirectional 1:m or 1:1 associations are being maintained correctly (assuming that they follow the <a href="../applib-guide/how-tos/how-to-04-060-How-to-set-up-and-maintain-bidirectional-relationships.html">mutual registration pattern</a></p>
+<p>This contract test automatically checks that bidirectional 1:m or 1:1 associations are being maintained correctly (assuming that they follow the <a href="../more-advanced-topics/how-to-04-060-How-to-set-up-and-maintain-bidirectional-relationships.html">mutual registration pattern</a></p>
 
 <blockquote>
-  <p><strong>Note:</strong> </p>
-  
-  <p>If using the <a href="../components/objectstores/jdo/about.html">JDO Object Store</a>, then there is generally no need to programmatically maintain 1:m relationships (indeed it may introduce subtle errors).  For more details, see <a href="../components/objectstores/jdo/managed-1-to-m-relationships.html">here</a>.</p>
-  
-  <p>If <em>not</em> using the JDO Object Store, note that <em>Isis</em> provides <a href="../getting-started/editor-templates.html">Eclipse templates</a> to help generate the necessary boilerplate.</p>
+  <p><em>Note</em> If using the <a href="../components/objectstores/jdo/about.html">JDO Object Store</a>, then there is generally no need to programmatically maintain 1:m relationships (indeed it may introduce subtle errors).  For more details, see <a href="../components/objectstores/jdo/managed-1-to-m-relationships.html">here</a>.  Check out the <a href="../intro/resources/editor-templates.html">Eclipse templates</a> for further guidance.</p>
 </blockquote>
 
 <p>For example, suppose that <code>ParentDomainObject</code> and <code>ChildDomainObject</code> have a 1:m relationship (<code>ParentDomainObject#children</code> / <code>ChildDomainObject#parent</code>), and also <code>PeerDomainObject</code> has a 1:1 relationship with itself (<code>PeerDomainObject#next</code> / <code>PeerDomainObject#previous</code>).  </p>