[
https://issues.apache.org/jira/browse/JCR-1312?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12559856#action_12559856
]
Jukka Zitting commented on JCR-1312:
------------------------------------
> > Jackrabbit is not an XML parser project.
> Definitely agreed on that one.
And yet you're proposing to add 350+ LOC with no other purpose than XML
parsing. The code is nontrivial and I'm certainly not convinced that it doesn't
have bugs or doesn't overlook some DOM semantics that we may or may not rely
on.
> IMHO given advantages (memory footprint (1% of Xerces) and performance
> (40-60% of Xerces)) this is probably a small price to pay :-)
I don't agree. JCR-1310 is a better way to drop the Xerces jar and the
performance improvement is IMHO only relevant if it translates to real-world
use cases. I don't see that happening here, especially in light of what Julian
and Ian said, but feel free to prove me otherwise.
I'd resolve this as Won't Fix.
> 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.
