Apache TomEE 1.0 Released

| by Bienvenido David Follow 1 Followers on May 08, 2012. Estimated reading time: 1 minute |

The Apache Software Foundation has released Apache TomEE 1.0. Apache TomEE, pronounced "Tommy", is a Java EE 6 Web Profile certified all-Apache stack available under the Apache 2.0 license. TomEE is composed of Tomcat (Servlet, JSP, JSTL), OpenWebBeans (CDI), OpenEJB (EJB), OpenJPA (JPA), MyFaces (JSF), Geronimo Transaction (JTA), Geronimo JavaMail (Javamail) and Apache Bean Validation (Bean Validation). There is also TomEE+, a TomEE distribution that adds Apache CXF (JAX-RS, JAX-WS), ActiveMQ (JMS) and Geronimo Connector (Connector). Apache TomEE is a sub-project of Apache OpenEJB and supersedes what is known as the OpenEJB + Tomcat integration. Apache TomEE 1.0 is based on Apache Tomcat 7.0.27, the latest version of Tomcat with WebSocket support.

Apache TomEE 1.0 has improved startup times for large applications over earlier versions. This was achieved through reduced classloading, and enhanced annotation and TLD file scanning. Tuning was focused on large applications like Confluence, Ralio, and Lift, which resulted in 369%, 128% and 166% faster startup times, respectively. Server startup time has also improved. On a modern MacBookPro, startup time should be ~1200ms from the command line or ~700ms from within Eclipse.

Other new features include the ability to pinpoint which classes and JARs should be scanned via the scan.xml file. There is also now a remote adapter for Arquillian. Shipped in a separate zip file is an experimental new feature for provisioning applications using online Maven repositories.

Apache TomEE is assembled from the standard Apache Tomcat distribution. The extra JAR files, configurations files and the TomEE webapp are then added and repackaged. This Tomcat with EE distribution runs without any additional memory requirements and is compatible with existing Tomcat web applications and tools. There is also a more detailed comparison of the Tomcat and TomEE distributions.

For more information, please visit the official Apache TomEE website. To get started, watch the TomEE Getting Started video on YouTube, and then download TomEE 1.0 from Apache website.

Rate this Article

Adoption Stage

Hello stranger!

You need to Register an InfoQ account or or login to post comments. But there's so much more behind being registered.

Get the most out of the InfoQ experience.

Tell us what you think

Allowed html: a,b,br,blockquote,i,li,pre,u,ul,p

Email me replies to any of my messages in this thread

Apache TomEE by Naresh Chintalcheru

Probably this is what we are looking for ..........

Congratulations To the TomEE Team by Chris Alexander

Like Naresh said, this is something Java developers have desired probably for over 10 years. The Apache Foundation and the TomEE team should be congratulated for this accomplishment. An accomplishment that will go down as one of the best project integrations in OSS history.

Lightweight Java WebStack is Hot... by Gurkan Erdogdu

Congratulations to TomEE.

You can also checkout Siwpas, Simple Web Profile Application Server stack from MechSoft. Nearly one year ago Infoq published article about it,

Re: Apache TomEE by Shi Kafune

For EJB 's I would probably use Jboss or glassfish as they are very stable.

What does tomcatEE provide that jboss/glassfish does not?

Re: Apache TomEE by David Blevins

The EJB support in TomEE is OpenEJB which is also used by Geronimo and WebSphere CE. It's very mature.

If you love Tomcat, TomEE is for you. It is Tomcat. Aside from that TomEE is very light. Several users have reported TomEE being the only option for very small VMs with low memory.

If you have benchmarks setup for any of your existing applications, try one out in TomEE. You might be very surprised.

Re: Apache TomEE by Cameron Purdy

For EJB 's I would probably use Jboss or glassfish as they are very stable.

What does tomcatEE provide that jboss/glassfish does not?

First of all, congratulations on the TomEE release!

Regarding Glassfish, it provides Web Profile support by leveraging the modular OSGi-based infrastructure that the application server is built on. Thus the TomEE solution is similar in result, but architecturally different.


Cameron Purdy | Oracle

Caucho Resin, Open Source, Java EE Web Profile certified last 1 year ago by Richard Hightower

I've been using Resin off and on for over 10 years. Resin predates Tomcat, and had Java EE Web profile support one year ago.
It get's used by some of the highest traffic sites on the web. It is fast and lightweight.

Caucho Resin ...certified a compliant implementation of the EE 6 Web Profile, starting with version 4.0.17.

Resin according to NetCraft is used on quite a bit of the worlds busiest sites.

"Resin, the web server and Java application server from Caucho Technology, is getting some media attention at the moment, with both Netcraft and Gartner talking about the product. Caucho has been in business for more than 14 years, and has built up a relatively large install base for Resin including Bebo, CNET, Motorola, and Openwave."

Caucho's Resin Application Server Grew by a Factor of Almost Ten Last Year According to Netcraft.

"The Resin application server has been experiencing strong growth over the past 12 months; seeing an almost tenfold growth from 480k hostnames in February 2011 to 4.7M or 0.77% of the market in February 2012."

"Caucho ... claims for Resin's performance, stating that Quercus, their ... PHP engine, is faster than standard PHP, and that the web server is faster than Apache httpd (and more similar to NginX)".

"Resin's core networking library is written in highly optimized C. Java is the OOP layer that allows Resin to be full featured. C is what allows Resin to be fast. On top of this layer we build our distributed caching, clustering, session replication, servlet engine, etc."

Good job TomEE team! This rocks. by Richard Hightower

I hope this will further promotes the use of Java EE 6, and standard Java Dependency Injection. CDI (Java Dependency Injection) and EJB light work well, and you can use them without shipping a 20MB war file. You can even easily do method interception (AOP style) with Java Dependency Injection.

The Apache TomEE mission statement by David Blevins

Thanks for the congratulations, all!

An explicit note to readers just in case there is any misunderstanding. We didn't create TomEE because we thought the existing choices were bad.

We created TomEE because despite the existence of really awesome choices, people are still trying to turn Tomcat into a Java EE server. We want to give people what their actions have been telling us they wanted, Tomcat as a Java EE server.

We want to reach a hand out and help them into Java EE and in doing so, heal a bit of a rift that has persisted for over 10 years now.

We're all about strengthening Java EE by taking one of the most popular stacks and certifying, bringing it and its users into the Java EE space.

Re: The Apache TomEE mission statement by Mark Little

Congratulations and welcome to the fold!

Congratulations by JayaMurugan Sivaraj

Congratulations to TomEE team.

Most of the time we build the server Stack with Tomcat as base. Now this is a great step and I'm sure this will definitely gain popularity. This will enable to build strong JEE compliant private cloud infrastructure.


Allowed html: a,b,br,blockquote,i,li,pre,u,ul,p

Email me replies to any of my messages in this thread

Allowed html: a,b,br,blockquote,i,li,pre,u,ul,p

Email me replies to any of my messages in this thread

11 Discuss