2 Replies Latest reply: Apr 24, 2013 7:57 AM by Colm Divilly-Oracle RSS

    generate pdf with apex listener 2.0

    517154
      hi,
      we would like to generate pdf out of apex.
      as long as we have text (IRR) WITHOUT special characters (öäü), everything is working fine.
      when we have this characters in a text-columng (IRR), then we get a .pdf with the following content:

      javax.xml.transform.TransformerException: com.sun.org.apache.xml.internal.utils.WrappedRuntimeException: An invalid XML character (Unicode: 0x3) was found in the element content of the document.

      could this be a problem of the characterset? but if, where to change what?

      - we defined in ADMIN in 'report printing' / 'instance-settings': oracle-apex-listener
      - we are working with apex-listener 2.0 (integrated in weblogic-server)
      - we work with APEX 4.2.1.00.08

      thanks for any ideas
      roland

      Edited by: user514151 on 01.04.2013 23:24
        • 1. Re: generate pdf with apex listener 2.0
          mdyla
          I have this same problem with windows-1250 encoding.

          Invalid byte 1 of 1-byte UTF-8 sequence.
          com.sun.org.apache.xerces.internal.impl.io.MalformedByteSequenceException: Invalid byte 1 of 1-byte UTF-8 sequence.
               at com.sun.org.apache.xerces.internal.impl.io.UTF8Reader.invalidByte(UTF8Reader.java:687)
               at com.sun.org.apache.xerces.internal.impl.io.UTF8Reader.read(UTF8Reader.java:557)
               at com.sun.org.apache.xerces.internal.impl.XMLEntityScanner.load(XMLEntityScanner.java:1753)
               at com.sun.org.apache.xerces.internal.impl.XMLEntityScanner.skipChar(XMLEntityScanner.java:1426)
               at com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl$FragmentContentDriver.next(XMLDocumentFragmentScannerImpl.java:2754)
               at com.sun.org.apache.xerces.internal.impl.XMLDocumentScannerImpl.next(XMLDocumentScannerImpl.java:607)
               at com.sun.org.apache.xerces.internal.impl.XMLNSDocumentScannerImpl.next(XMLNSDocumentScannerImpl.java:116)
               at com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl.scanDocument(XMLDocumentFragmentScannerImpl.java:489)
               at com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(XML11Configuration.java:835)
               at com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(XML11Configuration.java:764)
               at com.sun.org.apache.xerces.internal.parsers.XMLParser.parse(XMLParser.java:123)
               at com.sun.org.apache.xerces.internal.parsers.AbstractSAXParser.parse(AbstractSAXParser.java:1210)
               at com.sun.org.apache.xerces.internal.jaxp.SAXParserImpl$JAXPSAXParser.parse(SAXParserImpl.java:568)
               at com.sun.org.apache.xerces.internal.jaxp.SAXParserImpl.parse(SAXParserImpl.java:302)
               at javax.xml.parsers.SAXParser.parse(SAXParser.java:195)
               at oracle.dbtools.apex.fop.FOPUtils.fop2pdf(FOPUtils.java:72)
               at oracle.dbtools.apex.hooks.postProcess.FOP2PDF.requestTOPDF(FOP2PDF.java:87)
               at oracle.dbtools.apex.hooks.postProcess.FOP2PDF.postProcess(FOP2PDF.java:49)
               at oracle.dbtools.apex.hooks.ProcessorRegistry.postProcess(ProcessorRegistry.java:56)
               at oracle.dbtools.apex.ModApex.handleRequest(ModApex.java:241)
               at oracle.dbtools.apex.ModApex.doGet(ModApex.java:98)
               at oracle.dbtools.apex.ModApex.service(ModApex.java:316)
               at oracle.dbtools.rt.web.HttpEndpointBase.modApex(HttpEndpointBase.java:260)
               at oracle.dbtools.rt.web.HttpEndpointBase.service(HttpEndpointBase.java:110)


          Any solution ?

          Regards
          md
          • 2. Re: generate pdf with apex listener 2.0
            Colm Divilly-Oracle
            Thank you for your problem reports, I have filed BUG:16715723 to track this issue, it will be addressed in the next patch release of Listener. In the meantime you can workaround this problem by forcing the JVM to use UTF-8 encoding, by adding the following flag to the startup command used to start the JVM
            -Dfile.encoding=UTF8
            For example to force standalone mode to start in UTF-8 mode do:
            java -Dfile.encoding=UTF8 -jar apex.war
            Consult your application server documentation for information on how to set this flag on your application server