My team implemented Struts without bothering to ask, too. It's worked out great with the exception of upgrading from 1.0 to 1.1 - that was a PITA! But there's really no reason a CIO should be concerned with such implementation details. It's open-source and it's Java, so there is no maintenance issue other than wanting to keep up with the latest release (and that's not necessary - there are many projects out there using 1.0). If you don't like the code, change it. Nevertheless, the real beauty of Struts is standardization of an MVC framework that permits others coming after you who have experience with Struts to quick ascertain the program flow of your app and cut resource committal costs. And then there's this wonderful list!
Mark -----Original Message----- From: Chappell, Simon P [mailto:Simon.Chappell@;landsend.com] Sent: Friday, November 01, 2002 9:05 AM Can't help you. I just started using it and said sorry alot when they discovered what I'd done. I'm at the top of the technical track here and I don't want to be a manager, so it wasn't going to hurt my promotion chances! :-) And the system is working very well and the users are happy! :-) Simon >-----Original Message----- >From: Jeff Born [mailto:jborn@;gr.com] >Sent: Friday, November 01, 2002 8:03 AM > >Can anyone point me at an article that explains at an >executive level why to use struts? -- To unsubscribe, e-mail: <mailto:struts-user-unsubscribe@;jakarta.apache.org> For additional commands, e-mail: <mailto:struts-user-help@;jakarta.apache.org>
