> > I don't believe it's necessarily true for the system loader to be a parent > of the context loader. It's common, but not necessary. The only loader you > can't get away from is the boot class loader.
Ok, I wasn't totally precise. You're right about the boot and system class loader. The point was that all the parent class loaders would be checked prior to checking the actual class loader. So checking the context class loader would result in checking all the class loaders above it (in the hierarchy) - and if the hierarchy wasn't explicitly changed this should be perfectly ok. On Tue, Jun 1, 2010 at 9:17 PM, Lex Spoon <[email protected]> wrote: > On Tue, Jun 1, 2010 at 2:35 PM, Marko Vuksanovic < > [email protected]> wrote: > >> Class Loaders are checked in parent to child direction - so if you try to >> fetch a resource from a context class loader, system class loader is the >> first that will be checked and only after resource is not found there, next >> child will be checked... and so on... So if something is found in context >> class loader, all parent class loaders have been checked. Somebody correct >> me if I'm wrong. > > > I don't believe it's necessarily true for the system loader to be a parent > of the context loader. It's common, but not necessary. The only loader you > can't get away from is the boot class loader. > > That said, if it's not on the context loader, you might want to ignore it > if you can get away with it. For that matter, the same goes for things not > in the resource oracle. > > -Lex > > > -- > http://groups.google.com/group/Google-Web-Toolkit-Contributors > -- http://groups.google.com/group/Google-Web-Toolkit-Contributors
