[
https://issues.apache.org/jira/browse/SOLR-17?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13031847#comment-13031847
]
David Barnes commented on SOLR-17:
----------------------------------
Strongly second comment from Bill Bell. Working on a commercial project
integrating Solr 3.1.
Lack of an XSD is making integration with our business service back end a royal
pain.
We do have XSDs from all other 3rd parties we are integrating with. Using Solr
commons connector is not an option for us.
> XSD for solr requests/responses
> -------------------------------
>
> Key: SOLR-17
> URL: https://issues.apache.org/jira/browse/SOLR-17
> Project: Solr
> Issue Type: Improvement
> Reporter: Mike Baranczak
> Priority: Minor
> Attachments: SOLR-17.Mattmann.121709.patch.txt,
> UselessRequestHandler.java, solr-complex.xml, solr-rev2.xsd, solr.xsd
>
>
> Attaching an XML schema definition for the responses and the update requests.
> I needed to do this for myself anyway, so I might as well contribute it to
> the project.
> At the moment, I have no plans to write an XSD for the config documents, but
> it wouldn't be a bad idea.
> TODO: change the schema URL. I'm guessing that Apache already has some sort
> of naming convention for these?
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
