On 8/8/05, James Mitchell <[EMAIL PROTECTED]> wrote: > Very well said Ted. I was initially opposed to moving Struts over to Maven > (way back when) more out of the frustration of having to learn another tool. > While there is not (and probably never will be) a standard for build tools, > with enough time and trial, the payoff for using Maven became *very* clear > to me. And I quickly became a convert (almost an evangelist;). And, funny > enough, I think the same is happening with my view on JSF ;) although slowed > by work commitments of course.....who knows, maybe one day I'll say "Struts > is old school", but right now, it is blazing hot!!
I'd definately agree it's the same pattern. And, if it were as easy to migrate an enterprise web application as it is to migrate a build system, I'd be encouraging everyone to switch to JSF, so that we can work together to make it a truly great platform. But, the teams I've worked with can't turn on a dime. A lot of people now have years of work invested in Struts Classic applications. As far as I know, the migration path from Struts to Shale is not lined with gold. My own hope for Struts 1.3.x and beyond is that people will begin to see CoR as a great way to provide the missing link between business logic and the presentation layer. If we can get people to do less in Struts Actions, and more in Commons Commands, it will become much easier for teams to migrate to newer platforms, like Shale, in the future. The promise of a MVC architecture has always been to cleanly separate the application from the presentation, but so many people still seem to be developing ~with~ Struts rather than *into* Struts (to use Steve McConnell's terms). -Ted. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
