I am not sure that is true. Struts seems to lack of an API. IMO, there are more required configurations than necessary. Take Action for example, to write an Action, one has to paddle back and forth between the code and the configuration. It is like an executable having to configure each of its dlls. The visibility of the mappings is nice to have but the mappings can be generated after the fact as in a debugging view. When the application is finished, configurations become static. But since configurations are required, they will be like loose ends of the application. Another issue: how can one componentize his code and deploy it in a self-contained plug-in, as with Eclipse? Please forgive my novice.
- Robert. ----- Original Message ----- From: "Rick Hightower" <[EMAIL PROTECTED]> To: "'Struts Developers List'" <[EMAIL PROTECTED]> Sent: Wednesday, December 03, 2003 6:24 PM Subject: RE: Disadvantages of Struts? > Don't be silly. Struts is perfect. > > -----Original Message----- > From: Robert H. Tran [mailto:[EMAIL PROTECTED] > Sent: Wednesday, December 03, 2003 2:10 PM > To: Struts Developers List > Subject: Disadvantages of Struts? > > I just wonder if Struts comes with any significant drawback. I mean not in > terms of when to use Struts and when not to use it necessarily, but more in > the line of anyone's wishes that it had been better. Any advice is very > appreciated. > > - Robert. > > --------------------------------------------------------------------- > 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] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
