Ask user to check if those machines have the same set up and versions of JDK or server to run the program. Usually a lot of problems came from the incompatibility between different versions of tools and supporting files. For example, the default encoding for JDK 1.3 is set to ISO-8859-1, for JDK1.4, the default encoding changed to ASCII. Sometimes it needs programmer to explicitly specify the encoding used in program. Therefore, same code may have different behavior under different environment.
Just 2 cents thought.
- Daniel Zhang
Joseph R. McVerry wrote:
Lately I have had several users report that their XML parsers are getting exceptions related to codepage mismatch. One example, below, the Crimson parser doesn't like the codepage as defined in the dtd. The code page in the document says "ISO-8859-1"; Crimson wants Cp1252.
"Warning at (file null, line 1, char -1): org.apache.crimson.parser/P-061 ISO-8859-1 Cp1252 Exception Message: Fatal Error at (file null, line 2, char -1): org.apache.crimson.parser/P-055 envelopeRules.dtd
All this user did was move the document from one machine to another. As with all unsightly bugs, the parser runs fine on the first machine.
BTW, this isn't related just to Crimson. I've seen similar reports from other Java/XML parsers.
Is this because the codepage is not loaded on his apache machine?
Should I specify a more generic code page? Presently it's ISO-8859-1, which I thought was as generic as codepages get.
Any help and tips would be appreciated.
Joe McVerry
_______________________________________________ Juglist mailing list [EMAIL PROTECTED] http://trijug.org/mailman/listinfo/juglist_trijug.org
