Originally posted by Jeanne Boyarsky:
Jeff,
Does the other person running the app already have a database? If so, which one?
Originally posted by marc weber:
It does not set the e3.e reference to null. However, the object that e3.e is pointing to can no longer be reached, and this makes it eligible for garbage collection.
But there is a problem with this code. At runtime, it will throw a NullPointerException at the line e2.e = e1; At that point, e2 is already null, so e2 cannot be dereferenced to get to e2.e.
[ July 28, 2007: Message edited by: marc weber ]
Originally posted by kathir vel:
In this sample program also the same logic...with out notify waiting thread can continue execution once it get the object lock again.
Originally posted by anil kumar:
Hi
Jeff Schuler
How can you assign a super class reference to a sub class reference ?
Here ArrayList is-A List
Have you Got it ?
Thanks
Anil Kumar
[ July 02, 2007: Message edited by: anil kumar ]