Development Roles
Development Roles
resources to the server's resources, and Application Server implementation-specific parameters,
such as caching directives. The Application Server runtime deployment descriptors are named
sun-
one component deployment descriptor of that type. An enterprise bean module deployment
descriptor, for example, declares transaction attributes and security authorizations for an
enterprise bean. A Java EE module without an application deployment descriptor can be
deployed as a stand-alone module.
descriptor. EJB modules are packaged as JAR files with a .jar extension.
HTML files, and a web application deployment descriptor. Web modules are packaged as
JAR files with a .war (Web ARchive) extension.
descriptor. Application client modules are packaged as JAR files with a .jar extension.
other documentation, along with the resource adapter deployment descriptor. Together,
these implement the Connector architecture (see
process into distinct roles so that different people or companies can perform different parts of
the process.
software is purchased and installed, Java EE components can be developed by application
component providers, assembled by application assemblers, and deployed by application
deployers. In a large organization, each of these roles might be executed by different individuals
or teams. This division of labor works because each of the earlier roles outputs a portable file
that is the input for a subsequent role. For example, in the application component development
phase, an enterprise bean software developer delivers EJB JAR files. In the application assembly
role, another developer combines these EJB JAR files into a Java EE application and saves it in
an EAR file. In the application deployment role, a system administrator at the customer site uses
the EAR file to install the Java EE application into a Java EE server.