Raible's Wiki: AppFuseRoadmap

At line 1 changed 1 line.

This page is designed to document the things [I|MattRaible] want to do with AppFuse in 2004. Feel free to add suggestions as you see fit.

This page is designed to document what's on the roadmap for future versions of AppFuse. Feel free to add suggestions as you see fit. For a more detailed report of where we are on the roadmap, see the [roadmap in JIRA|http://issues.appfuse.org/browse/APF?report=com.atlassian.jira.plugin.system.project:roadmap-panel].

At line 3 changed 9 lines.

!!July/August 2004

* Add [WebWork|http://www.opensymphony.com/webwork/] as a web framework choice. Replace Tiles with Sitemesh as part of this process.

* Enhance IDE integration, particularly with Eclipse and hot deploying. Attempt to get AppFuse working with [MyEclipse|http://www.myeclipseide.com]. 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.

* 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 Started, <a href="http://www.mail-archive.com/cactus-user%40jakarta.apache.org/msg05019.html">here is the thread</a> for implementing this.

* 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.

* Replace Mail classes with Spring's Mail support.

* Fix all [these damn bugs|https://appfuse.dev.java.net/issues/buglist.cgi?Submit+query=Submit+query&component=appfuse&issue_status=NEW&issue_status=STARTED&issue_status=REOPENED&email1=&emailtype1=exact&emailassigned_to1=1&email2=&emailtype2=exact&emailreporter2=1&issueidtype=include&issue_id=&changedin=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&short_desc=&short_desc_type=substring&long_desc=&long_desc_type=substring&issue_file_loc=&issue_file_loc_type=substring&status_whiteboard=&status_whiteboard_type=substring&field0-0-0=noop&type0-0-0=noop&value0-0-0=&cmdtype=doit&order=Reuse+same+sort+as+last+time] ;-)

!!AppFuse 2.0 - late 2006

At line 13 changed 2 lines.

* [[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.}''

* [[Low Priority] Add Configuration object that talks to a database table for application configuration. Create a dynamic UI (JSP) to handle updating.

!Milestone 1

* Maven 2 integration

* Migrate from CVS to Subversion

* Remove XDoclet, putting generated files into source tree

* Get all flavors (WARs) deployed and running on Tomcat and Jetty Maven Plugin

* Spring 2.0: Upgrade XML to XSDs, annotations where appropriate

* Upgrade WebWork to Struts 2

* Documentation - move to new Confluence or DocBook-based system for 2.0 documentation

At line 16 changed 1 line.

* __MILESTONE:__ Release 1.6 and take a break before the Tapestry/JSF push (1.7 and 2.0).

!Milestone 2

* [JDK 5, Annotations and JSP 2.0|http://raibledesigns.com/page/rd?anchor=appfuse_2_0_jdk_5]

* Archetypes for creating new AppFuse projects

* Documentation, including screencasts for tutorials

At line 18 changed 5 lines.

!!Fall/Winter 20004

* Add [Tapestry|http://jakarta.apache.org/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|http://java.sun.com/j2ee/javaserverfaces/] as a web framework choice.

* (Possibly) Add a Swing client that can talk to at least one of the above frameworks (if not all).

!Milestone 3

* Integrate XFire by default (for existing classes and generated classes)

* Code Generation/AppGen - hopefully with the [AppFuse Maven Plugin|http://mojo.codehaus.org/appfuse-maven-plugin/]

* Documentation

At line 24 added 8 lines.

!2.0 Nice to haves

* TestNG replacing JUnit

* Hibernate Validation Annotations (hard part is hooking it into the web frameworks)

* Tomcat Plugin for Maven (that operates like Jetty's plugin) (Looks like there is a [Maven 2 Tomcat Plugin|http://mojo.codehaus.org/tomcat-maven-plugin/introduction.html] that supports [tomcat:run|http://jira.codehaus.org/browse/MOJO-384] and [tomcat:run-war|http://jira.codehaus.org/browse/MOJO-567] (pending))

* JPA Support

* Support for JDK 1.4 using something like [Retroweaver|http://retroweaver.sourceforge.net/]

* Support for using Ant to build/test/deploy AppFuse-based projects

* Someone to do all the documentation ;-)

At line 25 changed 1 line.

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

!!AppFuse 2.1 - early 2007

* Search using [Compass|http://www.opensymphony.com/compass/], tutorials already existing for [Spring MVC|http://www.nabble.com/search---integrate-compass-%28lucene%29-and-appfuse-p5022176s2369.html] and [JSF|http://www.nabble.com/RE%3A-search---integrate-compass-%28lucene%29-and-appfuse-p5222253s2369.html]

* Pageable lists that only fetch a specified number of records (i.e. 10 at a time)

* Ajax Goodies (TBD)

!!AppFuse 2.2

* Convention over configuration, no XML modifications needed when adding new files

* Plugin API so all "features" can be added/removed via plugins

* Add Wicket and Stripes as supported web frameworks

!!Future

* (Possibly) Add a Swing/RCP, Laszlo and/or J2ME front-end

* Change from using Canoo WebTest to using [Selenium|http://openqa.org/selenium/] for UI testing ([Maven + Selenium HowTo|http://docs.codehaus.org/display/MAVENUSER/Maven+and+Selenium])

* [What others would like to see|http://raibledesigns.com/page/rd/Weblog/if_you_could_add_another]

!!Various Ideas - don't know if we'll use them

At line 27 changed 5 lines.

* Use JMeter or Microsoft's Web Application Testing tool to configure load testing scripts for inclusion in the distribution. Motivated by [this post|http://blog.rossmason.com/archives/000025.html].

* Create tutorial on how to integrate Quartz.

* Create tutorial on how to integrate Lucene for searching users.

* Use Spring for Quartz, JavaMail and Velocity.

* Integrate <a href="http://tuckey.org/urlrewrite/">UrlRewriteFilter</a> for prettier URLs.

* Use JMeter, Grinder or Microsoft's Web Application Testing tool to configure load testing scripts for inclusion in the distribution. Motivated by [this post|http://blog.rossmason.com/archives/2004/02/jmeter_measures_up.html].

* Create tutorial on how to integrate Quartz (using Spring). See Luciano Fiandesio's <a href="http://www.lucianofiandesio.com/javatales/qtzfuse.html">AppFuse and Quartz: an integration tutorial</a>.

* Add Configuration object that talks to a database table for application configuration. Create a dynamic UI (JSP) to handle updating.

Raible's Wiki

AppFuse

Other Applications

AppFuseRoadmap