db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Knut Anders Hatlen <knut.hat...@oracle.com>
Subject Re: Code loaded through SQL.INSTALL_JAR does not have access to derby API code. Is this expected?
Date Mon, 25 Jul 2011 18:47:32 GMT
"Bergquist, Brett" <BBergquist@canoga.com> writes:

> I found some information. I found that if I include my JAR file
> containing my Restricted Table code in the classpath before starting
> the network server, then the code can load correctly and it has access
> to the "org.apache.derby.vti.RestrictedVTI" class and others. If
> however the code is loaded through the SQLJ.INSTALL_JAR procedure,
> then the code does not have access to the
> "org.apache.derby.vti.RestrticedVTI" class or others.
>
> Is this expected? I really would like to be able to install my table
> function code to be in the database and not have to manipulate the
> classpath. No where in the documentation does it say that this cannot
> be done, but it does not work.
>
> Should I write up an issue in JIRA?

I think this is intended to work, so a JIRA issue would be in order.

This bug looks somewhat related:
https://issues.apache.org/jira/browse/DERBY-4126

In that bug, we had to make the VTICosting interface available for the
procedures. I guess we'll need a similar trick for RestrictedVTI.

-- 
Knut Anders

Mime
View raw message