EJB（EJB）.docVIP

EJB（EJB） Title: EJB Publisher: flyfox release time: 09, 18 Detailed information: EJB Summary： This section covers the main content: The architecture of EJB: the architecture of EJB technology is introduced. Why use the EJB container? The architecture of EJB: EJBs top tier distributed application is based on the object component model, and the lower level transaction service uses API technology. EJB technology simplifies the development, configuration, and execution of enterprise application systems written in JAVA language. The specification of the architecture of the EJB is formulated by Sun Microsystems. The EJB container for Inprise is based on the 1.1 edition specification. EJB technology defines a set of reusable components: Enterprise, Beans. You can use these components to build your distributed applications like building blocks. Once youve written the code, these components are grouped into specific files. Each file has one or more Enterprise Beans, plus some configuration parameters. Finally, the Enterprise Beans is configured to be on a platform with a EJB container. The client can locate a beans through these Beans home interfaces and produce an instance of the beans. In this way, the client can invoke the application method and the remote interface of Beans. The EJB server manages EJB containers and functions as a bridge between containers and low-level platforms. It provides the EJB container with the ability to access system services. For example: database management and transaction management, or for other Enterprise application servers. All the EJB instances are running in the EJB container. The container provides system level services that control the life cycle of the EJB. Because the container has mastered most of the system level issues (ha ha, I dont know how to translate). Developers of Enterprise Beans do not need to apply logical considerations. In general, the EJB container has the following system - level issues. 1, the Security-- configura