You are viewing a plain text version of this content. The canonical link for it is here.
Posted to solr-dev@lucene.apache.org by "Thorsten Scherler (JIRA)" <ji...@apache.org> on 2007/02/06 13:25:06 UTC
[jira] Created: (SOLR-144) Harmonizing different XML technologies
and their usage in Solr
Harmonizing different XML technologies and their usage in Solr
--------------------------------------------------------------
Key: SOLR-144
URL: https://issues.apache.org/jira/browse/SOLR-144
Project: Solr
Issue Type: Task
Reporter: Thorsten Scherler
Resulting out of some comments in SOLR-133, we should harmonize our usage of different xml technologies.
IMO we should move to StAX, since it is an upcoming standard and in comparison to SAX easier to use.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Resolved: (SOLR-144) Harmonizing different XML technologies
and their usage in Solr
Posted by "Ryan McKinley (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SOLR-144?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Ryan McKinley resolved SOLR-144.
--------------------------------
Resolution: Fixed
Fix Version/s: 1.3
Currenty there we have two cases where we parse xml:
# config files
# /update messages
All config files are parsed using the registered XML parser for {{XPathFactory.newInstance()}}
XML processing for XmlUpdateHandler are processed via StAX
This is not *unified*, but I think reasonable. If we want to switch the xml parsing technique for config, lets open a new issue for that.
> Harmonizing different XML technologies and their usage in Solr
> --------------------------------------------------------------
>
> Key: SOLR-144
> URL: https://issues.apache.org/jira/browse/SOLR-144
> Project: Solr
> Issue Type: Task
> Reporter: Thorsten Scherler
> Fix For: 1.3
>
>
> Resulting out of some comments in SOLR-133, we should harmonize our usage of different xml technologies.
> IMO we should move to StAX, since it is an upcoming standard and in comparison to SAX easier to use.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.