I don't think there's some magic threshold, before which Struts is overkill and beyond which Struts is a no-brainer. For a very small application (couple of servlets, a handful of JSP's, etc.), Struts is most likely overkill, especially for someone who's never used it before and has at least some ramping up to do. But even for moderate applications (say, 10-20 pages), the power and value of Struts (especially once you're comfortable with the architecture) becomes obvious everywhere you look. It takes only one or two maintenance or upgrade nightmares with a Model 1-type application before you find yourself wondering whether things could be improved.
I'd suggest you look at the architecture diagrams and sample applications (such as MailReader) until you have a good sense of how it all fits and flows together. I suspect you'll find it illuminating (and maybe even give you some ideas about how to improve your current application), but if not, then perhaps it's not a compelling product for your effort. There's certainly no reason to chase down and use certain technologies only because they're popular or sound cool. (Editorial: I suspect XML has derived most of its popularity due to the latter, but I digress...). ----- Original Message ---- From: Geffrey Caruso <[EMAIL PROTECTED]> To: Struts Users Mailing List <user@struts.apache.org> Sent: Thursday, April 19, 2007 4:24:50 PM Subject: RE: Migrating to Struts 2 Right that is my worry. That migrating will be basically starting from scratch which we definitely do not want to do. We are going to be adding a lot of new feature in the near future but I don't want to expend a huge effort to get into Struts just to say we are in struts. I'm looking for compelling reasons to switch and I just can't seem to come up with one. That's why I mentioned the form heavy site. If we were moving towards something like that I could see the usefulness. I'd like to see some discussion of what kind of apps struts is really good for and what kinds of apps it is overkill for. -----Original Message----- From: Shahak Nagiel [mailto:[EMAIL PROTECTED] Sent: Thursday, April 19, 2007 12:57 PM To: Struts Users Mailing List Subject: Re: Migrating to Struts 2 First question: Why are you looking to migrate? My general opinion on foundational upgrades like this is, "don't fix it if it ain't broke." I wouldn't necessarily agree that Struts (1 or 2) is "geared towards form-heavy apps". I'd say it's a powerful and flexible manifestation of the MVC design pattern that makes reuse and maintenance much easier than a traditional (aka "Model 1") application for moderate-to-large application, but if you already have a stable (and relatively small) application, I don't see a compelling need to re-architect it. OTOH, if you're on the bring of having to make a lot of changes/additions in the near future, then "migrating" to Struts will not be much different than simply starting from scratch, so I'd suggest reading through the tutorials and sample apps. ----- Original Message ---- From: Geffrey Caruso <[EMAIL PROTECTED]> To: Struts Users Mailing List <user@struts.apache.org> Sent: Thursday, April 19, 2007 11:53:58 AM Subject: Migrating to Struts 2 Ok I'm looking for some advice on migrating and existing web application to struts 2. I've seen a lot of stuff online on migrating from struts 1 or from Web Works but not much on migrating an app that isn't in any existing framework. What we currently have is a web app that uses a custom Ajax implementation, Tiles, maybe a dozen servlets, a lot of JSPs, one applet, and a ton JavaScript files It's not a form heavy application and that's why I'm hesitant to move to struts 2. From what I've read it seems to be more geared towards apps that are heavy on the form side and need a lot of flow control. Our app isn't like that nor do I see it being like that in the near future. I just don't want to spend tons of time converting this app to struts 2 only to find out it doesn't offer us that much over what we are doing right now. Any advice anyone could offer or any websites they could point me to would be much appreciated. Thanks --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
