Hi, I think that both these statements are true. EJB1.1 CMP says: one table row == one entity bean And common sense (as well as most experts of component oriented development) says that: (one table row == one entity bean) means "no good" due to interbean call overhead and no advantage. The conclusion is harsh, though obvious: EJB1.1 CMP is no good. I guess this is why CMP is changed for EJB2.0. Best Regards, Ole Husgaard. [EMAIL PROTECTED] wrote: > > >From reading the EJB spec and a number of other documents, I have > gained the impression that (one table row == one entity bean) if I > want to use CMP. > > I am currently in the progress of reading the J2EE Blueprints, and in > a discussion on the cons of using entity beans, the following is said: > > "(...) Therefore modeling every object representing a row in the > database as an entity bean is not recommended. An entity bean is > better suited to represent a coarse-grained business object that > provides more complex behavior than only get and set methods for its > fields." > > ( http://java.sun.com/j2ee/blueprints/ejb_tier/entity_beans/index.html ) > in the bullet titled "Representing persistent data", first bullet > on the page. > > This seems to imply that there is another method that I have not seen > in which I may not need one entity bean per row. > > Is someone able to elaborate on this? > > Cheers > Bent D > -- > Bent Dalager - [EMAIL PROTECTED] - http://www.pvv.org/~bcd > powered by emacs > > _______________________________________________ > JBoss-user mailing list > [EMAIL PROTECTED] > http://lists.sourceforge.net/lists/listinfo/jboss-user _______________________________________________ JBoss-user mailing list [EMAIL PROTECTED] http://lists.sourceforge.net/lists/listinfo/jboss-user
