Janssen, Roger wrote:
There is no problem when the resultset is presented as a collection. Why is
that?
Is the collection build by iterating over the resultset?
Exactly. The Iterator holds an open ResultSet and materialize the object when 'next()' was called.
OJB iterate over an OJBIterator instance to populate the Collection, thus the Collection instance has no dependency to PB or Connection.
Suppose i do not call the releaseresources method, what would happen? Would it produce a memory leak?
hmm, what do you expect? ;-)
If you don't release the resources all ResultSet and Statement will not be closed, thus the side-effects depend on your jdbc-driver (normally the driver close these resources by himself).
But if an OJBIterator implementation does some intern cleanup (free used objects or something similar) it may cause memory leaks.
regards, Armin
thanx for the quick repsonse,
roger
*************************************************************************
The information contained in this communication is confidential and is
intended solely for the use of the individual or entity to whom it is
addressed.You should not copy, disclose or distribute this communication without the authority of iBanx bv. iBanx bv is neither liable for the proper and complete transmission of the information has been maintained
nor that the communication is free of viruses, interceptions or interference.
If you are not the intended recipient of this communication please return the communication to the sender and delete and destroy all copies.
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
