Artifact: J2EE Application
|
| A J2EE Application is an Implementation Element at a very large level of granularity. It is the largest deployable element directly supported by the J2EE Platform. |
|---|---|
| Other Relationships: |
Part Of Implementation Model
Extends: Implementation Element |
| Role: | Integrator |
| Optionality: | Optional. J2EE applications may be deployed as a set of standalone J2EE Modules. |
| Templates and Reports: |
|
| Examples: |
|
| UML Representation: | Artifact, with the stereotype <<EAR>> |
| More Information: |
|
|
|
| Input to Activities: | Output from Activities:
|
Purpose
The J2EE Application is the largest deployable element directly supported by the J2EE Platform. It contains one or more J2EE Modules.
Timing
A J2EE Application might be created in the Elaboration Phase as the architectural
prototypes are developed. The J2EE Application is updated during the Construction
and Transition Phases as J2EE components are developed and defects are found
and fixed.
Responsibility
The Integrator is responsible for the J2EE Application, and ensures that:
- J2EE Application implements the corresponding design correctly, and fulfills the design specifications.
- The J2EE Modules are consistent with each other, including deployment descriptors.
- The application deployment descriptor is correct and consistent.
- The application has been correctly packaged for deployment.
Tailoring
J2EE Applications are packaged into an Enterprise ARchive (EAR) file, and have an application.xml deployment descriptor that allows the modules and the application as a whole to be customized. However, stand-alone J2EE Modules can also be deployed directly, rather than assembling them into J2EE Application.
