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 2014/02/11 09:05:24 UTC
svn commit: r1567005 - /isis/site/trunk/content/core/unittestsupport.md
Author: danhaywood
Date: Tue Feb 11 08:05:23 2014
New Revision: 1567005
URL: http://svn.apache.org/r1567005
Log:
fixing links
Modified:
isis/site/trunk/content/core/unittestsupport.md
Modified: isis/site/trunk/content/core/unittestsupport.md
URL: http://svn.apache.org/viewvc/isis/site/trunk/content/core/unittestsupport.md?rev=1567005&r1=1567004&r2=1567005&view=diff
==============================================================================
--- isis/site/trunk/content/core/unittestsupport.md (original)
+++ isis/site/trunk/content/core/unittestsupport.md Tue Feb 11 08:05:23 2014
@@ -41,7 +41,7 @@ If using the JDO Objectstore then we str
* Second, `SortedSet` is preferable to `Set` because then the order is well-defined and predictable (to an end user, to the programmer).
- The [ObjectContracts](../applib-guide/reference/Utility.html) utility class substantially simplifies the task of implementing `Comparable` in your domain classes.
+ The [ObjectContracts](../reference/Utility.html) utility class substantially simplifies the task of implementing `Comparable` in your domain classes.
* Third, if the relationship is bidirectional then JDO/Objectstore will automatically maintain the relationship. See [here](../components/objectstores/jdo/managed-1-to-m-relationships.html) for further discussion.
@@ -87,14 +87,9 @@ For example:
##Bidirectional Contract Test
-This contract test automatically checks that bidirectional 1:m or 1:1 associations are being maintained correctly (assuming that they follow the [mutual registration pattern](../applib-guide/how-tos/how-to-04-060-How-to-set-up-and-maintain-bidirectional-relationships.html)
-
->**Note:**
->
->If using the [JDO Object Store](../components/objectstores/jdo/about.html), then there is generally no need to programmatically maintain 1:m relationships (indeed it may introduce subtle errors). For more details, see [here](../components/objectstores/jdo/managed-1-to-m-relationships.html).
->
->If *not* using the JDO Object Store, note that *Isis* provides [Eclipse templates](../getting-started/editor-templates.html) to help generate the necessary boilerplate.
+This contract test automatically checks that bidirectional 1:m or 1:1 associations are being maintained correctly (assuming that they follow the [mutual registration pattern](../more-advanced-topics/how-to-04-060-How-to-set-up-and-maintain-bidirectional-relationships.html)
+> *Note* If using the [JDO Object Store](../components/objectstores/jdo/about.html), then there is generally no need to programmatically maintain 1:m relationships (indeed it may introduce subtle errors). For more details, see [here](../components/objectstores/jdo/managed-1-to-m-relationships.html). Check out the [Eclipse templates](../intro/resources/editor-templates.html) for further guidance.
For example, suppose that `ParentDomainObject` and `ChildDomainObject` have a 1:m relationship (`ParentDomainObject#children` / `ChildDomainObject#parent`), and also `PeerDomainObject` has a 1:1 relationship with itself (`PeerDomainObject#next` / `PeerDomainObject#previous`).