Get Free Email Alerts-Freshers Jobs/Conferences/Entrance Exam Alerts-Subscribe to Technicalsymposium.com & Latest Updates-Click here

Free Publishing of your college Events Procedure (Symposium/Conferences/Workshops)-Click here

EJB Development Considerations and Steps

The steps to developing EJBs can be partitioned along two main lines: server-side and client-side development. Although server-side development of distributed communications servers, such as CORBA and RMI, takes on a somewhat-complicated nature at times, server-side development of EJBs is simplified because much of the communications, state management, resource allocation, and thread management infrastructure coding is provided by the container. These are the main steps employed for server-side EJB development:

1. Implement EJB standard interfaces—Any interfaces required by the standard EJB component model to enable container-based management of the EJB should be implemented.

2. Implement EJB business-specific interfaces—Any business-specific interfaces provided by your EJB and any supporting helper and utility classes should be implemented.

3. Create client remote interfaces—The remote interface for your EJB that defines all business-specific interfaces to the EJB should be created.

4. Create client home interfaces—The home interface for your EJB that defines the application-specific methods for creating your EJB, as well as application-specific methods for finding your EJB (if it is an entity bean), should be created.

5. Compile EJB code—The EJB implementation, home interface, and remote interface should be compiled.

6. Configure module deployment descriptors—The standard EJB deployment descriptor should be configured to define the specific structural characteristics and dependencies of your EJB. Any deployment descriptors needed by your container/server provider should also be configured.

7. Package EJB into an EJB JAR module—The standard EJB deployment descriptor, any vendor-specific deployment descriptors, and one or more of your compiled EJB class files should be packaged into an EJB JAR module.

8. Configure application deployment descriptor—A standard J2EE deployment descriptor should be configured for a cohesive collection of J2EE modules.

9. Package EJB Modules into a J2EE EAR Application—The standard J2EE deployment descriptor and one or more EJB JAR files should be packaged into a J2EE EAR application.

10. Deploy the J2EE application—The J2EE EAR application should be deployed to a J2EE-compliant application container/server environment.