[
https://issues.apache.org/jira/browse/SOLR-2490?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13050648#comment-13050648
]
Hoss Man commented on SOLR-2490:
--------------------------------
hmmm...
i don't think we should do this.
the request handler as written is total agnostic to what the properties are or
how they are being written out -- it just builds up the response and lets the
writer take care of it. As noted the XmlResponseWriter does in fact output the
newline.
if PropertiesRequestHandler tried to specially encode any (or all) properties
with whitespace in them, that would screw up clients that were treating the
whitespace as significant when parsing the xml -- and worse it would royally
screw up clients using other response writers where whitespace is always
significant.
> PropertiesRequestHandler; encode line.separator
> -----------------------------------------------
>
> Key: SOLR-2490
> URL: https://issues.apache.org/jira/browse/SOLR-2490
> Project: Solr
> Issue Type: Improvement
> Components: web gui
> Reporter: Stefan Matheis (steffkes)
> Priority: Trivial
>
> Currently, the XML looks like this:
> {code}<!-- .. -->
> <str name="java.io.tmpdir">/tmp</str>
> <str name="line.separator">
> </str>
> <str name="java.vm.specification.vendor">Sun Microsystems Inc.</str>
> <!-- .. -->{code}
> would be good to have this instead:
> {code}<!-- .. -->
> <str name="java.io.tmpdir">/tmp</str>
> <str name="line.separator">\n</str>
> <str name="java.vm.specification.vendor">Sun Microsystems Inc.</str>
> <!-- .. -->{code}
> afterwords we will be able to display to used line seperator
--
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
