Apache Terminates Struts 1
twofishy writes "Struts 1, the venerable Java MVC Web framework, has reached End Of Life status, the Apache foundation has announced. In a sense, the move simply formalises what has already happened, as the Struts team have focused their efforts on version 2; the last release of Struts 1 was version 1.3.10 in December 2008. The change of status does mean however that, whilst the code and documentation will still be available, no further security patches or bug fixes will be issued."
no, IBM Websphere does that
Does anyone use whatever this article is talking about?
No. It's terminated. RTFA
Slashdot, fix the reply notifications... You won't get away with it...
Apache is screwing over just as many people as PHP screwed over when they EOL-ed the PHP 4.4.x branch, or .Net 1.1 or 2.0 when mainstream support ended.
People can continue to use the outdated version, but it wasn't supported. It's not as if all applications ceased to operate, just that if you haven't moved on to developing Struts 2 apps by now, then you need to bite the bullet and switch.
It's just Struts 1 that is being EOLed. Given that Struts 2 was 6 years old in February, developers had plenty of time to switch to Struts 2. The current release is 2.3.12.
GLaDOS for President 2016! "Well here we are again. It's always such a pleasure." -- GLaDOS, 2011
Answer: A good start. If I never see another framework which makes you write the same thing three different times in three different ways, and claims it's making things "easier" by doing so, it'll be 15 years too late.
What transactional application framework would you use today (April 2013) for your web-scale application,
For Java, the big one these days seems to be Spring.
GLaDOS for President 2016! "Well here we are again. It's always such a pleasure." -- GLaDOS, 2011
Although Struts 2 is a complete rewrite, it's backward compatible with Struts 1.
Rubbish, it has entirely different concepts, architecture configurations and just about everything. There are migration tools, but these are far from automatic.
Developers have had years to start making the switch.
True, but many haven't because if you have a website in maintainance mode (a small number of upgrade and changes) it is hard to get approval for an upgrade if what you are using is still supported. I am actually pleased that it is now at end of life, we have been wanting to evaluate new frameworks and upgrade for ages but not given the budget.
But why would you, unless you were stuck maintaining a legacy application?
I'd rather chew razor blades than work on a Struts application again.