What are the roles defined by J2EE?

What are the roles defined by J2EE?

What are the roles defined by J2EE?

    Requires Free Membership to View

    Login

    When you register, you'll begin receiving targeted emails from my team of award-winning writers. Our goal is to keep you informed on recent service-oriented architecture (SOA) and SOA-related topics such as integration, governance, Web services, Cloud and more.

    Hannah Smalltree, Editorial Director

    By submitting your registration information to SearchSOA.com you agree to receive email communications from TechTarget and TechTarget partners. We encourage you to read our Privacy Policy which contains important disclosures about how we collect and use your registration and other information. If you reside outside of the United States, by submitting this registration information you consent to having your personal data transferred to and processed in the United States. Your use of SearchSOA.com is governed by our Terms of Use. You may contact us at webmaster@TechTarget.com.

Provider - Responsible for providing the containers, and APIs defined by the J2EE specification.

Application Component Provider - Responsible for creating J2EE application components. These include: HTML documents, JSP pages, servlets, EJBs, etc.

Application Assembler - Responsible for combining J2EE components together to make a J2EE application. This usually involves packaging them into WAR files or an EAR file and deploying them.

Deployer - Responsible for installing and configuring a J2EE application in a particular application server or J2EE container environment.


This was first published in March 2002

Back to top