{quote:vinraj}
As per my understanding, a class loader always delegates the search of a given class to its parent and only if the class is not found tries to load it on its own. This I believe is the fundamental paradigm ensuring security. For example, I cannot define a class called java.lang.Object on my own. Even if I do so, the class loaded will always be the Object class belonging JVM's system jars and not my custom class.
{quote}

Hello vinraj, first of all thank you for your post. And yes you are right, thank you for your correction. I'll correct the entry. \\
I wrote that because at the time I was already thinking what I had done with my "hot deploy custom class loader" - you can read more about it on my latest post {link:Java Programming: Hot Deploy|url=http://www.pabrantes.net/blog/comments/start/2007-07-23/1} - which first would try to find the class by itself in order to be able to reload it (other the parent would already have it defined and the old version would be returned).

Once again thank you for the correction and for the post. I'm glad you found it interesting.