In order to code an application the developer needs some way to get to the attributes of an object, so the developer has to have the getXXX() and setXXX() methods. I don't think you'd want the container changing the field names and thus the accessor methods, it would make it hard to write the rest of the application. Of course the persistence manager is free to add attriutes to the bean in order to get it's work done, but these aren't visible to clients which is the way it should be. By moving the fields out, and thus the implementations of the getXXX() and setXXX() methods the persistence manager has a large amount of freedom in how it implements it's part of the bean (CMP). It can do lazy loading, whatever. Cheers Jay Walters -----Original Message----- From: Frank Gao [mailto:[EMAIL PROTECTED]] Sent: Friday, January 19, 2001 1:41 PM To: [EMAIL PROTECTED] Subject: cmp Hi, all I've got a question about ejb2.0 spec. and hopefully somebody can discuss it with me. 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? Thanks Frank =========================================================================== 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". =========================================================================== 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".
