Apache TomEE, pronounced "Tommy", is an all-Apache Java EE 6 Web Profile certified stack where Apache Tomcat is top dog. Apache TomEE is assembled from a vanilla Apache Tomcat zip file. We start with Apache Tomcat, add our jars and zip up the rest. The result is Tomcat with added EE features - TomEE.
The Web Profile version of TomEE contains
The TomEE Plus distribution adds the following:
Simple, Get more from Tomcat without giving anything up.
Some core focuses guide the integration:
The desire to beef up Tomcat installations has persisted despite the existence of full-blown app servers, many of which include Tomcat in some truncated and stripped-down form. Not TomEE.
Apache TomEE is assembled from a vanilla Apache Tomcat zip file. No picking and choosing individual parts of Tomcat and building a "new" server leveraging Tomcat. We start with Tomcat, add our jars and zip up the rest. The result is Tomcat with added EE features, TomEE.
Tomcat provides plenty of hooks for filling out parts of its lifecycle. We leverage them all to fill the gaps. The result is a whole lotta sharing!
Servlets now get access to JPA and Transactions, EJBs get access to Tomcat provided Security. Any Tomcat provided resources, say from a context.xml, can be looked up or injected by any managed component in the system.
There's a definite "less is more" philosophy in Apache TomEE. It's too easy to go too far when developing an app server. The result is usually a slow to start, memory hogging, beast. We're not here to create an ultra flexible, super powerful, infinitely composable, be anything to anyone platform. We're here to deliver Java EE 6 Web Profile in the simplest way possible.
If you were to imagine taking a plain Tomcat install and integrating the missing components in the most direct and to-the-point style possible, you'd end up with TomEE. The result speaks for itself:
In Apache TomEE's previous life, it was simply known as the OpenEJB+Tomcat integration. That description was always quite misleading. For one, there's incredible benefit even if EJB is never used.
Quite simply, EJB as a technology integrates with the most number of specs than any other spec. It touches JMS, Web Services, Connectors, Servlets (EJB Web Services are still driven by Servlets!), JPA, JDBC, Transactions, Security. Integrating with all these technologies takes time and expertise and in the end has very little to do with EJB specifically. To apply this all to Tomcat and leverage it all from a simple Servlet is a natural extension and the reason most app servers started out as EJB servers.
Whereas most app servers pluck Tomcat out of its environment, Apache OpenEJB has always existed as an embeddable container focused on being as tiny and invisible as possible. The natural extension of this is to embed the "EE" into Tomcat, rather than the other way around.
But in the end, it is not about EJB. It's about the other guys: ActiveMQ, CXF, MyFaces, OpenJPA, OpenWebBeans, and of course Tomcat! So out with OpenEJB+Tomcat and in with Apache TomEE!
All edits are reviewed before going live, so feel free to do much more than fix typos or links. If you see a page that could benefit from an entire rewrite, we'd be thrilled to review it. Don't be surprised if we like it so much we ask you for help with other pages :)NOTICE: unless indicated otherwise on the pages in question, all editable content available from apache.org is presumed to be licensed under the Apache License (AL) version 2.0 and hence all submissions to apache.org treated as formal Contributions under the license terms.