Re: Another question about codebases and jar versions
"Logan, Patrick" <[email protected]>
| Newsgroups | gmane.comp.java.sun.jini |
|---|---|
| Message-ID | <[email protected]> |
> The visibility of that new classloader vs any older version > classloader is still something that your application might have to > "worry" about explicitly. The context class loader is one of the > predominate mechanisms for making sure that the right classes are > loaded as preferred classes. > Managing and maintaining the right context class loader is another > issue for another thread. Thanks. OK. So this would come up particularly in the situation with some framework/library utility loading something on behalf of some application code, and the utility has to be aware of the loader to be used, what's the context loader for that thread, etc. So I believe for my current purposes I can just ignore the context loader issues. I hope. Give me one thing to ignore. Thanks -Patrick -------------------------------------------------------------------------- Getting Started: http://www.jini.org/wiki/Category:Getting_Started Community Web Site: http://jini.org jini-users Archive: http://archives.java.sun.com/archives/jini-users.html Unsubscribing: email "signoff JINI-USERS" to [email protected]