As can be seen in the drawing, a component is having two additional placeholders, slightly extended to the left of the symbol's boundary. Thus, for EJBs, these will be used for the methods that need to have related operations in the 'home' and 'remote' interfaces of a bean. Since SoftModeler supports components of both types, EJB and plain JavaBeans, one may set the default component framework of the whole class diagram to either EJB or JavaBeans. This will make all components created from that moment on, have this framework already set. Designing an EJB EJBeans are divided into two types, Session beans and Entity beans.
Entity beans are mainly for representing persistence data, such as records in a relational database.
They are intended for being accessed by multiple clients, and they survive a server shut down. Session beans are for managing client-server sessions, business rules, transactions, and alike, and are aimed at communicating with a single client. Therefore, the life cycle of a session bean may end when a client is disconnecting, or the server is turned off. Session beans may be either stateful, or stateless, a decision deferred to the deployment stage. When requesting to create a new component in the class diagram, SoftModeler automatically opens a dialog window which allows to define the properties of the component.