Access Keys:
Skip to content (Access Key - 0)

Release Notes 2.0 M3

Enter labels to add to this page:
Please wait 
Looking for a label? Just start typing.

Please see the Upgrade Guide below or the QuickStart Guide to get started with this release. The major feature in this release is documentation! All of the web tutorials tutorials have been written and tested. In addition, we figured out how to get native2ascii to work with Maven 2 - so all i18n bundles and supported languages (now including Turkish!) should work. Besides those key features, this is primarily a bug fix release. We still plan on creating a Maven plugin for code generation, as well as integrating XFire.

Thanks to all the developers and users that have helped with this release!

Upgrade Guide

If you're currently using AppFuse 2.0 M2, here's a few things you'll need to change to upgrade to 2.0 M3.

Diff is your friend
The easiest way to make the changes below might be to compare your pom.xml, web.xml and web-tests.xml with the ones from a new archetype. Beyond Compare is a fabulous diff tool for Windows users.
  1. Backup your project on your local file system or (even better) in your source control system.
  2. In pom.xml, change <appfuse.version>2.0-m2</appfuse.version> to <appfuse.version>2.0-m3</appfuse.version>.
  3. Change your pom.xml so the hibernate3 plugin's hbm2ddl goal runs in the "process-test-resources" phase instead of the "test-compile" phase (diff). This prevents dbunit from executing before the schema is created.
  4. Modify log4j.xml so it has INFO logging for org.appfuse and DEBUG logging for your groupId (diff).
  5. Move the values in struts.properties into struts.xml as contants (diff).
  6. In web.xml, comment out the filter-mapping for the gzipFilter since it causes issues with foreign characters and exporting from the Display Tag.
  7. The applicationContext-resources.xml has been added to src/main/resources of the archetypes and included in web.xml (using classpath*:/applicationContext-resources.xml). You'll need to download this file into your project for it to work correctly.
  8. Change src/test/resources/web-tests.xml so the "AddUser" test redirects to the list screen instead of back to the form (diff).
  9. If you're using Struts, you can consolidate the "label", "value" and "name" attributes into a single "key" attribute. See Simplified UI Tags in Struts 2 for more information.
  10. If you're using Tapestry, you need to modify your web-tests.xml to use "fileField" instead of "Upload" in the "FileUpload" target (diff).
  11. Add <filtering>true</filtering> in <testResource> section.
  12. Add ${jdbc.* variables as a <dependency> in pom.xml (APF-580).
  13. Add new keys for tagline, version and company information (APF-619).
  14. If you're using Tapestry, the package names changed from org.appfuse.webapp.action to org.appfuse.webapp.pages and org.appfuse.webapp.tapestry to org.appfuse.webapp.components. You'll need to make these changes in your Java code, as well as tapestry.application.
  15. If you're using Struts, you'll need to add Struts 2.0.5 repository to your pom.xml:
<repository>
    <id>struts-205-staging</id>
    <name>Apache Struts 2.0.5 Staging Repository</name>
    <url>http://people.apache.org/builds/struts/2.0.5/m2-staging-repository</url>
</repository>

Detailed Changelog

Adaptavist Theme Builder (4.0.0-M8) Powered by Atlassian Confluence 3.1, the Enterprise Wiki.