[ 
https://issues.apache.org/jira/browse/JCR-1261?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Felix Meschberger closed JCR-1261.
----------------------------------


Agreed. So I close this and created two new issues. JCR-1312.

Oops, I see angela just went ahead .... So I closed JCR-1311 in favor my own 
JCR-1312 and do nothing for the dropping Xerces.

> Replace Xerces/JAXP based (un)marshalling by KXml2 based implementation
> -----------------------------------------------------------------------
>
>                 Key: JCR-1261
>                 URL: https://issues.apache.org/jira/browse/JCR-1261
>             Project: Jackrabbit
>          Issue Type: Improvement
>          Components: jackrabbit-webdav
>    Affects Versions: 1.3.3
>            Reporter: Felix Meschberger
>            Assignee: Felix Meschberger
>         Attachments: JCR-1261.drop-xerces.patch, JCR-1261.patch, 
> JCR-1261_2.patch
>
>
> Proposing to replace the current Xerces/JAXP based implementation of XML data 
> unmarshalling and marshalling to be replaced by a MXP ([1]) based 
> implementation. MXP is an implementation of the XML PullParser API [2] and 
> provides a very mall footprint (120KB) and far better performance than Xerces 
> (my tests showed around 50% performance increase over Xerces for both 
> unmarshalling and marshalling, see also [3]).
> Why do I care ? I would like to include WebDAV functionality into Sling and 
> bundle is with as little dependencies as possible ( the xpp3 lib might even 
> be bundled into this project to minimize dependencies). In addition, I think 
> XML (un)marshalling performance is crucial in any WebDAV solution. For this 
> reason, this project can only win if we add a more performing library.
> [1] http://www.extreme.indiana.edu/xgws/xsoap/xpp/mxp1/
> [2] http://www.xmlpull.org
> [3] http://www.extreme.indiana.edu/~aslom/xpp_sax2bench/results.html

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

Reply via email to