[
https://issues.apache.org/jira/browse/JCR-1312?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12559429#action_12559429
]
Jukka Zitting commented on JCR-1312:
------------------------------------
I still don't see why we should have the alternative DocumentBuilder
implemented within jackrabbit-webapp. JAXP already has a mechanism for
specifying which XML parser to use.
If there's a better XML parser available, then it should worry about
implementing DocumentBuilder and correctly handling all the associated DOM
semantics. I don't want to start seeing bug reports about "our" XML parser.
> 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.
