[
https://issues.apache.org/jira/browse/SOLR-620?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12644491#action_12644491
]
Erik Hatcher commented on SOLR-620:
-----------------------------------
Ok, got your JAR loader in place. At this point, templates get found first in
params (&template.name=body), then the file system (either v.base_dir property
value, bad name I know, or conf/velocity), then the JARs. This gives
overridability down to the request level.
The one caveat to the JAR loader... it's actually just a front-end to
SolrResourceLoader#openResource(), so it can open files in the conf directory
(or via absolute path, it seems!), as well as from conf/lib/*.jar's and the
Solr classpath itself.
We'll make the Velocity properties more flexibly managed as we evolve this.
Templates on the file system really make the most sense to me, but we'll let
Velocity's flexibility shine through.
> 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.
