AppFuseRoadmap |
|
Your trail: |
This is version 102.
It is not the current version, and thus it cannot be edited.
[Back to current version]
[Restore this version]
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.
AppFuse 2.0 - late 2006
- JDK 5, Annotations and JSP 2.0
- Maven 2 integration while (hopefully) continuing to support Ant. Ideally, we could use Maven to generate Ant files. However, the Maven Ant Plugin has quite a few issues that need to be fixed first.
- Support for JDK 1.4 using something like Retroweaver.
- Replace Struts with Struts Action 2 (a.k.a. WebWork) and remove extras/webwork.
- Support for using AppFuse as a library.
- Support for creating a new project using AppFuse as an archetype (from Maven).
- Replace AppGen with a solution that's not based on XDoclet. Hopefully annotations can be read and used, possibly using something like Greenbox.
AppFuse 2.1 - early 2007
- Search using Compass.
- Pageable lists that only fetch a specified number of records (i.e. 10 at a time).
Future
- (Possibly) Add a Swing client that can talk to at least one of the above frameworks (if not all).
- (Possibly) Add a Laszlo front-end.
- (Possibly) Add Wicket as a supported web framework.
- Change from using Canoo WebTest to using Selenium for UI testing.
- What others would like to see
Various Ideas - don't know if we'll use them
- Use JMeter or Microsoft's Web Application Testing tool to configure load testing scripts for inclusion in the distribution. Motivated by this post.
- Create tutorial on how to integrate Quartz (using Spring).
- Create tutorial on how to integrate Lucene for searching users.
- Add Configuration object that talks to a database table for application configuration. Create a dynamic UI (JSP) to handle updating.
|