Hiran, You are correct that this can already be accomplished with the current versions of castor. Simply specify the alternate setter/getter methods that you want castor to use in the mapping file -
HTH - Margaret -----Original Message----- From: Hiran Chaudhuri [mailto:[EMAIL PROTECTED] Sent: Wednesday, February 26, 2003 10:20 AM To: [EMAIL PROTECTED] Subject: Re: [castor-dev] Castor JDO serious design flaw? ----- Original Message ----- From: "Rhett Sutphin" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Wednesday, February 26, 2003 3:39 PM Subject: Re: [castor-dev] Castor JDO serious design flaw? > > The reason I ask, is of course that I would like my getter & setter > > method code > > blocks to execute only when called by other aspects of my system. > > I would argue that a persistence mechanism has no business executing > > these code blocks. > > If you would prefer that it read field values by direct access to the > member variables, that can be accomplished using the "direct" attribute > in the field mapping. Note that this requires that the member > variables be public. > > Otherwise, I am curious about how you would suggest the persistence > mechanism gain access to the values that it will persist. How about jdoGetXXXX and jdoSetXXXX (just alternate get/set methods, which are not used by normal bean pattern...) I think Castor can be configured to do so, but I have never practiced it. Hiran ----------------------------------------------------------- If you wish to unsubscribe from this mailing, send mail to [EMAIL PROTECTED] with a subject of: unsubscribe castor-dev ----------------------------------------------------------- If you wish to unsubscribe from this mailing, send mail to [EMAIL PROTECTED] with a subject of: unsubscribe castor-dev
