Apache TomEE, pronounced "Tommy", is an all-Apache stack aimed at Java EE 6 Web Profile certification certified stack where Tomcat is top dog. Apache TomEE is assembled from a vanilla Apache Tomcat zip file.
Overview
...
Connector
...
We start with Tomcat, add our jars and zip up the rest. The result is Tomcat with added EE features - TomEE.
| Info |
|---|
You can now have Dependency Injection, Configurable Transactions and Security and much much more, coupled with blazingly fast develop-deploy-test cycles!! |
Goal
Get more from Tomcat without giving anything up.
Technology Stack
Following is the technology stack supported in TomEE:
| Div | ||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
...
Apache TomEE PlusTomEE Plus adds support for the following, over and above TomEE
|
Goal
Simple, Get more from Tomcat without giving anything up.
Focuses
Some core focuses guide the integration:
- Don't mess with Tomcat
- Keep it simple
- Avoid architecture overhead
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.
Under the Covers
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.
| Div | ||
|---|---|---|
| ||
The philosophy - Keep it Tight, Keep it Simple
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.
- make the developers life easier
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:
- Runs without any additional memory requirements
- Compatible with
...
- Tomcat-aware tools
- Compatible with Tomcat-tested apps
Focuses
Some core focuses guide the integration:
- Don't mess with Tomcat
- Keep it simple
- Avoid architecture overhead
- Allow users to get the job done
History
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.
...