I find that "no framework" allows quicker writing while using a framework (i.e.: Struts) leads the thought processes to eventually produce cleaner, better organized, easier to maintain code. At least at first, using a framework will be slower, with productivity catching up as you gain experience and start reusing your code. When I was at the top of my game and past the awkward first week or two of a project, by using Struts (1.2.x at the time) I could go from a paper drawing to a fully implemented and unit-tested web page (including the database code) in 4 hours. You should not expect such productivity right away... 1-3 pages per week are probably reasonable at first.
I hope that provides some perspective. bruno -----Original Message----- From: Frank W. Zammetti [mailto:[EMAIL PROTECTED] Sent: Friday, May 11, 2007 10:49 AM To: Struts Users Mailing List Cc: Struts Users Mailing List Subject: Re: Need a recommendation to use struts version That's certainly not a bad approach, I wouldn't disagree... however, only the person actually architecting the application can make the determination... I don't know if any of this is true, so it's just hypothesizing, but consider this... The OP knows servlets, JSP and JSTL pretty well, but has no experience at all with Struts... further, the application truly is simple, i.e., a handful of screens, some simple CRUD operations, etc... lastly, he (and hopefully a representative of the business) doesn't forsee much, if any, expansion in the future. In that case, jumping on Struts, or any other framework, might be counterproductive (except from the point of view of wanting to learn something new, which is of course always worth it). This doesn't invalidate your answer, not in the least, I happen to agree with you... but I also believe in choosing the right tool for the job, and sometimes that isn't breaking out the chain saw to cut a piece of Balsa wood :) Unless you suspect that toy airplane for your kid is going to need to morph into a 747 later that is :) Frank -- Frank W. Zammetti Founder and Chief Software Architect Omnytex Technologies http://www.omnytex.com AIM/Yahoo: fzammetti MSN: [EMAIL PROTECTED] Author of "Practical Ajax Projects With Java Technology" (2006, Apress, ISBN 1-59059-695-1) and "JavaScript, DOM Scripting and Ajax Projects" (2007, Apress, ISBN 1-59059-816-4) Java Web Parts - http://javawebparts.sourceforge.net Supplying the wheel, so you don't have to reinvent it! On Fri, May 11, 2007 11:08 am, Musachy Barroso wrote: > I haven't seen a single project that starts as a simple application > and with time doesn't grow up to a big application. That's why I like > to use the right tools since the beginning, assuming it will grow > someday. > > 2 cents > > musachy > > On 5/11/07, Frank W. Zammetti <[EMAIL PROTECTED]> wrote: >> >> Don't forget one possible option here: don't use Struts at all. In >> fact, don't use any FRAMEWORK at all! >> >> What your describing isn't enough to make a recommendation whether to >> use a framework or not, but since you yourself describe it as simple, >> then you may not even need all Struts has to offer, or any other >> framework. >> Plenty >> of good, production-quality applications are still built sans any >> framework, it's a prefectly viable alternative in some cases. Now, >> don't get me wrong: I'd lean towards using *something* initially too, >> it >> *usually* makes more sense, but you shouldn't dismiss the alternative >> out of hand IMO. >> >> Frank >> >> -- >> Frank W. Zammetti >> Founder and Chief Software Architect >> Omnytex Technologies >> http://www.omnytex.com >> AIM/Yahoo: fzammetti >> MSN: [EMAIL PROTECTED] >> Author of "Practical Ajax Projects With Java Technology" >> (2006, Apress, ISBN 1-59059-695-1) >> and "JavaScript, DOM Scripting and Ajax Projects" >> (2007, Apress, ISBN 1-59059-816-4) >> Java Web Parts - http://javawebparts.sourceforge.net >> Supplying the wheel, so you don't have to reinvent it! >> >> On Fri, May 11, 2007 9:55 am, Saravanan Vijayappan wrote: >> > >> > Hello, >> > >> > Which Struts version is preferred to use in production environment ?. >> The >> > below is my requirement. >> > >> > 1. it's simple MVC application >> > 2. The backend would be mysql db >> > 3. No EJBs >> > 4. No Ajax >> > 5. Servlets, JSP, JSTL would be used. >> > >> > Please adivise me ! >> > >> > Thanks & Regards, >> > Saravanan Vijayappan, >> > +91 9448833571. >> > >> > >> > >> > >> > >> > >> _____________________________________________________________________ >> _______________ >> > Bored stiff? Loosen up... >> > Download and play hundreds of games for free on Yahoo! Games. >> > http://games.yahoo.com/games/front >> >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: [EMAIL PROTECTED] >> For additional commands, e-mail: [EMAIL PROTECTED] >> >> > > > -- > "Hey you! Would you help me to carry the stone?" Pink Floyd > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
