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)" <ji...@apache.org> on 2009/03/27 22:42:50 UTC
[jira] Commented: (DERBY-4126) You can't invoke a table function
which is stored in a jar file inside the database
[ https://issues.apache.org/jira/browse/DERBY-4126?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12690119#action_12690119 ]
Rick Hillegas commented on DERBY-4126:
--------------------------------------
Tests ran cleanly for me except for the heisenbug in the stress-multi tests. Committed second rev of the patch at subversion revision 759360.
> You can't invoke a table function which is stored in a jar file inside the database
> -----------------------------------------------------------------------------------
>
> Key: DERBY-4126
> URL: https://issues.apache.org/jira/browse/DERBY-4126
> Project: Derby
> Issue Type: Bug
> Components: SQL
> Affects Versions: 10.4.1.3, 10.4.2.0, 10.5.1.1, 10.6.0.0
> Reporter: Rick Hillegas
> Assignee: Rick Hillegas
> Attachments: derby-4126-01-aa-useSessionClassloader.diff, derby-4126-01-ab-useSessionClassloader.diff
>
>
> You get a ClassNotFoundException when you try to invoke a table function which lives in a jar file stored inside the database. This is because FromVTI.implementsDerbyStyleVTICosting() looks up the class using Class.forName() rather than using the session classloader. A similar bug is in FromVTI.getVTICosting(). This bug was reported by Krzysztof N in the following user list thread: http://www.nabble.com/Uinable-to-use-Table-function-due-to-java.lang.ClassNotFoundException--while-class-is-clearly-reachable..-td22478383.html#a22699492
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.