This week's book giveaway is in the OO, Patterns, UML and Refactoring forum. We're giving away four copies of Refactoring for Software Design Smells: Managing Technical Debt and have Girish Suryanarayana, Ganesh Samarthyam & Tushar Sharma on-line! See this thread for details.
I can't quantify, but i18n and scalability have been major concerns with the Struts development team. To get the most i18n you'll need the new Beta - the production release has areas that they've addressed. Security is less certain - I think they're mostly relying on the J2EE security mechanisms.
Customer surveys are for companies who didn't pay proper attention to begin with.
Joined: Jul 11, 2002
Thanks Tim. The J2EE security is mainly for EJB tier. I'm thinking about security on web tier - user authentication, access control, and single signon.
Security is a misnomer, b/c it is bigger than just the framework. There is no built in functionality inside STRUTS to handle security. I would suggest abandoning the stupid ".do" which tells the world "I'm a STRUTS web application"!!! The major down fall(s) of STRUTS in my view are posted below: 1) Only uses single servlet model 2) Does not have inherent Error Page subsytem included in tools (you must build these) 3) Implementation uses hashtable and Vector which are synchronized and not exceptionally fast. 4) Does not provide a BootStrap Servlet framework. 5) Documentation sucks! 6) No provided bug fixes. YOu have to wait till a volunteer posts a fix. Granted there a multide of reasons why you should use struts, and the best is the validation framework.