Discussion on:
View:
Show:
This article is nice but might give the impression that using custom class loaders is easy.
Well, it's mostly the case in a standalone, single-thread virtual machine but writing and enforcing the use of a custom class loader in a multi-threaded environement like a J2EE application server is another story.
I think the article should also say a word on that, developers must be aware that a class loader can be specified for a Thread, overriding the default class loader mechanism described here.
The article should also describe the different strategies for delegating the loading to the parent class loader which are "parent-first" and "parent-last".
Parent-first is the default behaviour. Parent-last allows you to make specific classes be loaded prior to classes already present in the class-path.
Lots of subtleties this article does not cover at all...
Well, it's mostly the case in a standalone, single-thread virtual machine but writing and enforcing the use of a custom class loader in a multi-threaded environement like a J2EE application server is another story.
I think the article should also say a word on that, developers must be aware that a class loader can be specified for a Thread, overriding the default class loader mechanism described here.
The article should also describe the different strategies for delegating the loading to the parent class loader which are "parent-first" and "parent-last".
Parent-first is the default behaviour. Parent-last allows you to make specific classes be loaded prior to classes already present in the class-path.
Lots of subtleties this article does not cover at all...
This is an introducing article, more a tip than a documentation. It should not cover the described feature in all details, but just give a direction for experiments and further learning for inexperienced users, obviously you are just not one of them.
- Keyboard Shortcuts:
- Prev
- Next
- Toggle
