[ 
https://issues.apache.org/jira/browse/SOLR-260?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12503678
 ] 

Hoss Man commented on SOLR-260:
-------------------------------

a few more thoughts...
1) instead of DEFAULT_PACAKGES that should really be "String[] 
getDefaultPackages()" method that could be overridden in subclasses (anonymous 
or otherwise)
2) there's really no reason for the createInstance methods i put in 
NamedListPluginLoader and MapPluginLoader ... if a special case comes along 
where a special type of plugin requires a special type of instantiation, people 
can take care of it by overriding getInstance.

> reusable PluginLoader -- helper class to load plugins
> -----------------------------------------------------
>
>                 Key: SOLR-260
>                 URL: https://issues.apache.org/jira/browse/SOLR-260
>             Project: Solr
>          Issue Type: New Feature
>            Reporter: Ryan McKinley
>
> As we talk about adding more configuration (Handlers, Highlighting, 
> Components, etc) we should standardize the format and share the loading and 
> initialization code.
> This patch extracts the common stuff from SOLR-225 and makes it work with the 
> RequestHandler framework.
> This is an abstract base class -- each implementation needs to take care of 
> actually creating and initializing the instances:
> abstract class PluginLoader<T>
> {
>   abstract public T create( String className, NamedList args, 
> Map<String,String> params );
>  
>   abstract public void init( T plugin, NamedList args, Map<String,String> 
> params );
>   
>   public Map<String,T> load( NodeList nodes )
>   {
>     ...
>   }
> }

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

Reply via email to