[
https://issues.apache.org/jira/browse/DERBY-6600?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Rick Hillegas updated DERBY-6600:
---------------------------------
Attachment: derby-6600-02-aa-addAPIpackage.diff
Attaching derby-6600-02-aa-addAPIpackage.diff. This patch makes it possible to
register functions against the methods in Derby's Lucene api package:
org.apache.derby.optional.api. I am running tests now.
Touches the following files:
------------------------
M java/engine/org/apache/derby/impl/sql/compile/StaticMethodCallNode.java
Allow class references in org.apache.derby.optional.api to be resolved.
------------------------
M
java/testing/org/apache/derbyTesting/functionTests/tests/lang/LuceneJarLoadingTest.java
Add a test case for this.
> 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)
