Michael McGrady wrote the following on 9/21/2004 9:37 AM:
What do you do with classes like DispatchAction and ImageButtonBean (which solve the same problem in different ways) when someone comes up with something better?
You need to include some flavors of DispatchAction in the core of Struts and although I don't use Tiles (I use Sitemesh) and I no longer use DynaForms of any flavor, I think there is no problem including them. Now, if you included SiteMesh as 'part' of Struts that would be dumb since it is completely stand alone, but Tiles (from what I remember, relies on Struts, but I could be wrong there).
Granted there is a fine line sometimes between bloat and necessary, but I only see major bloat when I'm 'required' to extend a bunch of classes that I don't really need.
One of the nice things about Struts is it comes with a bunch of stuff to make your job easier. You don't have to go google around to find some Dispatch implementation or even for a solution for web layout or dynamic beans. (It doesn't mean you can't go find other solutions.) Having this stuff easily available is a huge plus especially for new developers.
Under your philosophy Struts would end up being just one ActionServlet, a config file, a RequestProcessor, one Action and one ActionForm. Then you'd be on your own to find validation, web layout, dispatch, and tag solutions.
-- Rick
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
