Deploying applications in TomEE is as simple as deploying them in Tomcat.
You could deploy your application in Eclipse just like how you would deploy with Tomcat. For an example, tomee-and-eclipse shows how to use TomEE with Eclipse.
Or you can simply package your application as a standard WAR file and copy it to the [TomEE]/webapps folder, or as an EAR file and copy it to the [TomEE]/apps folder.
Read on to learn more about packaging EJBs in a WAR file.
The basic idea of this approach is that your Servlets and EJBs are together in your WAR file as one application.
This is very different than J2EE or Java EE 5 as there are not several levels of separation and classloader hierarchy any more.
This may take some getting used to and it is important to understand that this style of packaging is not J2EE compliant.
You should not worry though, as it is an accepted feature of Java EE 6.
To pull that off, J2EE has to kill you on packaging:
Critically speaking, forcing more than one classloader on an application is where J2EE "jumps the shark" for a large majority of people's needs.
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.