[ http://issues.apache.org/jira/browse/XALANJ-1814?page=all ]

Brian Minchau updated XALANJ-1814:
----------------------------------

    Fix Version: 2.7

> Xalan-J 2.5.2 fails reading Encoding.properties
> -----------------------------------------------
>
>          Key: XALANJ-1814
>          URL: http://issues.apache.org/jira/browse/XALANJ-1814
>      Project: XalanJ2
>         Type: Bug
>   Components: Serialization
>     Versions: 2.5
>  Environment: Operating System: Windows XP
> Platform: PC
>     Reporter: Philippe Verdy
>     Assignee: Bhakti H. Mehta
>      Fix For: 2.7

>
> Xalan-J 2.5.2 fails to initialize correctly when called from JUnitReport in a 
> ant build file.
> For some mysterious reasons, it fails to setup the serialization TextStream, 
> when it attempts to initialize its supported encoding.
> In ant, it produces an Initializer exception, and debug/verbose output 
> indicates that this is caused by attempting to parse an integer from a string 
> which really is part of a comment indicating the HTTP url of the IANA charset 
> database.
> This string should not be parsed as an integer, and it seems that the XalanJ 
> uses its own code to parse a encoding.properties file embedded in xalan.jar, 
> and forgets to ignore comment lines.
> The problem is when parsing this line in the jar-embedded 
> Encodings.properties. 
> This bug occurs at least when using the newer Java 1.5, as if comment lines 
> in 
> properties files were no more detected (possibly a problem of text format for 
> this properties file)
> Reverting to XalanJ 2.5.1 solves this problem. Something has changed in the 
> way 
> Xalan initialize its supported encodings, or something is already bogous in 
> XalanJ 2.5.1 even though its codepath currently does not read its embedded 
> Encoding.properties file which also contains comment lines.
> Note that the Encoding.properties file is not the same between XalanJ 2.5.1 
> and 
> XalanJ 2.5.2, that's why I think it's a problem of text format for the 
> properties file embedded in XalanJ 2.5.2 (a Mac format? a Unix format which 
> parses incorrectly under Windows?)

-- 
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


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

Reply via email to