Hi, I missed this message initially, so forgive the late response. As a non-developer, I'm going to try and tread carefully, but forgive me if I do not.
I've asked a couple of times about the OQLEnumeration static class in OQLQueryImpl (org.exolab.castor.jdo.engine) with regard to it being static, and wondering if I'm trying to bend castor too far, or if there is room for making it non-static. Useful references to the issue are: http://www.mail-archive.com/[email protected]/msg01671.html - the start of one thread on it. http://www.mail-archive.com/[email protected]/msg02657.html - Thomas saying he'd try and look at it (Thomas I am sure you are busy, and your work on castor is much appreciated, I assume you haven't had a chance to look at this as yet?). in short, the finalizer for OQLQueryImpl closes the query and the results, meaning that if you have a reference to the results, without having a reference to the query, then you could find yourself with a closed set of results. my suggestion is to make OQLEnumeration non-static, so that the reference to the results will prevent the QQLQueryImpl being garbage collected. cheers, dim ----------------------------------------------------------- If you wish to unsubscribe from this mailing, send mail to [EMAIL PROTECTED] with a subject of: unsubscribe castor-dev
