> From: A mailing list for Enterprise JavaBeans development > [mailto:[EMAIL PROTECTED]]On Behalf Of Frank Gao > In ejb2.0 specification cmp fields are moved out from the bean to the > deployment file, but bean providers still have to code a bunch of "getxxx" > and "setxxx" methods, which means bean provides have to know the names of > all cmp fields and therefore the deployer can not change, insert or delete > cmp fields or their attributes defined in xml file. So what's the benefit of > moving cmp fields out? First, Bean Providers have always needed to know the names of their CMP fields, and use them in both their bean class and their deployment descriptor. Nothing terribly new here. The benefit of "moving CMP fields out" is to leave their implementation up to the Persistence Manager. This has several good properties, such as making it easier for the Container to determine if the bean has changed, and to know exactly what fields have changed. -- Cedric =========================================================================== To unsubscribe, send email to [EMAIL PROTECTED] and include in the body of the message "signoff EJB-INTEREST". For general help, send email to [EMAIL PROTECTED] and include in the body of the message "help".
