The basic idea of this approach is that your Servlets and EJBs are together in your WAR file as one app.
This is very different than J2EE or Java EE 5 as there aren't several levels of separation and classloader hierarchy. This is going to take some getting used to and it should be understood that this style of packaging isn't J2EE compliant. Who would care tough as it is a feature of Java EE 6 we would've been waiting for so long.
J2EE classloading rules:
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.