Summary

Today's lesson completed your study of session beans by covering stateless session beans. Stateless session beans are "lightweight" session beans. Today's lesson began with the basic concepts of stateless session beans. You looked at how the life cycle of a stateless session bean differs from the life cycle of a stateful session bean. You also took a quick look at the components of a stateless session bean.

After this, an advanced concept accessing EJBs from CORBA and RMI clients was covered. You took a quick look at some of the issues involved in the distributed-computing communication mechanism between EJBs and CORBA and RMI clients. You also studied the steps involved in writing CORBA and RMI clients that can access EJBs deployed on WebLogic Server. For this purpose, you studied how to generate IDL files and client stubs using the weblogic.ejbc and weblogic.rmic compilers provided with WebLogic Server. The final step was to understand how CORBA and RMI clients access the naming service of WebLogic Server (where the EJBs are registered using JNDI) and use JNDI to obtain references to the home interface objects of EJBs registered during deployment.

The last two sections were devoted to writing stateless session beans in the restaurant sample application and the Airline Ticket Booking System MVC application. You rewrote the functionality of the chef in yesterday's restaurant application as a stateless session bean.

The final activity you undertook was to build the business-logic part of the model layer of the Airline Ticket Booking System MVC application. For this you implemented the user registration function as a stateless session bean and the ticket-booking representative as a stateful session bean.

Now that you have completed the study of session beans, in the next two days you will be looking at the second type of EJB, the entity bean.