Call me silly, but I use my brain to figure out what to use.
I think Struts-devs said they are writing something new, once the new thing is established... then someone can say that in relation to the new release, 1.3.1 is an older release, and that's all.
It's good to separate MVC, mostly people chose the easier way. No one got fired for choosing Struts. Hey... look at PHP apps, they don't use anything modern or MVC. It just works. JEE v5 app servers are not even ready for something new. What's wrong for having an app in production for 10 years. (and when new happens, it will be client side UI - an that will be disruptive).
Focusing on technology on a project will fail; focusing on business requirements is better. That is the only choice to make.
.V
Well, if the Struts developers themselves are saying that Struts 1.x is technically obsolete and is not going to be the focus of further development effort, AFAICS, it is silly not to just take this at face value.
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
