> On Mon, 25 Oct 2004 04:56:45 +0000, [EMAIL PROTECTED] wrote: >> URL: http://wiki.apache.org/struts/StrutsShale
A few more more notes. > 2.4 View Controller > 3.3 View (Presentation) Tier APIs > Proposal:: JavaServer Faces 1.1 Does the View Controller need to be tied to JSF? Could the interface be agnostic and a FacesViewController be provided that is specific to JSF? Or, could there be a [org.apache.shale.faces] package, allowing room for, say, a [org.apache.shale.xlst] package or a [org.apache.shale.jstl] package or a [org.apache.shale.velocity] ? I'm not saying that we would have to provide all of these packages for Shale to be complete. I'd just like to position Struts 2.x so it could be everyone's controller :) -- if there are volunteers ready, willing, and able to make it so. > 2.5 Functionality Not Included In Struts 2.0 Core Would any view packages be bundled with the 2.x core, or would the core be the Application controller and interfaces for the Dialog and View controllers (and any implementation-independent utilities). > 2.5 Functionality Not Included In Struts 2.0 Core Since "client-side" validation is mentioned, are we leaving the door open for "server-side" validation? Perhaps as an abstract link in the request processing chain? Would there be an interface for the Application Controller? > [New topic] 2.6 Unit Tests Would it be all right if I contributed some unit tests to the codebase accompanying the proposal? I realize that everything is subject to change, and the tests would have be resynched with any changes, but I'm up for that :) Obviously, the tests would not be much at this point, but I want to be sure we start out on the right foot. > 3.8 Logging APIs Proposal: Commons Logging +1 On Tue, 26 Oct 2004 01:14:40 -0400, Ted Husted wrote: >> 3.1 Java2 Standard Edition APIs >> > I'd be +1 for J2SE 5.0 > > * http://java.sun.com/j2se/1.5.0/index.jsp > > Since Struts 1.x is in evolutionary mode, we might as well start > the revolution based on the latest and greatest. We'd then be able > to "take advantage of annotations, generics, and all that". From > the traffic on the list, I have the feeling many of us have JDK 5.0 > itches. I'm getting one myself :) > > As Apache Beehive reasoned, by the time we are done, it will be > widely deployed. If we both base our work on JDK 5.0, we might help > that become a self-fulfilling prophesy :) > > >> 3.5 Service Provisioning APIs >> From my research so far, I like Spring's capabilities in this >> area the best, but am open to other suggestions. >> > +1 > > > On Mon, 25 Oct 2004 04:56:45 +0000, [EMAIL PROTECTED] wrote: > >> Date: 2004-10-24T21:56:45 >> Editor: CraigMcClanahan <[EMAIL PROTECTED]> >> Wiki: Apache Struts Wiki >> Page: StrutsShale >> URL: http://wiki.apache.org/struts/StrutsShale >> >> Pointers to information about the "Shale" proposal >> >> New Page: >> >> This is a proposal for an overall architecture for Struts 2.0, >> based on dividing the controller tier into >> modular layers, and dramatically increasing the usability of the >> controller functionality. >> >> * [http://svn.apache.org/viewcvs.cgi/*checkout* >> /struts/trunk/contrib/struts-shale/README.html Proposal Details] >> (latest SVN version) >> * [http://www.apache.org/~craigmcc/struts-shale/ API Javadocs] >> (periodically updated) >> >> >> ------------------------------------------------------------------ >> -- - 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] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
