Lesson 2 | The deployment process and EJB platforms |
Objective | Describe the roles required for deployment and the J2EE reference platform |
EJB Deployment Process Platforms
Recap of roles and responsibilities
To recap, there are a number of roles that you will play in the deployment of the Hello bean you met in the previous module.
Developer Role | Responsibilities |
Bean Developer | Writes the code for the home and remote interfaces and the bean and compiles them. Creates the deployment descriptor. Packages the DD and class files in a jar file. |
Deployer | Deploys the bean on the EJB platform using the tools provided by the vendor. |
Client Programmer | Writes a client program that uses the services of the remote bean and executes it against the bean |
We will ignore the application assembler's role since we are deploying a single bean. In this module, you will perform each of the roles above.
The EJB reference implementation
The EJB platform used in this workshop is the Java 2 Enterprise Edition (J2EE) reference implementation from JavaSoft.
This implementation was designed to allow developers to develop and test beans on a platform that guarantees to implement the J2EE specification
completely and accurately. The idea is that, if a bean runs on the reference implementation, it will run in any EJB 1.1 compliant container. This
is not a platform that is suitable for production, but is great for our purposes, and it's free!
Because "J2EE reference implementation" is clumsy to write, I will refer to it as the J2EE platform in the rest of this course.
The J2EE platform also supports servlets, Java server pages, and Java messaging services. We will not use these facilities in this course.
In the next lesson, you will download and install the J2EE platform.