APEX Listener 2.0.1 released

This has escaped my attention: since the beginning of March there is a new bug fix version of the APEX Listener 2.0 available for download. The latest version is now 2.0.1 and it contains the following bug fixes:

  • Support the handling of responses around 32KB in size on Oracle 10.2 database
  • Handling of large identifiers that prevented some RESTful Services being found or dispatched
  • Change the behaviour of BDB storage, each restart of listener gets it’s own folder for BDB storage, allowing multiple (e.g. clustered) nodes to share a single configuration folder, without getting an error
  • JSON streams not being parsed as UTF-8 encoded text
  • Dispatching of RESTful Services was causing a 404 not found exception when more than one database was configured
  • Improved the handling of Media Resources that are generated from large XMLType values
  • Fixed 503 Service Unavailable statuses generated by the PL/SQL Gateway to be mapped to a 404 Not Found status
  • Improve the error message generated when the icap.server/icap.port settings are misconfigured
  • PDF printing not handling results & XSL that totalled over 32766 bytes in size
  • RESTful Service Media Resource source type, that was preventing CLOBs over 4000 bytes in size from being returned without error
  • Handling of the icap.server and icap.port configuration settings
  • Virus scanning of empty and very small files
  • Debug.debugger configuration setting not working properly
  • Class loading in Standalone Mode was preventing FOP (PDF) printing working
  • Reporting of connection pool usage statistics

It’s cool that PDF printing now supports results that are over 32 kB in size, and also that there is now reporting available on the connection pool usage.

Maybe it’s time to upgrade the APEX Listener on our production environment :-)



3 Responses to APEX Listener 2.0.1 released

  1. fateh says:

    Hello Matthias,
    Can we use Apex Listener 2.0.1 as print server to print custom layout report. ??
    When I used the listener as print server, I was able to print IR report as PDF, but when I tried to print customed report layout, I get corrupted PDF file. Am I missing something ? or we Apex Listener 2 does not server us in this case ?

    Best Regards,

    • matthiashoys says:

      Sorry, I haven’t tried yet what you are doing. We are still using Apache FOP for PDF printing. Maybe you could ask your question on the OTN forum for the APEX Listener? https://forums.oracle.com/forums/forum.jspa?forumID=858. I noticed that there is a thread where high-ascii characters are involved. Do you have any special accented characters in your text?


      • fateh says:

        Hello Matthias,
        Thanks for the reply, I got the answer from Marc:
        APEX Listener 2.0 and up can be used as a print server for APEX and provides the same level of functionality that you would get when configuring the FOP based printing setup, i.e. you can use generic report layouts and XSL-FO based report layouts, but not RTF based report layouts. Also, Interactive Reports currently only support generic layouts, no custom layouts.


Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s

%d bloggers like this: