Author: jgbutler Date: Wed Oct 15 20:16:17 2008 New Revision: 705128 URL: http://svn.apache.org/viewvc?rev=705128&view=rev Log: [ibator] more documentation updates
Modified: ibatis/trunk/java/tools/ibator/core/htmldoc/migratingFromAbator.html ibatis/trunk/java/tools/ibator/core/htmldoc/whatsNew.html Modified: ibatis/trunk/java/tools/ibator/core/htmldoc/migratingFromAbator.html URL: http://svn.apache.org/viewvc/ibatis/trunk/java/tools/ibator/core/htmldoc/migratingFromAbator.html?rev=705128&r1=705127&r2=705128&view=diff ============================================================================== --- ibatis/trunk/java/tools/ibator/core/htmldoc/migratingFromAbator.html (original) +++ ibatis/trunk/java/tools/ibator/core/htmldoc/migratingFromAbator.html Wed Oct 15 20:16:17 2008 @@ -32,8 +32,9 @@ "http://ibatis.apache.org/dtd/ibator-config_1_0.dtd"> </pre> </li> - <li>All abator* elements are renamed to ibator*. For example, - <abatorConfiguration> is renamed to <ibatorConfiguration></li> + <li>The <abatorConfiguration> element is renamed to <ibatorConfiguration></li> + <li>The <abatorContext> element is renamed to <ibatorContext></li> + <li><ibatorContext> elements now require an ID</li> <li>The <code>generatorSet</code> attribute is removed from the <code><ibatorContext></code> element and replaced with the <code>targetJRE</code> attribute. Valid values for this @@ -62,6 +63,20 @@ simplified. If you specified a custom implementation on the <javaTypeResolver> element, you must rework your implementation class.</li> + <li>The ibator classloading strategy has changed substantially, and we now recommend that + you manage the runtime classpath external to ibator. If you manage the classpath with + configuration entries, you must make the + following changes from Abator: + <ul> + <li>Class path entries are specified at the configuration file level + with the <a href="configreference/classPathEntry.html"><classPathEntry></a> + element - now a child element of <code><ibatorConfiguration></code> only.</li> + <li>A <code><classPathEntry></code> element is not longer allowed as a child + of <code><jdbcConnection></code></li> + <li>The "rootClasspath" property is no longer valid for the <code><javaModelGenerator></code> + element.</li> + </ul> + </li> </ul> </body> </html> \ No newline at end of file Modified: ibatis/trunk/java/tools/ibator/core/htmldoc/whatsNew.html URL: http://svn.apache.org/viewvc/ibatis/trunk/java/tools/ibator/core/htmldoc/whatsNew.html?rev=705128&r1=705127&r2=705128&view=diff ============================================================================== --- ibatis/trunk/java/tools/ibator/core/htmldoc/whatsNew.html (original) +++ ibatis/trunk/java/tools/ibator/core/htmldoc/whatsNew.html Wed Oct 15 20:16:17 2008 @@ -56,41 +56,28 @@ <ul> <li>JSE 5.0 or higher is required for ibator</li> <li>Ibator does not contain the "legacy" code generators from Abator. You must - choose either the "Java2" or "Java5" generator set - and code generated from + choose "Java2" or "Java5" as a target JRE - and code generated from ibator is compatible with iBATIS version 2.2.0 or higher only. If you are using an earlier version of iBATIS - upgrade! If you are not able to upgrade, then you must continue to use Abator.</li> - <li>The DOCTYPE entry for configuration files has changed. The the - <a href="configreference/ibatorConfiguration.html"><ibatorConfiguration></a> - reference page for the correct DOCTYPE.</li> - <li>The classloading strategy in ibator is changed and simplified from Abator. All - classes are now loaded through the same classloader - including JDBC drivers, - Java model root classes, plugins, and ibator implementation classes. The - configuration for classloading has changed in these ways: - <ul> - <li>Class path entries are specified at the configuration file level - with the <a href="configreference/classPathEntry.html"><classPathEntry></a> - element - now a child element of <code><ibatorConfiguration></code> only.</li> - <li>A <code><classPathEntry></code> element is not longer allowed as a child - of <code><jdbcConnection></code></li> - <li>The "rootClasspath" property is no longer valid for the <code><javaModelGenerator></code> - element.</li> - </ul> - </li> - <li>Renamed <abatorConfiguration> to <ibatorConfiguration></li> - <li>Renamed <abatorContext> to <ibatorContext></li> - <li><ibatorContext> elements now require an ID</li> - <li>The API on the <code>DAOGenerator</code>, <code>JavaTypeResolver</code>, - <code>JavaModelGenerator</code>, and <code>SqlMapGenerator</code> interfaces - has changed. In most cases, implementations of these interfaces should + <li>The classloading strategy in ibator is changed from Abator. In all cases, we recommend + specifying the classpath external to ibator and we further recommend that you do not use + the <code><classPathEntry></code> element. You may specify classpath entries + if you feel you must, but those entries will only be used when loading JDBC drivers + of Java model root classes. If you write a custom extension to ibator, or a plugin, + you must specify that classpath entry external to ibator.</li> + <li>The API for extending ibator is significantly changed from Abator. + In most cases, implementations of these interfaces should be converted to ibator plugins.</li> <li>The <code>afterXXXGenerationHook</code> methods have been removed from all ibator supplied implementations of the core interfaces. If you were extending an ibator supplied implementation to make use of these methods, then you <em>must</em> migrate your code to an ibator plugin.</li> <li>The build has been significantly modified and now includes an Emma based - code coverage report (ibator is 78% covered in automated testing - with the core - code generators all over 95% covered - pretty good!) .</li> + code coverage report.</li> + <li>Many changes to the XML configuration file are required. See the + <a href="migratingFromAbator.html">Migrating from Abator</a> page for detailed + information</li> </ul> <h2>Version 1.1.0</h2>