Session Object Persistence
Session objects, by definition, are not persistent. They may, however, contain information that needs to be made persistent. As with bean-managed entity objects, session objects can implement persistence operations directly in the methods in the enterprise bean. Session objects also often maintain a cache of database information that must be synchronized with the database when transactions are started, committed, or aborted. The enterprise bean developer must implement persistence operations (e.g., JDBC, JDO, or SQLJ) directly in the session bean class methods. See:
More on the general topic: J2EE EJB Server or Container
Author: Douglas K Barry
You may use this material for your work or classes. Reprint Policy. Be sure to check the menu at the left for other articles available on this site.
The Savvy Manager's Guide
Douglas K Barry is also the author of a book that explains Web Services, service-oriented architecture, and Cloud Computing in an easy-to-understand, non-technical manner.
Web Services, Service-Oriented Architectures, and Cloud Computing: The Savvy Manager's Guide (Second Edition)
by Douglas K Barry with David Dick
This is a guide for the savvy manager who wants to capitalize on the wave of change that is occurring with Web Services, service-oriented architecture, and—more recently—Cloud Computing. The changes wrought by these technologies will require both a basic grasp of the technologies and an effective way to deal with how these changes will affect the people who build and use the systems in our organizations. This book covers both issues. Managers at all levels of all organizations must be aware of both the changes that we are now seeing and ways to deal with issues created by those changes.