xml-xalan-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From bugzi...@apache.org
Subject DO NOT REPLY [Bug 27516] - Xalan-J 2.5.2 fails reading Encoding.properties
Date Mon, 08 Mar 2004 15:43:46 GMT
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://issues.apache.org/bugzilla/show_bug.cgi?id=27516>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

http://issues.apache.org/bugzilla/show_bug.cgi?id=27516

Xalan-J 2.5.2 fails reading Encoding.properties





------- Additional Comments From verdy_p@wanadoo.fr  2004-03-08 15:43 -------
Additional information from my Java settings, if this interests you.
This is the environment I get when reverting to version 2.5.1 of xalan.jar just 
copied into my ant/lib directory where I uses JUnitReport:

#---- BEGIN writeEnvironmentReport($Revision: 1.20 $): Useful stuff found: ----
version.DOM.draftlevel=2.0fd
java.class.path=e:\ant\lib\xalan.jar
version.JAXP=1.1 or higher
java.ext.dirs=C:\j2sdk1.5.0\lib\ext
version.xerces2=Xerces-J 2.6.1
version.xerces1=not-present
version.xalan2_2=Xalan Java 2.5.1
version.xalan1=not-present
version.ant=not-present
java.version=1.5.0-beta
version.DOM=2.0
version.crimson=not-present
sun.boot.class.path=C:\j2sdk1.5.0\lib\rt.jar;C:\j2sdk1.5.0\lib\i18n.jar;C:\j2sdk
1.5.0\lib\sunrsasign.jar;C:\j2sdk1.5.0\lib\jsse.jar;C:\j2sdk1.5.0\lib\jce.jar;C:
\j2sdk1.5.0\lib\charsets.jar;C:\j2sdk1.5.0\classes
#---- BEGIN Listing XML-related jars in: foundclasses.java.class.path ----
xalan.jar-path=e:\ant\lib\xalan.jar
#----- END Listing XML-related jars in: foundclasses.java.class.path -----
version.SAX=2.0
version.xalan2x=Xalan Java 2.5.1
#----- END writeEnvironmentReport: Useful properties found: -----
# YAHOO! Your environment seems to be OK.

This environment works fine like this, but JunitReport fails to initialize its 
HTML output formater if I just replace xalan.jar with the newer version.
Shamely the default failure message is not very helpful to see what's 
happening. I had difficulties to isolate this problem, thinking first that this 
was a problem with Xerces (because also I can't use Xerces2 which changed its 
default behavior when handling namespaces, notably for unbound namespace 
prefixes found in various XML documents, notably for common XML namespace 
prefixes like "xsi:")

May be I should post another RFE as well for Xerces2, so that an application 
that instanciates a DOMParser can add a list of default bindings for namespace 
prefixes. For now I still need to use Xerces1, which shamely is no more 
supported, even though there was a upgrade compatibility problem for 
wellformness of XML documents (many XML documents use undeclared namespace 
prefixes, assuming that they are known to the application that uses the result 
of the DOM parser, and do not need to validate the document with a schema or 
DTD). This is a problem with LOTS of XML 1.0 documents in which the colon was 
acceptable as part of attribute names, element names, processing instruction 
names, etc, for which namespaces support was not a requirement... This means 
that Xerces2 can't be used with many _VALID_ XML 1.0 documents (these documents 
are invalid only with XML 1.1, but not if the documents are declared with a 
explicit XML version="1.0" declaration).

Mime
View raw message