db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Rick Hillegas (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (DERBY-6600) Make the Lucene plugin use the database class path to resolve ANALYZERMAKERs and QUERYPARSERMAKERs
Date Fri, 06 Jun 2014 18:02:01 GMT

    [ https://issues.apache.org/jira/browse/DERBY-6600?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14020142#comment-14020142
] 

Rick Hillegas commented on DERBY-6600:
--------------------------------------

I have tried loading the Lucene jar files themselves into the database. The plugin will not
run in this configuration. I believe that is because the class loader for code in derbyoptionaltools.jar
is unable to see classes which are only visible to the class loader bound to derby.database.classpath.
I have tried to also load derbyoptionaltools into the database. Same problem. It may be that
any class in the org.apache.derby namespace must be resolved by the JVM class path and cannot
refer to classes only visible to the class loader bound to derby.database.classpath.

So, for the moment, users must be content with the advice given in the user documentation:
Put derbyoptionaltools.jar on the JVM class path alongside the other Derby jars, and put the
Lucene jars there too.

> Make the Lucene plugin use the database class path to resolve ANALYZERMAKERs and QUERYPARSERMAKERs
> --------------------------------------------------------------------------------------------------
>
>                 Key: DERBY-6600
>                 URL: https://issues.apache.org/jira/browse/DERBY-6600
>             Project: Derby
>          Issue Type: Bug
>          Components: SQL
>            Reporter: Rick Hillegas
>            Assignee: Rick Hillegas
>         Attachments: derby-6600-01-aa-useDBclasspath.diff, derby-6600-02-aa-addAPIpackage.diff
>
>
> You get a ClassNotFoundException if you try to use an Analyzer or a QueryParser stored
in a jar file in the database. This is probably easy to fix: the class resolution needs to
use the database class loader.



--
This message was sent by Atlassian JIRA
(v6.2#6252)

Mime
View raw message