In terms of new features, I would like to see the Scope plugin integrated into the core similar to the plan for Convention. This seems like an essential service for a modern mvc framework. However, the plugin as it stands is not feature complete. I believe the following features would make it generic enough to be applied to a variety of common use cases:

1. Action method based annotations (context sensitive bijection, not requiring you to create a new action for variations in scope usage) 2. Result sensitive outjection (such that in case of error, an object is not outjected)
3. Pluggable scopes / scope processors

--------------------------------------------------
From: "Don Brown" <[EMAIL PROTECTED]>
Sent: Sunday, June 01, 2008 8:59 AM
To: "Struts Developers List" <dev@struts.apache.org>
Subject: [s2] 2.1 to 2.5 Roadmap discussions

Struts 2 desperately needs a public roadmap, IMO, so here's a quick
strawman to get the discussion started:

Struts 2.1

   * New plugins: REST, Dojo, DWR, Portlet, JUnit, and TestNG
   * Internal API cleanups

Struts 2.2

   * Finalize zero configuration strategy with new Conventions plugin
         o Move REST Plugin over to use Conventions plugin, if necessary
         o Ensure full legacy support
   * OSGi Plugin?
   * Public API

Struts 2.5

   * 2.5 and not 2.3 to reflect important changes in xwork
         o Guice 1.0
         o Reworked localization
   * JSR 303 (Bean Validation) support
   * Built-in command line tool like Grails

I'm mirroring the proposal on this wiki page:

http://cwiki.apache.org/confluence/display/S2WIKI/2.1+to+2.5+Roadmap

Also keep in mind, what we can do is very much constrained by who
volunteers to do the work.  Most of what is on the strawman are
features that Rainer, Rene, or I have already indicated we plan on
working on.  Still, don't hesitate to throw out ideas that may inspire
someone to take them up.

Don

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to