Interesting. A prossible use of finalize. It seems that finalize is 'suggested to be' removed though: Link From Thinking in Java, 3rd ed. Revision 4.0
So it appears that finalize( ) is only useful for obscure memory cleanup that most programmers will never use. However, there is a very interesting use of finalize( ) that does not rely on it being called every time. This is the verification of the termination condition of an object. At the point that you�re no longer interested in an object�when it�s ready to be cleaned up�that object should be in a state whereby its memory can be safely released. For example, if the object represents an open file, that file should be closed by the programmer before the object is garbage collected. If any portions of the object are not properly cleaned up, then you have a bug in your program that could be very difficult to find. The value of finalize( ) is that it can be used to eventually discover this condition, even if it isn�t always called. If one of the finalizations happens to reveal the bug, then you discover the problem, which is all you really care about.
[ January 16, 2004: Message edited by: Jim Crawford ]
Jim, That's old news. Class finalization was specified in the first edition of the JLS in 12.7, Finalization of Classes. The class finalization feature does not appear in the second edition. The instance finalization feature that remains is not the same as the obsolete class finalization feature. Instance finalization occurs before instances are garbage collected. Class finalization was intended to occur before classes were unloaded.
Dan Chisholm<br />SCJP 1.4<br /> <br /><a href="http://www.danchisholm.net/" target="_blank" rel="nofollow">Try my mock exam.</a>
I’ve looked at a lot of different solutions, and in my humble opinion Aspose is the way to go. Here’s the link: http://aspose.com