We had a 30-day prototype to get up and running and chose Struts for the framework. There were 3 team members, none of whom had ever used Struts before. We chose it because of how much we had heard about ease of use, etc from other peers. We made our deadline and the interface included about 20 jsp pages 15 action classes, 10 forms and a couple of servlets with a database interface. Its not an overly complex application but my point is we had no problem getting up to speed by walking through the example and taking advantage of the helpful folks on the user's list. Another component that we have recently incorporated (Which has really decreased the code in the classes) is the basic validation stuff. Very easy to use and understand and has cut my code down significantly.
One other point I want to make is the customer decided after delivery they did not like the look and feel, well by using the struts, we were able to change the look and feel within a day (and I mean it changed 180 degrees), without impacting and of the business logic. Peggy -----Original Message----- From: neal [mailto:[EMAIL PROTECTED]] Sent: Sunday, August 18, 2002 5:40 PM To: Struts Users Mailing List Subject: when to use Struts I am new to struts and am attempting to get my around how valuable it would be me. >From what I gather, it's primary asset is the action servlet which makes for a nice seperation between the view and the control. I also understand that if provides some useful tools such as a connectionPool for JDBC, and some XML parsing tools. Aside from these things, what makes Struts useful? I guess what I am ultimatley wondering is if the time saved by using Struts will be eaten up by the time it takes me to learn Struts, enough to use it? Any thoughts/comments would be appreciated. Thanks. Neal -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]> -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
