AppFuseRoadmap

This is version 56. It is not the current version, and thus it cannot be edited.
[Back to current version]   [Restore this version]

July/August 2004

• Add WebWork as a web framework choice. Status: Done.
• Replace Tiles with Sitemesh as part of this process. Status: Done.
• Enhance IDE integration, particularly with Eclipse and hot deploying. Attempt to get AppFuse working with MyEclipse. Figure out a way so that unit tests do not depend on running Ant first.
• Remove seldom used components (i.e. Clickstream, PMD, Checkstyle) and add documentation on how to add them back in. Status: More trouble than it's worth.
• Modify Cactus to create a <runcontainer> task for all supported containers. The idea here is to make AppFuse so it can be easily run with Resin or Tomcat, by only changing a few Ant properties. Status: Not in this release, Cargo is the answer - but it's not quite ready for primetime. It says it can't start Tomcat when it's apparent that it started fine from the log file. Also, it doesn't show any container startup log messages whereas runservertests does. Maybe in the 1.7 (w/ Tapestry) release.
• Add support/documentation for Sun Appserver 8.
• Fix XDoclet form generation one-to-one mappings. Figure out and document how to generate validation rules for nested forms. Status: Done.
• Replace Mail classes with Spring's Mail support. Status: Done.
• Fix all these damn bugs ;-)

• [Low Priority] Figure out how to use MockStrutsTestCase to run ActionTests out-of-container. In-container is too slow. {Lance: Try mockrunner.sf.net - check out the BookmarksActionTest in Roller (baby steps). I never did get MockStrutsTestCase to work.} {Carlos: I've got it to work ;) You can check http://oness.sourceforge.net subproject oness-party-webapp}
• [Low Priority] Add Configuration object that talks to a database table for application configuration. Create a dynamic UI (JSP) to handle updating.

• MILESTONE: Release 1.6 and take a break before the Tapestry/JSF push (1.7 and 2.0).

Fall/Winter 2004

• Add Tapestry as a web framework choice.
• Figure out how to use Mocks to create faster unit tests, rather than just integrations tests (which is what exists now).
• Add JSF as a web framework choice.
• (Possibly) Add a Swing client that can talk to at least one of the above frameworks (if not all).

Various Ideas - don't know if I'll use them'