I opened JIRA issue:
https://issues.apache.org/jira/browse/DERBY-5352
Note that this is also a problem with code implementing the VTICosting
interface. I think the problem is in JarLoader in the code:
// Classes in installed jars cannot reference
// Derby internal code. This
So it seems that DERBY-2331 disables access to org.apache.derby.* namespace
but the comment says except for public apis. It seems to me that the
RestrictedVTI and VTICosting are public API's now.
From: Bergquist, Brett [bbergqu...@canoga.com]
Sent:
So in UpdateLoader.java there is:
private static final String[] RESTRICTED_PACKAGES = {
// While loading java. classes is blocked by the standard
// class loading mechanism, javax. ones are not. However
// allowing database applications to override jvm classes
Bergquist, Brett bbergqu...@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
