Roles in the development of (Php5 hosting) an EJB application
Roles in the development of an EJB application Fortunately, using components that follow the EJB specification to build distributed systems relieves much of the burden by: Dividing the development of a distributed system into specific tasks that are assigned to specialists. For example, if the application is an accounting system, the enterprise bean developer would need to understand accounting. The system administrator must know about monitoring a deployed and running application. Each specialist assumes a particular role. Making EJB server and container services available to the enterprise bean and application developers. The EJB server provider and EJB container provider (who are often the same vendor) handle many of the more difficult tasks so the developers don t have to. For example, the container an enterprise bean runs in can provide transaction and security services to the bean automatically. Making enterprise beans portable. Once a bean is written, it can be deployed on any EJB server that adheres to the Enterprise JavaBeans standard. Each bean is likely to include vendor-specific elements, however. Roles in the development of an EJB application The work of developing a distributed EJB application is divided into six distinct roles. Each role is assumed by an expert in their domain. By dividing the work this way, the task of creating and managing a distributed system becomes much easier. The six roles are divided into three categories: application roles, infrastructure roles, and deployment and operation roles. Application roles Those who assume the application roles write the code for the enterprise beans and the applications that use them. Both roles require an understanding of how the business runs, although at different levels. These are the two application roles: Bean provider Bean providers (also called bean developers) create the enterprise beans and write the logic of the business methods within them. They also define the remote home or local home and remote or local interfaces for the beans and they create the beans deployment descriptors. Bean providers don t necessarily need to know how their beans will be assembled and deployed. Application assembler Application assemblers write the applications that use the enterprise beans. These applications usually include other components, such as GUI clients, applets, JavaServer Pages pages (JSP), and servlets. These components are assembled into a distributed application. Assemblers add assembly instructions to the bean deployment descriptors. Although application assemblers must be familiar with the methods contained within the enterprise beans so they can call them, they don t need to know how those methods are implemented. JBuilder users who are interested in Enterprise JavaBeans are usually bean providers and application assemblers. Therefore, this book is written primarily for them. JBuilder has wizards, designers, and other tools that simplify the development of enterprise beans and the applications that use them. 6 Developing Applications with Enterprise JavaBeans
We are the cheapest Catholic web hosting provider, check Catholic Web Hosting services and make sure of alone.