[
https://issues.apache.org/jira/browse/JCR-1312?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12559842#action_12559842
]
Felix Meschberger commented on JCR-1312:
----------------------------------------
> Jackrabbit is not an XML parser project.
Definitely agreed on that one.
> Why doesn't kxml come with the DocumentBuilder implementation?
Probably, they don't need it. But if you look at the patch, we are discussing
three classes:
* XmlPullDocumentBuilderFactory: A very simple class backed by a JAXP
DocumentBuilderFactory
* XmlPullDocumentBuilder: Also very simple, just one method of real
complication, of which the
most part is taken to guess the streams character encoding
* DOM2XmlPullBuilder: The actual builder converting Pull Events to DOM. This
class is copied
from xmlpull.org
* XmlPullDomSerializer: Straight forward and simple as well.
IMHO given advantages (memory footprint (1% of Xerces) and performance (40-60%
of Xerces)) this is probably a small price to pay :-)
> Get rid of DOM for XML support
> ------------------------------
>
> Key: JCR-1312
> URL: https://issues.apache.org/jira/browse/JCR-1312
> Project: Jackrabbit
> Issue Type: Improvement
> Components: jackrabbit-webdav
> Reporter: Felix Meschberger
>
> Currently the web dav library uses Xerces and DOM to parse and create XML
> data. This mechanism is well-known but has two major issues: It is slow and
> it has a big memory footprint. In order to solve these two issues, I suggest
> to drop the use of the W3C DOM in webdav in favor of something easier and
> more straight forward to use.
> One candidate could be (out of my head and based on my bias towards KXml)
> KDOM. See also http://www.kxml.org.ww
> See also JCR-1261 for more discussions on this issue.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
