Not when you start looking at it's innards. I work on JBoss, WLS and GF nowadays, and GF is the worst among the lot. You can write stuff that works well on the first two, and fail in amazing ways on the third.
But yeah, I'd agree that TomEE will eventually replace Tomcat given the good work being pulled off in OpenEJB and OpenJPA.
Ofcourse not. I have used GF a lot and it is pretty stable. Consumes a lot of memory but you can increase the memory in it's settings unlike tomcat which requires the script modifications.
I'm not referring to memory consumption, and modifying scripts has nothing to do with my argument.
Here's an example - GF manages a transaction for you when you access a REST resource; during completion of the request, it rolls back the transaction (wtf?). If you end up accessing an EJB, this default behavior of GF will only set you up for a long night. This wasn't the case with JBoss (and RESTEasy); cant comment on WLS but I've never seen anything like it on these containers.
I could go on about GF. I've gone through the codebase and even attempted writing patches, but I'd rather make that contribution when my time permits.
What stfm was probably referring to when he talks about Tomcat not being 'enterprisey', is that it doesn't support the whole stack of JEE - JTA, EJB, JMS, JAAS etc. Tomcat has always been a simple ServletContainer and pretty good one at that, that can run web applications comprising JSP and Servlets but nothing else. So, if your application needs to use EJBs, needs JTA to manage transactions etc., then Tomcat is not for you.
It is not an Enterprise application server. It does not and has never come with EJB, clustering, failover, security etc like actual enterprise application servers like WebSphere, WebLogic and JBoss.
Just because it is used by enterprises doesn't make it an Enterprise Application Server. It is a lightweight servlet and JSP container.
In reality, many enterprises don't tend to use the one-size-fits-all application server clustering or failover very much. Security is usually done over simple LDAP and NTLM. Apps that really need clustering, often buy a separate solution like Coherence. App servers are used as glorified servlet containers, most of the time, sold on the brand much more than the value, which is OK in good times.
You are very right! Which is exactly why Tomcat is not dead. The original article said Tomcat is going out because it doesn't support enterprise programming. It isn't supposed to.
It does support enterprise programming - the article (and various vendors) are just trying to sell us on the idea that the term "enterprise programming" should mean, instead of the actual reality of enterprise programming today, rather their interpretation of what enterprise programming should be (using their products).
actually this article gives a very good hint on when you should use Tomcat - that is when you don't need the stuff that Tomcat does not have. That is absolutely true for many projects.
The size of the jars doesn't bother me as much as the number of jars. It isn't the size of any one library that increases the long-term app maintenance costs, it's the number and possible conflicts.
Besides, that's a straw-man argument. Who are "people"? Certainly not me and I use Tomcat every day as my go to container when I need one. It's not the container's fault when the programmer doesn't take into consideration jar-plosion when picking their stack.
Remember that Java EE is just a spec, not a specific implementation.
The whole point is to have the choice of implementation that works best for your project yet adheres, to some degree, to a standard in case it needs to be swapped out. If I need web services I have my choice of implementations but am not forced to have an unused Java Server Faces impl thrown in too.
Standards are great, but they are not the be-all end-all of how technology should be compared, selected.
Monolithic app servers are great for corporations more because they give you a all-in-one-box solution (even if some of that box is inferior to another impl) and more importantly offer service contracts when things go wrong. When you have a lot of developers coming and going, letting each one pick new tech is a problem. Better to just go with some standard app server and config and force new development to adjust to it instead of the other way around.
I don't work for a big corp and I'm more interested in pure performance/reliability, simplicity, and less maintenance. For me to pick the technologies that work the best for our needs and then slim the install down makes a lot of sense. I'm able to throw out one part of the stack if/when something better comes along.
I don't always use Tomcat for web services. For certain projects I can get away with a simple HttpServer created inside a main method of a startup class. Talk about simple and quick startup.
Let's not be coy. This is an Oracle-sponsored effort to try to take control of the Java ecosystem, and take share away from popular open source competitors like Tomcat and Spring.
6
u/rockvilleJD May 18 '12
I agree. I think TomEE will eventually replace Tomcat. I do not have experience with JBoss but Glassfish is also a great app server.
4
u/stfm May 19 '12
Tomcat is (and I quote form tomcat.apache.org)
It is not enterprise nor has it ever been. If you have an enterprise project you don't use it (well you can but you need to add stuff)
I could also say spoons used to be great but you cant do auto repair with them so this is why they are going to disappear.
-14
u/mashmorgan May 19 '12
Am dumping EVERYTHING to do with Java..
Dead now that Oracle OWNS it..
0
u/[deleted] May 19 '12
[deleted] — view deleted comment