In this chapter, we introduced the forms in which enterprise applications are packaged for deployment into an application server. Concentrating on the packaging of EJB Tier code, we described how this code is often packaged into EJB JAR files to aid the transfer of the multiple files required by the deployment module. We also described the contents of an EJB deployment module including the location for EJB code content and the required deployment descriptor named ejb-jar.xml. Furthermore, we discussed the use of application server-specific deployment descriptors that are required by many application servers to provide them with additional information about the components being deployed.
Deployed EJBs need to be accessed by a client that often exists within a different environment. In such instances, the client needs to have a copy of the interface types for each of the EJBs they intend to invoke. We described how Eclipse simplifies the provision of this EJB client library, and we created a client to invoke methods from the TroubleTicket project, which we have presented in preceding chapters.
Finally, we examined the creation of EAR files as deployable modules that often contain the Web-Tier and EJB-Tier elements that make up an enterprise application. We examined the packaging of such a file as well as the application.xml deployment descriptor that it requires.
Unable to display preview. Download preview PDF.