RE : Xerces 2 release date?

[Andy Clark <an...@cyberneko.net>]

Sam,
 
The first couple errors that I see are because the Turbine Torque folks
are importing xerces.framework.XMLParser even though it's not used in
that particular source file. This should be easy to fix. And from this
internet cafe I really can't check to see why the security build is
failing (but the second one builds correctly now, it looks like). It
would be great if someone could set the PRINT_STACK_EXCEPTION debugging
flag to true in the StandardParserConfiguration and re-run the build so
we determine the real source of the problem.
 
-AndyC

	-------- Message d'origine-------- 
	De: Sam Ruby 
	Date: lun. 21/01/2002 18:32 
	À: xerces-j-dev@xml.apache.org 
	Cc: turbine-dev@jakarta.apache.org; security-dev@xml.apache.org 
	Objet: Re: Xerces 2 release date?
	
	

	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: xerces-j-dev-unsubscribe@xml.apache.org
	For additional commands, e-mail:
xerces-j-dev-help@xml.apache.org