In BMP the bean provider is responsible for implementing the persistence of the entity bean. In CMP, on the other hand, the tools supplied by the EJB container provider generate the persistence code for the entity bean.
A2:
Yes, JDO can be used as a better alternative to BMP in entity beans. Because JDO does not contain any database-specific code within the Java source code file, it proves to be an effective alternative to BMP. Moreover, with the XML metadata mapping file, JDO provides ease of development at a level similar to that of CMP.
A3:
The EJB to JSP integration tool is useful for generating tag libraries that encapsulate the client-side code required to look up and create EJBs. The tool makes it easier to embed and access EJBs from within JSPs. Model I architecture defines accessing JavaBeans, Java classes, or EJBs from within JSPs.
Exercise
A1:
Start up the EJB to JSP integration tool and follow the instructions listed in the section "EJB to JSP Integration Tool" for generating the tag library for the entity beans of the restaurant application. Use the EJBBMPDeploy.jar Java archive file.