Hi Guys,
I just wanted to say that I've been using Castor JDO for a short time now,
and all seemed to be going swimmingly. It's well documented, easy to use &
combined with Castor Doclet it aids development quite nicely.
However I have noticed that the Castor JDO engine calls the setter & getter
methods for objects which I have decided should be persistent.....
Is this by design?
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.
At first this might seem like a pedantic requirement, but if I want
to attach an observer to a class which has been made persistent using
Castor JDO, well you can imagine....
Since I discovered this, I have tested it with a commercial implementation (lido)
of JDO and found that this does not happen with it. I assume the other commercial
vendors have thought of this.
Has else anybody found this to be the case, and had similar problems?
Is there a known way to prevent this happening using Castor?
Regards,
Darragh
Darragh O'Flanagan|Software Engineer
Ericsson Systems Expertise
Beech Hill
Clonskeagh
Dublin 4
( +353 1 2072689
[EMAIL PROTECTED]
-----------------------------------------------------------
If you wish to unsubscribe from this mailing, send mail to
[EMAIL PROTECTED] with a subject of:
unsubscribe castor-dev
