db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Daniel John Debrunner <...@debrunners.com>
Subject Re: [jira] Created: (DERBY-556) NetworkServer does not set thread context classloader
Date Tue, 06 Sep 2005 15:56:08 GMT
Jeremy Boynes (JIRA) wrote:

> NetworkServer does not set thread context classloader
> -----------------------------------------------------
> 
>          Key: DERBY-556
>          URL: http://issues.apache.org/jira/browse/DERBY-556
>      Project: Derby
>         Type: Bug
>   Components: Network Server  
>     Versions: 10.1.1.0    
>     Reporter: Jeremy Boynes
> 
> 
> The NetworkServer does not set the thread context classloader which is used to load the
implementations of stored procedures.
>As a result, procedure implementations must be present in the classpath
of the engine itself;
>this differs from embedded mode where classes may be located in the
application.

Jeremy, I'm having trouble understanding this.

The embedded engine requires classes for Java procedures to either be
available through the thread context classloader, the class loader for
Derby code, or through the database classpath using jars stored in the
database.

I'm not sure what the network server would set the thread context
classloader to that would change anything, and I'm not sure what you
mean by 'this differs from embedded mode where classes may be located in
the application'. What does 'located in the application' mean?

Is there some concrete example you have that is broken?

Dan.






Mime
View raw message