lucene-solr-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Luke Forehand (JIRA)" <j...@apache.org>
Subject [jira] Commented: (SOLR-1408) Allow classes from ${solr.home}/lib to be loaded by the same classloader as solr war to prevent ClassCastException
Date Fri, 04 Sep 2009 15:08:57 GMT

    [ https://issues.apache.org/jira/browse/SOLR-1408?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12751487#action_12751487
] 

Luke Forehand commented on SOLR-1408:
-------------------------------------

This is also happening when I try to extend EventListener, I get the mysterious ClassCastException
from within Solr.  I am running solr from a jetty server, specifying solr.home using JNDI,
and I am starting the jetty server from within a unit test for integration testing purposes.

> Allow classes from ${solr.home}/lib to be loaded by the same classloader as solr war
to prevent ClassCastException
> ------------------------------------------------------------------------------------------------------------------
>
>                 Key: SOLR-1408
>                 URL: https://issues.apache.org/jira/browse/SOLR-1408
>             Project: Solr
>          Issue Type: Improvement
>          Components: contrib - DataImportHandler
>    Affects Versions: 1.3
>            Reporter: Luke Forehand
>
> When extending org.apache.solr.handler.dataimport.DataSource, I would like to package
my extended class in ${solr.home}/lib to that I can keep the vanilla copy of my solr.war intact.
 The problem is I encounter a ClassCastException when Solr tries to create a newInstance of
my extended class, which I suspect has to do with the DataSource and my extended class being
loaded from different classloaders.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message