[ http://issues.apache.org/jira/browse/JCR-367?page=comments#action_12418261 ]
Felix Meschberger commented on JCR-367: --------------------------------------- > did you test with jre 1.4. and jre 1.5? Hmm, no, but as the new code relies on JAXP, which is part of the J2SE API since 1.4. I assume, this code is correct in both 1.4 and 1.5 I have to assume, right ? Correct me if I am wrong. > (e.g. performance, memory consumption, different jre's) Performance ? Don't know whether Xerces Serializer is faster or slower than JAXP. Do I have to care in this special case of import and export, whether it takes 1 or 2 ms longer or not ? Memory Consumption ? I assume removing and not using a library which has a file size of almost 1MB is a big plus in this regard, right ? But you are right, I did not crosscheck whether the serialization takes more or less memory. Is this kind of test a requirement for fixes ? Different JREs ? As I said JAXP is part of the J2SE API and runtime hence I assume this to be working. I have to, as I have confidence in Sun - else I could not even use the java.lang.String class :-) > Remove dependency on Xerces > --------------------------- > > Key: JCR-367 > URL: http://issues.apache.org/jira/browse/JCR-367 > Project: Jackrabbit > Type: Improvement > Components: xml > Reporter: Michael Young > Attachments: No_Xerces_Patch.fm.20060627.patch > > Classloaders in certain J2EE servers do not play well with the Xerces > requirement -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
