You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@isis.apache.org by bu...@apache.org on 2012/12/03 15:17:17 UTC
svn commit: r840553 - in /websites/staging/isis/trunk: cgi-bin/ content/
content/components/objectstores/jdo/hints-and-tips.html
Author: buildbot
Date: Mon Dec 3 14:17:16 2012
New Revision: 840553
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/components/objectstores/jdo/hints-and-tips.html
Propchange: websites/staging/isis/trunk/cgi-bin/
------------------------------------------------------------------------------
--- cms:source-revision (original)
+++ cms:source-revision Mon Dec 3 14:17:16 2012
@@ -1 +1 @@
-1416532
+1416533
Propchange: websites/staging/isis/trunk/content/
------------------------------------------------------------------------------
--- cms:source-revision (original)
+++ cms:source-revision Mon Dec 3 14:17:16 2012
@@ -1 +1 @@
-1416532
+1416533
Modified: websites/staging/isis/trunk/content/components/objectstores/jdo/hints-and-tips.html
==============================================================================
--- websites/staging/isis/trunk/content/components/objectstores/jdo/hints-and-tips.html (original)
+++ websites/staging/isis/trunk/content/components/objectstores/jdo/hints-and-tips.html Mon Dec 3 14:17:16 2012
@@ -184,10 +184,6 @@
</h1>
</div>
-<p><div class="stub">
-This page is a work-in-progress
-</div></p>
-
<p>By leveraging the JDO/Datanucleus ORM, Isis' JDO objectstore is very powerful. However, with such power comes a little bit of complexity to the development environment: all domain objects must be enhanced through the <a href="http://db.apache.org/jdo/enhancement.html">JDO enhancer</a>. So the enhancer must, in one way or another, be integrated into your development environment.</p>
<p>If working from the Maven command line, JDO enhancement is done using the <code>maven-datanucleus-plugin</code>.</p>
@@ -204,22 +200,22 @@ This page is a work-in-progress
<p>In other words:</p>
<table>
-<tr><th></th><th>Maven</th><th>Eclipse</th></tr>
-<tr><th>Unix</th><td>use workaround when new DN version</td><td>no known issues</td></tr>
-<tr><th>Windows</th><td>use workaround for path limit<br/>use workaround when new DN versions</td> </td><td>use workaround for path limits</tr>
+<tr><th> </th><th>Maven</th><th>Eclipse</th></tr>
+<tr><td><b>Unix</b></td><td>use workaround when new DN version</td><td>no known issues</td></tr>
+<tr><td><b>Windows</b></td><td>use workaround for path limit<br/>use workaround when new DN versions</td> </td><td>use workaround for path limits</tr>
</table>
-<p>In addition, Eclipse's enhancer needs some special care over the classpath</p>
+<p>In addition, Eclipse's enhancer needs some special care over the classpath.</p>
<h2>For Eclipse: configuring the enhancer</h2>
<p>for the domain object model project, first add DataNucleus support:</p>
-<p><img src="resources/eclipse-100-project-support.png" width="600px"/></p>
+<p><img src="resources/eclipse-100-project-support.png" width="400px"/></p>
<p>Then turn on Auto-Enhancement:</p>
-<p><img src="resources/eclipse-110-project-support.png" width="600px"/></p>
+<p><img src="resources/eclipse-110-project-support.png" width="400px"/></p>
<h3>For Eclipse: classpath considerations</h3>
@@ -229,7 +225,7 @@ This page is a work-in-progress
<p>And tell DataNucleus to use the project classpath:</p>
-<p><img src="resources/eclipse-010-windows-preferences.png" width="600px"/></p>
+<p><img src="resources/eclipse-010-windows-preferences.png" width="400px"/></p>
<p>When the enhancer runs, it will print out to the console:</p>
@@ -245,7 +241,7 @@ This page is a work-in-progress
<h3>For Eclipse: Windows > Preferences</h3>
-<p><img src="resources/eclipse-020-windows-preferences.png" width="600px"/></p>
+<p><img src="resources/eclipse-020-windows-preferences.png" width="400px"/></p>
<h2>Workaround for DN versions: using a profile</h2>
@@ -257,7 +253,7 @@ This page is a work-in-progress
<p>The fix is to use a Maven profile:</p>
-<p><img src="resources/eclipse-300-range-incompatibilities.png" width="600px"/></p>
+<p><img src="resources/eclipse-300-range-incompatibilities.png"/></p>
<p>This says that when <em>not</em> run within Eclipse (the ${m2e.version} property is <em>not</em> set), then to use the latest version of the DataNucleus dependency can be referenced. You can maintain the <version> to keep track with the latest-n-greatest available in the Maven repo.</p>
@@ -272,7 +268,7 @@ This page is a work-in-progress
<p>The best solution is to remove DataNucleus support and then to re-add it:</p>
-<p><img src="resources/eclipse-220-enhancer-fails-duplicates.png" width="600px"/></p>
+<p><img src="resources/eclipse-220-enhancer-fails-duplicates.png" width="400px"/></p>