After the finalize method has been invoked for an object, no further action is taken until the Java virtual machine has again determined that there is no longer any means by which this object can be accessed by any thread that has not yet died, including possible actions by other objects or classes which are ready to be finalized, at which point the object may be discarded.
Originally posted by Cherry Sta. Romana:
Thanks to both of you. My friend was asking about this and I said that I don't think that it is possible. However, we both attended a training on Java and we both remember that our trainor said that it is possible using some form of super.super.. Anyway, we mis-understood it probably.
Thanks again.
Originally posted by Nils_Widmer:
70% + in JQPlus?
I bought the JQPlus, but hell I just got 31%, 37% and 46% in the tests I tried, I find that test awfully hard even if I program on job in java for over 7 months, plus there were no Sockets, Graphics or JDBC questions in JQPlus at all, dont they update JQPlus??
Originally posted by david hu:
Thanks. But is there a way not to use WindowListener interface? Since from the book Java exam cram, it's said that override processEvent is another way to tackle event?
The strategy of explicitly enabling events for a component can be summarized as follows:
1. Create a subclass of the component.
2. In the subclass constructor, call enableEvents(AWTEvent.XXX_EVENT_MASK).
3. Provide the subclass with a processXXXEvent() method; this method should call the superclass' version before returning.
Originally posted by payal sharma:
//When it break the loop and reach to point why it do not came again in
loop ?