Ted- You're exactly right about not being able to turn on a dime. At my current client, the team I work with has been doing struts for about 1 1/2 years and have made an investment in tools and training. It would be difficult (aka "politicial suicide") for someone to suggest turning the ship around and use a different web framework without being able to guarantee productivity gains, etc., whatever framework it is. (Oddly enough, that seems to be ignored when organizations decide to go with .Net, but I digress...) And, once that is done, all the Struts Classic systems become "legacy", and some developer(s) will need to know the old and the new too. Not that these tradeoffs are anything new, though. Also, I don't think it's going out on a limb to say that there are currently far more Struts developers than JSF too, although that will probably change going forward.
It's a great way you/McConnel put it about how people code "into" Struts too. From what I've seen, new developers don't see problems with putting all the business logic in the Action classes. It's only when they need to maintain the code or call it from different places that they realize the error in it, so it takes a couple of applications before people truly understand why it's a bad idea. Hmm, this wasn't intended to be a rant, sorry if it reads like one, just a "view from the trenches." -ed On 8/9/05, Ted Husted <[EMAIL PROTECTED]> wrote: > 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]
