Slashdot Mirror
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."
I like to get my knitting done whilst watching the telly.
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...
Maybe not much recently, but a few years ago it was very popular. Out of the 104 resumes I have for open Java positions, 47 of them have the word struts on their resume. Apache is screwing over quite a few people with this decision to drop a popular framework.
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.
Yes. It wasn't always terminated.
In that case why don't you just look it up? That's what I do nearly each time I encounter something new. And I do learn something that way... If it's worthy enough to bitch about it's certainly worthy enough to look it up, right?
Perl Programmer for hire
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.
... Struts is the most appaling MVC framework for web applications ever invented. It is a poor abstraction of the underlying servlet mechanism, it requires a hideously complicated configuration file and the original logic tags were some of the worst ever invented.
Struts 2 is of course polishing a turd.
Struts is open source software that any java developer can fix bugs for themselves. As far as I know, two big companies in my city are using Struts 1 since 10 years ago. They never had a chance to migrate to version 2 because too many code to convert.
life is short, learn more.
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
What the heck are you talking about? Struts 2.3.12 was released some weeks ago, and they are about to release Struts 2.3.14
I'm glad. Struts 1 wasn't such a good framework. It was first framework a lot of Java developers used these days, and one of the first frameworks available, and back then there wasn't that much choice. But today we have much more and much better ones. If you are still using Struts 1 in this day and age, you're doing something wrong... Even for legacy systems, there was plenty of time to refactor.
--Coder
You don't know the TLA MVC is? And you ate reading /. Seriously? I'd be too embarrassed to admit such a thing. The thing about journalistic courtesy is it works by ascertaining who your audience is - in this case technical people - and writing to them. As a result you might reasonably assume knowledge of a few basic acronyms - RAM, ROM, MVC, CPU and so on - and not bother to spell them out.
Honestly it doesn't make that much difference these days. Spring and Java EE are both good choices. Java EE needs an app server but there are plenty of free options including Glassfish which is the reference implementation. I'd tend to choose Java EE over Spring because it is easier to "grow" as you need to in my opinion, and I don't think the learning curve is any bigger really. Plus the fact that it is backed by the major vendors means that if you need to tie into a banks MQ Series/CICS/whatever back-end it is that much easier to do. There is pretty much nothing you need to do in enterprise software that Java EE doesn't handle reasonably well with the possible exception of HFT - even in low latency environments Java is a pretty decent choice. 10 years ago I'd have gone the other way mainly because Spring was just so much simpler. These days Spring has got really kind of complex, the two more-or-less have feature parity, and Java EE has got simper, and they've kind of met in the middle. One downside of Java EE is the standard web framework - JSF. Whilst it has its uses for the most part there are simpler options for a "typical" architecture - JSON over REST being presented via JQuery. Spring MVC is a good choice, as is Struts 2.
One downside of Java EE is the standard web framework - JSF. Whilst it has its uses for the most part there are simpler options for a "typical" architecture - JSON over REST being presented via JQuery. Spring MVC is a good choice, as is Struts 2.
A restful back end driven by an html/js/ajax client is my favorite architecture as well, however if you want to do a server-generated dhtml style application, I would suggest you have a look at Stripes - It's everything that Struts should be (and isn't).
Apache Wicket for the web UI (bye bye JSPs), and Spring (or Guice) for DI, beans, etc.
Does Struts catapult Java from a terrible server side language to a disastrous framework?
I'm just asking... Java is far too shitty for me so I don't really know.
No, it only goes part way. For that you need Struts 2
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.
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.
And they will never get approval unless the product goes to EOL. Above this, the longer it takes to lose support, the less likely there will be somebody who knows the system in case and the more work an update will take.
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.
Have you seen Maven? Whoever got the idea that quality documentation could be automatically generated deserves a punishment beating.
In that case why don't you just look it up? That's what I do nearly each time I encounter something new.
Technology from 1970's isn't "new" anymore.
Ezekiel 23:20
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.
I suppose that "web-scale" means "size of the .war files" in this context?
Ezekiel 23:20
Struts 2 is far worse. I've personally not seen it adopted anywhere. If the choice is to move away from Struts 1, it will generally be to SpringMVC or something similar, or that general horror known as JSF. Struts 2 was so bad, it doesn't even get a second look from anyone I know. Even Tapestry was better.
That aside, nice troll. Guess you run with that rock solid Ruby, or maybe that super efficient and secure PHP?
The cesspool just got a check and balance.
If any of my clients using Struts 1 are going to drop it, they won't be going to Struts 2. None have in the past either, and Struts 2 isn't even mentioned in the current group.
The cesspool just got a check and balance.
Your comment is 10 years or more out of date.
If you're HIPAA/HITECH or SOX regulated and you're running EOL'd software, don't expect to pass your next audit.
And if your plan is to lie to the auditors, well, be aware that the CEO is unlikely to be the one who goes to jail - it's more likely to be you, regardless of what your boss might tell you now.
"New" as in "new to me", of course.
Perl Programmer for hire
So just how is Apache "screwing over" people on this one? They have a new version of Struts available and focusing on that. They don't have unlimited resources so they have to decide what is supported with bug fixes versus what is not.
Speaking of trolls. In any case, defend your statement. There's *nothing* in S2 that's worse than S1. It's pretty similar to Spring MVC in functionality. I have no idea how you could come to the conclusion that S1 is better.
Nonsense.
S1 hasn't seen an update in quite some time--nobody is maintaining it. Making it official changes nothing on the ground.
No S1 resources are going away, and people will still answer questions about it on the mailing list and SO, just like now, even though nobody should be using it for anything other than legacy support.
having knowledge of more than 20 companies that all used Struts at one time, some still do, I'd say that 0 percent adoption is telling. Several went JSF, others started using SpringMVC. Anecdotal, I know, but in my entire circle of people I know, not a single one has used Struts 2 beyond a distasteful POC, provided they got past the initial documentation.
Follow that with your own comment - it may not be worse, but it's not better. And that was enough to arrive DOA for many.
The cesspool just got a check and balance.