Introduction
This guideline focuses on designing session beans. Additional guidance on session beans, such as how to identify and
model them, is provided by Guideline: Session Beans. General guidance on EJBs is provided by Guideline: Enterprise JavaBean (EJB)
Session beans can provide local and/or remote interfaces. See Guideline: Enterprise JavaBean (EJB) for guidance on when to use which.
Parameter Passing
Each call of a session bean's remote interface carries overhead. Thus, the number of remote calls required to perform a
given use-case can be a significant driver of performance and network loading. See Work Product Guideline: Enterprise JavaBeans (EJBs) for strategies for parameter
passing.
Session beans can use use bean-managed or container-managed transactions. Generally container-managed transactions are
simpler, and so are the preferred approach. See Guideline: Designing Enterprise JavaBeans (EJBs) for more guidance.
|
