I asked this nearly two months ago, and got:

>I'm all for it but just don't have time at the moment. Once I
>get a good beta candidate ready we'll be in better shape to
>flip the switch.

On the off chance that it might help encourage people to start thinking
about the issues, I just did a test run - same sources compiled first with
Xerces 1 and then with Xerces 2.  You can see the results at:

http://nagoya.apache.org/~rubys/gump/xerces1/
http://nagoya.apache.org/~rubys/gump/xerces2/

Analysis:

   Compilation failures:

     xml-xalan2

   Runtime failures with xerces2 but not present in xerces1:

     xml-axis

   Pre-existing problems, unrelated to Xerces

     bcel, openejb

   Failures due to indirect dependencies not being satisfied:

     test-ant, openjms

   Failures due to direct dependencies not being satisfied:

     too numerous to list

Recommendations:

   Clearly the compilation failure with xml-xalan2 is the one most blocking
   forward progress.  I personally make no assumptions as to whether this
   should be fixed in Xalan or Xerces, but it would be nice if this were
   resolved before Xerces 2 reaches a point where release candidates are
   produced.

   I've also attached below the XML from the xml-axis test case which
   Xerces 2 appears unable to parse.

   It only takes me a few minutes to set up this test, and about an hour to
   run (significantly less if there are massive prereq failures), so I can
   rerun these tests any time you guys are ready.

- Sam Ruby

XML from the xml-axis junit failure:

<?xml version="1.0"?>
<soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/"; 
xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/"; xmlns:xsi
="http://www.w3.org/2001/XMLSchema-instance"; 
xmlns:xsd="http://www.w3.org/2001/XMLSchema";>
<soap:Body>
<m:reverseData xmlns:m="urn:m"><arg0 
xmlns:foo="urn:foo"><field1>5</field1><field2>abc</field2><field3>3</field3></arg0></m:reverseData></soap:Body>
</soap:Envelope>


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to