DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT <http://nagoya.apache.org/bugzilla/show_bug.cgi?id=7463>. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE.
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=7463 Returning a null serializer ------- Additional Comments From [EMAIL PROTECTED] 2002-05-20 10:58 ------- Comment from orga.apache.xalan.serialize.CharInfo: // %REVIEW% KNOWN ISSUE: IT FAILS IN MICROSOFT VJ++, whichM // didn't implement the UTF-8 encoding. Theoretically, we shouldM // simply let it fail in that case, since the JVM is obviouslyM // broken if it doesn't support such a basic standard. ButM However, it seems to fail on many other setups as well. With Blackdown's port of Sun JDK 1.1.7 (Running XalanJ 2.3.1): java.lang.RuntimeException: The resource [ XMLEntities.res ] could not load: java.lang.IllegalArgumentException: sun.io.ByteToCharUTF-8 XMLEntities.res java.lang.IllegalArgumentException: sun.io.ByteToCharUTF-8 at org.apache.xalan.serialize.CharInfo.<init>(CharInfo.java:241) at org.apache.xalan.serialize.SerializerToXML.<init>(SerializerToXML.java:332) at org.apache.xalan.serialize.SerializerFactory.getSerializer(SerializerFactory.java:134) at org.apache.xalan.transformer.TransformerIdentityImpl.createResultContentHandler(TransformerIdentityImpl.java:232) at org.apache.xalan.transformer.TransformerIdentityImpl.transform(TransformerIdentityImpl.java:296) On a guess, I think this is your problem as well. Going still one layer deeper, the error becomes: java.lang.IllegalArgumentException: sun.io.ByteToCharUTF-8 at sun.io.ByteToCharConverter.getConverterClass(ByteToCharConverter.java) at sun.io.ByteToCharConverter.getConverter(ByteToCharConverter.java) at java.io.InputStreamReader.<init>(InputStreamReader.java) at org.apache.xalan.serialize.CharInfo.<init>(CharInfo.java:192) And the solution becomes catching both exceptions around line 194 of org.apache.xalan.serialize.CharInfo constructor. For most people telling them to just upgrade to a modern JDK/JRE would do, but there are certain embedded environments where running non-Java2 environment is preferable, or the only option. And the fix doesn't take much.
