I'm not an expert in Struts 2 but I will respond based on my experience: 1.- Themes. They make the framework harder to understand and slower, and to me adds little value.
MG>How would you differentiate between ajax and simple themed controls? NB> Personally, when I started to work on Struts 2, the theme part was very confusing, specially when the simple theme generates additional HTML code that you don't want. I don't know if there's a way to get the tags to just generate the controls their suppose to generate without using FTLs, so you get better performance. I had a problem with a client that was migrating from Struts 1 and they were complaining that it has less performance, and yes I applied all the guidelines on how to get better performance with Struts 2 including the problem with caching the ftl files. 2.- Validation is OK, but need better validation support like validation of list items. And the ability to validate a specific Action method in a straightforward way. Better JavaScript support. MG>if Dojo supports validation Struts 2 can incorporate that JS Validation routine in the ftl NB>Yes we have incorporated A LOT!!! of javascript validation in the form-close-validation.ftl file but Struts 2 should come with a lot of this validations from the start, like date, number validation, date and number range validation based on other fields, condition validation. Now I have a library of this validations that I reuse from project to project. Until now, I haven't been able to resolve the problem of list items validation, for example I have a list of addresses and I want to validate specific fields of each address in the list. Also it would be MUCH MORE FLEXIBLE if you could create validators in the form Action-method-validator.xml. The other way requires a lot of configuration if you're creating transactions that span multiple screens (like assistants for example). 3.- Struts 2 Tags should be more flexible. MG>Flexible? How? NB>Iterator tag can't iterate based on a dynamic number range, let's say from 1 to 5, I can do this creating a list statically but the problem is when I have a dynamic range. The radio tag doesn't allow you to put radio controls wherever you want, I have to create them manually. Yes I could modify the radio.ftl but different pages have different requirements. There is a date tag but no number tag to format numbers (also it has localized Date conversion, but no localized Number conversion), you have to do them with <s:text> or programming your own converter. If I have a select combo box and it receives a null list it will generate an Exception (Possible scenario, the list will be filled by AJAX), I have to always check that all my lists have an empty List. This are things that I could do easily with Struts 1 and JSTLs. The framework is a HUGE improvement over Struts 1, and I personally will never go back. If you study the web framework market (Struts 1, 2, Spring, JSF), I would definetely go with Struts 2 like in all my projects for it's maturity. I think it's a very good and flexible framework, which I stated in my pros. There are just some things that could be better ... like ANY framework for that matter. Néstor ______________________________________________ Disclaimer and confidentiality note Everything in this e-mail and any attachments relates to the official business of Sender. This transmission is of a confidential nature and Sender does not endorse distribution to any party other than intended recipient. Sender does not necessarily endorse content contained within this transmission. > Date: Mon, 10 Nov 2008 08:52:45 +0800 > From: [EMAIL PROTECTED] > To: user@struts.apache.org > Subject: Re: What are Pros and Cons for Struts 2? > > > > Thanks to all replies! I really appreciated all replies all are really > > helpful and informative. > > > > On Sat, Nov 8, 2008 at 9:02 AM, Gabriel Belingueres > > <[EMAIL PROTECTED]>wrote: > > > > > Pros: > > > Easy to learn and start with (some free books available.) > > > Great community (mailing list.) > > > Very extensible. > > > > > > Cons: > > > Sporadic releases. > > > Javascript validation framework is very limited for non ajax apps. > > > Multiple rendering technologies make their component model hard to > > > modify or extends (parallel class hierarchies for both components and > > > tags, and component's HTML code and styles are tied to a particular > > > theme.) > > > > > > 2008/11/7 Néstor Boscán <[EMAIL PROTECTED]>: > > > > Hi Ryan > > > > > > > > In my experience: > > > > > > > > Pros: > > > > > > > > 1.- Form mapping!!!. Yes form mapping in Struts 1 is horrible. > > > > 2.- Conversion support > > > > 3.- Interceptor support > > > > 4.- Better AJAX Support > > > > 5.- Lightweight vs JSF > > > > > > > > The framework is very flexible and you can adjust it to your needs. > > > > > > > > Cons: > > > > > > > > 1.- Themes. They make the framework harder to understand and slower, > and > > > to > > > > me adds little value. > > > > 2.- Validation is OK, but need better validation support like > validation > > > of > > > > list items. And the ability to validate a specific Action method in a > > > > straightforward way. Better JavaScript support. > > > > 3.- Struts 2 Tags should be more flexible. > > > > So there it is. > > > > On Thu, Nov 6, 2008 at 11:18 PM, ryan webb <[EMAIL PROTECTED]> > wrote: > > > > > > > >> Can anyone share to me some of the things you like about > > > >> Struts 2 as well some of the things you don't like about struts 2? > > > >> > > > >> Thanks! > > > >> > > > > > > > > > > --------------------------------------------------------------------- > > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > > > > > > > > -- > > warmest regards, > > Ryan Webb - Philippines > > > > email: [EMAIL PROTECTED] > > _________________________________________________________________ > Get 5 GB of storage with Windows Live Hotmail. > > http://windowslive.com/Explore/Hotmail?ocid=TXT_TAGLM_WL_hotmail_acq_5gb_112008 >
