Problem with IBM JDK1.4.2, UNIX and Saxon8
Added by Anonymous almost 20 years ago
Legacy ID: #2990878 Legacy Poster: ozink (ozink)
We have a problem running JDK 1.4.2 and XSLT processor Saxon 8. We are using Java(TM) 2 Runtime Environment, Standard Edition (build 1.4.2) on IBM AIX and the Saxon 8 XSLT processor. During a process our J2EE-Application throws an excepition. This exception is reproduceable starting Saxon with commandline. The exception: java.lang.NullPointerException at com.ibm.nio.cs.SBCS_Encoder.canEncode(SBCS_Encoder.java:198) at net.sf.saxon.charcode.UnknownCharacterSet.inCharset(UnknownCharacterSet.java:46) at net.sf.saxon.charcode.CharacterSetFactory.makeCharacterSet(CharacterSetFactory.java:85) at net.sf.saxon.charcode.CharacterSetFactory.getCharacterSet(CharacterSetFactory.java:29) at net.sf.saxon.event.Emitter.setOutputProperties(Emitter.java:87) at net.sf.saxon.event.ResultWrapper.getReceiver(ResultWrapper.java:175) at net.sf.saxon.Controller.changeOutputDestination(Controller.java:548) at net.sf.saxon.Controller.transformDocument(Controller.java:1538) at net.sf.saxon.Controller.transform(Controller.java:1349) at net.sf.saxon.Transform.processFile(Transform.java:733) at net.sf.saxon.Transform.doMain(Transform.java:437) at net.sf.saxon.Transform.main(Transform.java:66) Fatal error during transformation: null The commandline arguments: /usr/java14/bin/java -jar /apps/lib/saxon8.jar -o /home/xvabc/out.xml /home/xvabc/druck.xml /home/xvabc/druck.xsl The druck.xml file: <?xml version="1.0" encoding="UTF-8"?> <Druck> <Antwort> Test </Antwort> </Druck> The druck.xsl file: <?xml version="1.0" encoding="UTF-8"?> <xsl:stylesheet version="1.0" xmlns:xsl="http://www.w3.org/1999/XSL/Transform"> <xsl:output method="text" encoding="windows-1252"/> <xsl:template match="/"> <xsl:value-of select="Druck/Antwort"/> </xsl:template> </xsl:stylesheet> The Exception is only reproduceable with the IBM JDK on IBM AIX. In the development we use Windows Clients (Win2000) and the SUN JDK.
Replies (1)
RE: Problem with IBM JDK1.4.2, UNIX and Saxon - Added by Anonymous almost 20 years ago
Legacy ID: #2990947 Legacy Poster: Michael Kay (mhkay)
Please report this as a bug on the IBM JDK: it's crashing in their code. In the meantime I suggest you try a different character encoding, such as iso8859-1, which is very similar and more portable. It's quite possible that even if IBM fix this bug, the result will only be an error message that says the JVM doesn't support the requested encoding. Michael Kay http://www.saxonica.com/
Please register to reply