[
https://issues.apache.org/jira/browse/SOLR-17?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12790910#action_12790910
]
Shalin Shekhar Mangar commented on SOLR-17:
-------------------------------------------
Chris, it seems that you are taking my comment personally. Please don't; it is
not my intention to ridicule anyone's efforts.
As you can see, this issue has been open for some time now and a major reason
is that we have never found a good use for an XSD. I'm merely trying to say
that it seems like we're trying to _find_ use-cases for a solution instead of
starting with an actual need.
My point is that Solr can use it we _want_ to but Solr certainly does not
_need_ to use it. I don't think we gain much by an XSD.
> 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-complex.xml, solr-rev2.xsd, solr.xsd,
> UselessRequestHandler.java
>
>
> 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.
-
You can reply to this email to add a comment to the issue online.
