You are viewing a plain text version of this content. The canonical link for it is here.
Posted to derby-dev@db.apache.org by "Rick Hillegas (JIRA)" <de...@db.apache.org> on 2005/11/15 22:52:28 UTC
[jira] Assigned: (DERBY-556) NetworkServer does not set thread context classloader
[ http://issues.apache.org/jira/browse/DERBY-556?page=all ]
Rick Hillegas reassigned DERBY-556:
-----------------------------------
Assign To: Rick Hillegas
> 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
> Assignee: Rick Hillegas
>
> 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.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
Re: [jira] Assigned: (DERBY-556) NetworkServer does not set thread
context classloader
Posted by Sunitha Kambhampati <ks...@gmail.com>.
Rick Hillegas (JIRA) wrote:
>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.
>
>
>
>
>
I am trying to understand the problem here. What does it mean that
classes may be located in the application , for a client ?
Currently, in network server mode,
1) the user defined classes for procedure impl need to be added to
classpath of the server.
2) or you can install the jar using SQLJ.INSTALL_JAR option and then
update the derby.database.classpath value.
With a solution to this bug, how will it affect classpath issues for
procedures/functions ?
Rick -- when you have it figured out , can you please maybe provide a
description.
Many thanks.
Sunitha.