Re: Use of finalize methods in WO
Re: Use of finalize methods in WO
- Subject: Re: Use of finalize methods in WO
- From: Mike Schrag <email@hidden>
- Date: Thu, 21 Aug 2008 09:15:11 -0400
- where are the finalize() methods?(EOF, Wonder, ?)
As several others have pointed out, finalize is called by the GC.
Further, nothing in WO, EOF, or Wonder directly calls the finalize
method. If they're tracing through calls, they're probably seeing the
calls to super.finalize() and mistaking them for direct finalize calls.
- how this use could affect GC perfomance?
Well, obviously implementing a custom finalizer TECHNICALLY slows down
the GC, because it becomes more expensive to collect those
objects .... but .. i mean .. really? This is the POINT of a GC.
These objects have to be cleaned up, so it would be more work for you
to manually do it. Also, show me a J2EE stack that doesn't implement
any custom finalize methods.
- is it a valid point "per se"?
No. It's an asinine point per se.
I'll be the first one to point out WO's flaws, and it certainly has
its share of flaws (like any framework), but they've gotta do a little
better than this.
ms
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden