[ http://issues.apache.org/jira/browse/GERONIMO-1001?page=comments#action_12323128 ]
Jeremy Boynes commented on GERONIMO-1001: ----------------------------------------- A workaround is to load the classes for the procedures into the database as described here: http://db.apache.org/derby/docs/10.1/devguide/cdevdeploy30736.html I don't know if this is a permanent link so the relevant commands are: CALL sqlj.install_jar('procs.jar', 'APP.Sample1', 0); CALL SYSCS_UTIL.SYSCS_SET_DATABASE_PROPERTY('derby.database.classpath', 'APP.Sample1'); > Derby NetworkServer does not use TCCL > ------------------------------------- > > Key: GERONIMO-1001 > URL: http://issues.apache.org/jira/browse/GERONIMO-1001 > Project: Geronimo > Type: Bug > Components: databases > Versions: 1.0-M5 > Environment: Derby 10.1 > Reporter: Jeremy Boynes > > When calling stored procedures, the Derby engine locates the implementation > using three sources: > * the Thread's context classloader (TCCL) > * the database class path (jars that have been loaded in) > * the classpath of the engine classes themselves > When embedded in Geronimo as a RAR, we initialize the TCCL to that of the RAR > which allows procedure code to be located in the RAR itself. > However, if the RAR defines a NetworkServer the TCCL is not inherited by the > worker threads it spawns to service requests from clients and as a result > calls to procedures whose implementation is located in the war will fail with > a ClassNotFoundException -- 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
