Here's one, which is Struts vs. WebWork 1.x http://www.mail-archive.com/[EMAIL PROTECTED]/m sg00995.html
Which is only discussing WW1... WW2 is even further ahead, adding: * Interceptors -> Can be applied via configuration file. You do AOP so you should get this * OGNL -> A VERY powerful expression language * A nice flexible validation framework which can be used in your web app and throughout your application * Flexible type conversion * An IoC container to automatically fulfill component dependencies * powerful package-based configuration with configuration inheritance, etc. Here's my writeup of Mike's talk at TSSS http://wiki.opensymphony.com/space/Writeup+of+Mike%27s+Talk+at+TSS+on+We bWork2 This is all on top of the advantages WW1 had, such as: * Easily testable -> Your actions aren't tied to the web, so you can just set values in your properties and execute your Actions. This is one of the biggest productivity bonuses for development groups who stress unit testing * Interface based, not abstract base class -> You don't have to extend ActionSupport to use the framework, any class implementing the Action Interface can be used * NO FORMBEANS REQUIRED! -> You can choose to use sub-objects to group your properties, or you can have your properties directly on your Action Then there are general project advantages: * Mike and I are committers, and you know us :-) * Stuts is part of Apache, so every change requires committee approval :-) * If you have something you need changed or new ideas for the framework, you're much more likely to get it added here than in Struts (especially if you send a patch with unit tests) Let me know if there's anything else we can do to help your cause... Jason > -----Original Message----- > From: Bob Lee [mailto:[EMAIL PROTECTED] > Sent: Saturday, September 20, 2003 8:41 PM > To: [EMAIL PROTECTED] > Subject: [OS-webwork] WebWork vs. Struts > > > Does someone have a really good WebWork vs. Struts comparison > (specifically the benefits WebWork has over Struts). My > employer chose > Struts, but we haven't started development yet and I've talked them > into letting me put together a proposal to use WebWork instead. > > Thanks, > Bob > > > > ------------------------------------------------------- > This sf.net email is sponsored by:ThinkGeek > Welcome to geek heaven. > http://thinkgeek.com/sf > _______________________________________________ > Opensymphony-webwork mailing list > [EMAIL PROTECTED] > https://lists.sourceforge.net/lists/listinfo/opensymphony-webwork > ------------------------------------------------------- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf _______________________________________________ Opensymphony-webwork mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/opensymphony-webwork
