Oracle Kills Commercial Support For GlassFish: Was It Inevitable?
An anonymous reader writes "Oracle acquired GlassFish when it acquired Sun Microsystems, and now — like OpenSolaris and OpenOffice — the company has announced it will no longer support a commercial version of the product. Mike Milinkovich, executive director of the Eclipse Foundation. said in an interview the decision wasn't exactly a surprise: "The only company that was putting any real investment in GlassFish was Oracle," Milinkovich said. "Nobody else was really stepping up to the plate to help. If you never contributed anything to it, you can't complain when something like this happens." An update to the open source version is still planned for 2014." GlassFish is an open source application server.
What the hell is a glass fish?
The Wikipedia article is no help for someone that isn't familiar with Java appservers:
GlassFish is the reference implementation of Java EE and as such supports Enterprise JavaBeans, JPA, JavaServer Faces, JMS, RMI, JavaServer Pages, servlets, etc. This allows developers to create enterprise applications that are portable and scalable, and that integrate with legacy technologies. Optional components can also be installed for additional services.
Built on a modular kernel powered by OSGi, GlassFish runs straight on top of the Apache Felix implementation. It also runs with Equinox OSGi or Knopflerfish OSGi runtimes. HK2 abstracts the OSGi module system to provide components, which can also be viewed as services. Such services can be discovered and injected at runtime.
GlassFish is based on source code released by Sun and Oracle Corporation's TopLink persistence system. It uses a derivative of Apache Tomcat as the servlet container for serving Web content, with an added component called Grizzly which uses Java New I/O (NIO) for scalability and speed.
Why would someone choose Glassfish over Tomcat, JBoss, or one of the commercial alternatives? Can someone explain it in plain english without requiring links to a dozen different projects?
How popular is it?
I don't believe it. Right there in the summary.
For better or for worse, Glassfish has the reputation of being bloated. Tomcat has the reputation of awful developers (they disparage users on the bug tracker). And so on.
The only decent (excellent, actually) webserver I've seen is Jetty. And it's lean, to boot.
The king is dead. Long live the king!
I really, seriously don't think it's at all grammatically fair in any way to ask if something was inevitable after it already happened.
This can't possibly be related to track record?
It's CDDL licensed, as Solaris was, and the model is "managed community", the way Solaris was -- what guarantee did any contributor possibly have that Oracle wouldn't do to it exactly what they've done to the Open Source Solaris community? As in, *exactly* what they just announced?
The problem with "managed community" is that the "manager" can yank the rug out from under you at any time.
And who exactly thinks it's fun to work on Java based application server implementations anyway?
Sun drowned, and oracle was the shark that ate the carcass and after digesting the IP used its bulked up legal muscles to go after google.
Oracle has proven it would rather loot and pillage Sun's corpse than maintain it as a separate brand.
How many J2EE/EJB containers does the world really need? Certainly the world would be diminished if Oracle killed Glassfish completely because it is, after all, the reference implementation. But dropping commercial support only means that Oracle not going to support it as a commercial implementation. Keep in mind that Oracle also owns WebLogic, a more prominent and I dare say more successful competitor in this arena.
It's really quite a simple choice: Life, Death, or Los Angeles.
Here is a better answer (and it's not mine). The 0.1% figure is disingenuous. People normally don't user app servers like Glassfish as web servers. They usually serve back end web services (which doesn't really count as a web server in my book, despite the terminology used), and back end Java Enterprise services (like Enterprise Beans, and Persistence Layer objects). In my experience, while many use Tomcat for web services, it is a pain in the ass to use for any seriously large sized projects. And it is kludgey and tougher to configure unless you like playing with Apache style configuration files (meaning they are about as clear as Apache documentation). Glassfish is built with all the services required and integrated for doing most anything you need to do with an app server, no added packages needed. People who will tell you Glassfish isn't very good are also those who still think Netbeans is no good, when in fact it now eclipses Eclipse for just working without fucking around with adding plugins. And it works very well. Also Glassfish has built in facilities for horizontally scaling/high availability.
-- I ignore anonymous replies to my comments and postings.
Oracle bought some software company, provided shitty support for a couple of years, then complained no-one was using or contributing to it and then canceled support for it out of the blue leaving their customers that are using it screwed? eee gads! This has never happened before! Oh wait, that's right, this is what Oracle does with EVERYTHING THEY BUY.
All I ever used glassfish for was the Sun/Oracle IDM services. It was "different"
Actually, that raises the question why was it being put out there as open source in the first place? If you're only putting out an open source product _because_ you expect others to contribute, then your priorities are fucked up.
You should put it out there because it might be genuinely useful to others. Don't pollute the open source world with half baked tools that will bitrot and cause people who search for genuine free alternatives to get confused. That actually causes damage by fracturing the communities around the problem domain.
Seems not real...
yes, it absolutely was inevitable. no program or product lasts forever, everything dies.
Anons need not reply. Questions end with a question mark.
Glassfish, that name must have been generated using a startup product name generator:
Feed it a real list of adjectives and critters and you'll be in hog heaven - ehh, sorry, HogHeaven - for years, sprouting startups left and right. Maybe I should post this on HN instead...
--frank[at]unternet.org
I'll use whatever server is bundled with OEPE. I just need one for development and debugging; I'm not interested in the intricate details of different servers. In theory they all use the same APIs, so why should I care what is used for deployment?
I do not fail; I succeed at finding out what does not work.
I shat myself laughing!
It was also created to boost chip and disk sales, too.
And frameworks. Don't forget frameworks.
Get thee glass eyes, and, like a scurvy politician, seem to see things thou dost not.--King Lear
I shit on Oracle
Oracle is in the software business. Glassfish support takes resources away from WebLogic.
Despite supporting OSS back in the 90s when MSFT ruled, Larry's grumblings about OSS recently are hints as to where Oracle is going with this.
Large clients with unlimited funds are using OSS solutions on a large scale.
This (and support/consulting services) are where all proprietary software companies will aim for growth, and they will do and say what they have to in order to drive the business model.
They have no choice.
This, and confusion about licensing is why MariaDb has replaced MySQL in recent distro releases like Slackware 14.1
Remember SCO and the boatload of lawyers? Get ready for a repeat.
No. It was both foreseeable and unavoidable, knowing Oracle's true nature.
Religous speak to God. Insane are spoken to by God. When all shut up, one can finally hear Shostakovich in peace
The engineers and tech didn't kill Sun, bad Management and cheap Intel Linux boxes did. Sun should have dropped their hardware division sooner. Why buy 1 $100,000 Sun box when I can buy 5 $2,000 Intel boxes for the same.
:(. Also low TCO doesn't really help when you can't get enough credit to buy what you need up front. That's why Amazon web services is so popular even though the cost for CPU time is nuts.
Cheap labor didn't help them either. Sun boxes were a breeze to admin compared to Linux, but when wages for high level IT plummeted in the wake of off-shoring and outsourcing saving 20% on your admin's time wasn't worth as much. Heck, he was probably salaried so you could work him as many hours as you needed too
Hindsight's 20/20 and I think we can all think of 20 things Sun coulda done to stay relevant though. But what it came down to is the Management didn't react to changing times.
Hi! I make Firefox Plug-ins. Check 'em out @ https://addons.mozilla.org/en-US/firefox/addon/youtube-mp3-podcaster/
I've seen plenty of bad Java code, but then again I've seen plenty of bad non-Java code.
It's not Java's fault that people are using it wrong. It's easy to do the right thing with Java, but it's also quite easy to do the wrong thing and get SOMETHING kinda working. In a way that can be a curse. Bad C/C++ apps will crash and burn immediately quite often, thus forcing people to fix things. Bad Java apps will creep along and be somewhat usable.
On the other hand, you can get something working quicker with Java, and you can get reasonably good results with good design and supervision and a team of mediocre developers. So Java software is quite cost-effective.
--Coder
So for Oracle ruining Java would not make any financial sense, neither short term nor long term. If they have at least 2 brain cells working, they will not do it. Although big companies do not always act rationally.
--Coder
I'm confused by your comment. Why wouldn't Oracle or any company do whatever they want with a company they just purchased?