On 11/9/06 2:18 PM, "Levan Dvalishvili" <[EMAIL PROTECTED]> wrote: > > Hi All! I have been recently trying to come up with at least top 5 > justifieable reasons , why one should consider migrating from struts 1.3 (or > even 1.2.X) to struts 2,bascially , what are the gaining points that justify > migration headache? Not talking about more cutting edge architecture, IOC, > etc .. from pure fucntionality perperctive, what I will get that I did not > had in 1.3 if I migrate to 2.0, is it more clear ajax support? Is it more > faster ? etc ...
Levan, OK, it's Friday. I waited on this one. Personally, working in a house with a S1 commercial application, and starting a new S2 application, I don't think there are a lot of justifiable reasons. It appears that S1 is going to be around for a long long long time. I seriously doubt we will see development on it cease in the next few years. Now, I'm not a S1 expert by an means, but a lot of the advantages that are present in S2, can also be had in S1. You can use Spring, IOC, plain JavaBean actions (Strecks?), and I'm sure more that I don¹t know about. I'll cover my company's situation in particular. We have a S1 application with 167 actions, comprising 61,000 lines of code. We have additional utility classes wrapped around working with S1 to go along with the 61k lines. The most important thing though is the application works! The code base is well understood, and it's highly debugged at this point. Being the guy who writes the paycheck for this I can't really think of a justifiable reason to tear apart a working application just to move it to a new web framework. If it's not broken, don't fix it. Maybe I'll change my mind if S1 dies, lacks maintenance work, stops working or some such unlikely thing. But right now I don't see it. Well, that's just my Friday $0.02(US), take care, Mark --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
