Mailing-List: contact dev-help@lucene.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@lucene.apache.org
Date: Mon, 2 Apr 2012 02:16:29 +0000 (UTC)
From: "Mike Sokolov (Issue Comment Edited) (JIRA)" <jira@apache.org>
To: dev@lucene.apache.org
Message-ID: 
 <389336273.4172.1333332989807.JavaMail.tomcat@hel.zones.apache.org>
Subject: [jira] [Issue Comment Edited] (SOLR-1758) schema definition for
 configuration files (validation, XSD)
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Mike Sokolov edited comment on SOLR-1758 at 4/2/12 2:15 AM:
------------------------------------------------------------

Jan, I agree that keeping the schemas in the WAR would be more convenient for most cases.  I would usually put something like this in WEB-INF/classes so it is easy to retrieve using the ClassLoader.getResource method, but I'm not completely sure how to do this in the solr build?  Are there any other non-classes resources packaged that way?  The other option would be to place the file in the solr/webapp/web folder somewhere and could be loaded using the ServletContext.  And in this case, should it be visible as part of the webapp?  Or hidden at the top level in WEB-INF?  Seems to make sense to expose it as documentation (the main virtue of putting it in the conf folder).

Also it still might be useful to be able to override with a schema in the conf folder? 

I'll look into migrating this stuff to trunk.
                
      was (Author: sokolov):
    Jan, I agree that keeping the schemas in the WAR would be more convenient for most cases.  I would usually put something like this in WEB-INF/classes so it is easy to retrieve using the ClassLoader.getResource method, but I'm not completely sure how to do this in the solr build?  Are there any other non-classes resources packaged that way?  The other option would be to place the file in the solr/webapp/web folder in the source tree; then it would end up (I think) in WEB-INF, and could be loaded using the ServletContext.  Or maybe it should actually be made visible via the solr webapp?

Also it still might be useful to be able to override with a schema in the conf folder? 

I'll look into migrating this stuff to trunk.
                  
> schema definition for configuration files (validation, XSD)
> -----------------------------------------------------------
>
>                 Key: SOLR-1758
>                 URL: https://issues.apache.org/jira/browse/SOLR-1758
>             Project: Solr
>          Issue Type: New Feature
>            Reporter: Jorg Heymans
>              Labels: configuration, schema.xml, solrconfig.xml, validation, xsd
>             Fix For: 4.0
>
>         Attachments: config-validation-20110523.patch
>
>
> It is too easy to make configuration errors in Solr without getting warnings. We should explore ways of validation configurations. See mailing list discussion at http://search-lucene.com/m/h6xKf1EShE6

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org