One of my favorite comprehensive J2EE references is "Professional Java Server Programming, J2EE 1.3 Edition" by Allamaraju et al. (WROX). Their recommendation for CMP v. BMP is to stick with CMP unless you really need BMP:
"...The basic problem is that, although every EJB 2.0-compliant container must provide support for container-managed persistence, the specification does not indicate *how* this support must be provided. In fact, a container need not necessarily provide any CMP support for mapping your entity bean's state to columns in a database. It could use Java serialization to write the whole bean to one column and still be compliant. This would rarely be adequate for a project, and might necessitate the use of bean-managed persistence if your EJB container used serialization.
"On the other hand, this extreme case doesn't exist in real life. Every single application server with EJB support of which I am aware, including the open source ones, has some support for mapping your objects to the fields in a relational database.
"The trick is determining whether your EJB container has the level of support for container-managed persistence that you require. If it does, take advantage of this support to free your business-logic programmers from writing persistence logic. The boost in productivity is potentially very large, and depending on the EJB container, the boost in application performance may be large, too."
It goes on to say that you will probably need to use BMP is your target data store is an ERP system or some other existing application.
Ranch Hand Scavenger Hunt
Number Posts (4/100)
First Post