Maybe I am just a little naive about the topic, but I just read a tutorial on webwork2 and I see absolutely no reason why webwork has to exist. Of course there are great ideas in the implementation of webwork2, but I see no reason why they can't just be added to struts. Take interceptors for example. You don't need to rewrite a whole MVC application to add interceptors. Struts could easily integrate these into its request processor, either in the core of struts or as a struts hack. In my mind, struts provides a basic framework which almost every MVC application is going to need, reading a config file to obtain a datasource, message resources, controller configuration and action mappings. Maybe the last 5% of the code on the very top of struts is under question...then it just seems we should work that last 5% to satisfy the needs of these webwork converts. Am I way off here?
Dan -- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Daniel Allen, <[EMAIL PROTECTED]> http://www.mojavelinux.com/ - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - [Frodo]: "He deserves death." [Gandalf]: "Deserves it! I daresay he does. Many that live deserve death. And some that die deserve life. Can you give it to them? Then do not be too eager to deal out death in judgement. For even the very wise cannot see all ends." - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
