Andy Clark wrote: > > We're trying to have a production release of Xerces2 by the > end of this month.
IMHO, that would be premature. Take a look at http://nagoya.apache.org/~rubys/gump/xerces2/index.html . I've tried to encourage the Turbine team to work with the Xerces team to find a set of APIs that can enable them to smoothly make the transition from Xerces 1 to Xerces 2. At the moment, it looks like the JAXP interfaces may not be sufficient, and the Xerces specific APIs changed too much. For more details, see http://marc.theaimsgroup.com/?l=turbine-dev&m=101044066232727&w=2 http://nagoya.apache.org/~rubys/gump/xerces2/jakarta-turbine-torque.html Also, the xml-security subproject unit tests which pass with Xerces 1 cause failures inside the parser with Xerces 2. http://nagoya.apache.org/~rubys/gump/xerces2/xml-security.html http://nagoya.apache.org/~rubys/gump/base/xml-security.html - Sam Ruby -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
