That looks OK to me (though the thing about separate methods for GET and POST is not really true for my application anywhere).
The coolness of Stripes parameter-property mapping is (for me) easier to appreciate on the input side, especially when there's something akin to Stripersist to handle implicit loading of objects from the database. I can't compare that to the Spring world because I've never been to the Spring world. On Sun, Nov 29, 2009 at 2:36 AM, Rusty Wright <[email protected]> wrote: > Thinking out loud; did I make any mistakes about how Stripes works? > > http://lumpynose.wordpress.com/2009/11/29/action-based-frameworks-vs-spring-mvc-under-the-hood/ > > ------------------------------------------------------------------------------ > Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day > trial. Simplify your report design, integration and deployment - and focus on > what you do best, core application coding. Discover what's new with > Crystal Reports now. http://p.sf.net/sfu/bobj-july > _______________________________________________ > Stripes-users mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/stripes-users > -- Turtle, turtle, on the ground, Pink and shiny, turn around. ------------------------------------------------------------------------------ Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july _______________________________________________ Stripes-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/stripes-users
