[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: URL protocol handler classloader
From: |
Mark Wielaard |
Subject: |
Re: URL protocol handler classloader |
Date: |
Sun, 02 Jan 2005 12:23:26 +0100 |
Hi,
On Sat, 2005-01-01 at 16:01 +0100, Ewout Prangsma wrote:
> Now; currently the URL class uses the system classloader to load
> protocol handlers.
> Must this really be the system classloader?
>
> I have a protocol handler that is accessible via the context classloader
> (Thread.currentThread().getContextClassLoader()), but not via the system
> classloader. Is it possible to change this classloader arrangement so
> that the current context classloader is used?
Yes. I implemented the current behavior in response to bug #9466
(http://savannah.gnu.org/bugs/?func=detailitem&item_id=9466) which is
still open since we seem to agree that using the context classloader
would be the more correct option (falling back to the system/application
classloader when that fails). See the bug report for some more
discussion about this issue.
Cheers,
Mark
signature.asc
Description: This is a digitally signed message part
- URL protocol handler classloader, Ewout Prangsma, 2005/01/01
- Re: URL protocol handler classloader,
Mark Wielaard <=
- Re: URL protocol handler classloader, Steven Augart, 2005/01/15
- Re: URL protocol handler classloader, Mark Wielaard, 2005/01/16
- Re: URL protocol handler classloader, Steven Augart, 2005/01/16
- Re: URL protocol handler classloader, Mark Wielaard, 2005/01/16
- Re: URL protocol handler classloader, Steven Augart, 2005/01/16
- RE: URL protocol handler classloader, David Holmes, 2005/01/16
- Re: URL protocol handler classloader, Mark Wielaard, 2005/01/17