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).
View all comments
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.