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

Erik Hatcher commented on SOLR-620:
-----------------------------------

As for the duplication - I agree.... really all I'm after is getting an example 
configuration, much like data import handler (which also duplicates an entire 
configuration, mostly).  All this VelocityResponseWriter needs is to be 
registered in solrconfig.xml (where's Spring when you need it, such that 
dropping in a JAR is all that is needed to wire in a new component?! ;)   
Suggestions on improving, or just hardwire it into the default example config, 
are welcome?

Regarding Velocity template location, Velocity has a very flexible resource 
loader mechanism.  Right now it's hardcoded to use the custom parameter loader 
(&template.<template name>=<body>) or the file system.  Just wiring in the 
built-in classpath resource loader won't be enough... we need a 
SolrResourceLoader pass-through to pick up templates in JAR files in conf/lib - 
that'll be real handy.

I'll work on the JAR loading capability, shouldn't be too hard to toss in there.

> Velocity Response Writer
> ------------------------
>
>                 Key: SOLR-620
>                 URL: https://issues.apache.org/jira/browse/SOLR-620
>             Project: Solr
>          Issue Type: New Feature
>          Components: search
>    Affects Versions: 1.3
>            Reporter: Erik Hatcher
>            Assignee: Erik Hatcher
>            Priority: Minor
>         Attachments: SOLR-620.patch, SOLR-620.patch, SOLR-620.patch, 
> SOLR-620.patch, SOLR-620.zip, SOLR-620.zip
>
>
> Add a Velocity - http://velocity.apache.org - response writer, making it 
> possible to generate a decent search UI straight from Solr itself.  Designed 
> to work standalone or in conjunction with the JSON response writer (or 
> SolrJS) for Ajaxy things.

-- 
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