Srinivasan - There are lot of changes in terms of persistence approach in ejb 2x and ejb 3. Entity beans has been removed (i mean no CMP or BMP) and Pojo based entities are introduced. Sun has standardized the persistence approach through Java Persistence API.
if you are really thinking of a solution on a maintainability perspective, you would really have a second thought on the choosing CMPs for this assignment.
However as Newman has said, since this exam is not on JEE 5 you are free to choose CMP or BMP for this assignment.
Deiveehan N - SCJP, SCWCD, SCBCD, IBM-484, SCEA
You may be in the right track, but if you sit there, you will get run over !!
For what it is worth. I completed part II and part III a couple of weeks back and have not used entity beans as after many years of playing with entity beans and other persistence mechanisms such as JDO and Hibernate, I do not believe that Entity beans are anywhere near as scalable. Put Simply I do not believe that is the Sun engineers did not agree then the EJB 3.0 spec would not have included a JDO type of persistence mechanism.
I am waiting to get my results back, so Sun may take a look and say I failed cos I never used Entity Beans, however I never saw anything in the requirements that said they had to be used and I saw plenty that said the app needs to be scalable. I did see in the requirements that the architecture needs to be a j2ee architecture, but I think too many people forget that simple Servlets and Jsp's are J2EE components, and there is nothing (as I previously said) in the requirements that says there is a need to use all of the J2EE components.
This is however just my thinking and I have not got my final marks back yet, so I could be wrong.
Doody calls. I would really rather that it didn't. Comfort me wise and sterile tiny ad: