翻译文献EJB 3 Deployment.docVIP

大连交通大学2016届本科生毕业设计（论文）外文翻译 外文原文 EJB 3 Deployment Until now, this book has focused on how to build EJBs, Java Persistence API (JPA) entities, and their clients, for exploiting the surrounding enterprise services offered by the EJB container. In Java EE parlance, these tasks fall under the role of Application Component Provider, which is referred to here simply as the Provider. In this chapter, we explore the topics that surround the process of packaging your components into modules and library components, binding external references declared in your Java EE components to actual resources in your server environment, and sending it all off to an application server so that the components can be executed at run time by an application. These responsibilities are handled by the Java EE roles of the Application Assembler (the Assembler) and the Application Deployer (the Deployer). While in practice it is common or a single individual to perform one or more of these roles, or for many people to perform any single role, for the purpose of explaining these topics we will partition the deployment tasks into stages that correspond to these designated roles. We will emphasize EJB and JPA entity components, but also touch on deployment of the other Java EE module types: web application modules, application clients, and resource adapters. We will also look at the relationship between the Java EE server and the four Java EE containers that it supports, and explore some of the services that are provided by a Java EE server. Following a brief overview of the deployment tasks, in which we introduce much of the deployment terminology, we offer a look at the Java EE infrastructure components— the Java EE server and containers—that support deployment. We explore the different types of Java EE modules and how they fit together, and how you specify the deployment descriptors—metadata files—that define each module. A section on library components explains how to declare classpath dependenc