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.
