> Again, I'm not attempting to "prove" that SpringMVC is better than Stripes, > the question of interest is whether Stripes encourages bad practice from an > OO point-of-view?
I suppose it depends on your definition of OO - I use subclassing in my ActionBeans so that I can share common parameters and validators efficiently. That is hard to do when your method arguments define the parameters. Also, I could argue that it's a slightly better OO practice to have lots of small ActionBeans, rather than big ActionBeans that have multiple entry points. But it depends on what you think of as an "Object" in a web application sense, and how Model-centric your thinking is. I don't really see either way as inherently bad practice. /Janne ------------------------------------------------------------------------------ Free Software Download: Index, Search & Analyze Logs and other IT data in Real-Time with Splunk. Collect, index and harness all the fast moving IT data generated by your applications, servers and devices whether physical, virtual or in the cloud. Deliver compliance at lower cost and gain new business insights. http://p.sf.net/sfu/splunk-dev2dev _______________________________________________ Stripes-users mailing list Stripes-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/stripes-users
