Oracle Application Express Listener 2.0 Released

Oracle Application Express Listener version 2.0 is now available for download.

This release includes many new features including:

  • Support for multi tenant/multiple database connections

    In earlier releases, you could only configure one database connection per listener instance. With Release 2.0, you can configure multiple database connections. See “Configuring Multiple Databases” in the Oracle Application Express Listener Installation and Configuration Guide.

  • Use Oracle SQL Developer to administer Oracle Application Express Listener

    Oracle SQL Developer 3.2.2 is able to remotely administer Oracle Application Express Listener instances. Access the Administration interface by selecting View|APEX Listener from the SQL Developer main menu. See “Application Express Listener Administration” in the Oracle SQL Developer User Guide.

  • Use command line to configure Oracle Application Express Listener

    You can also configure Application Express Listener using the command line. See “About the Command-Line Interface” in the Oracle Application Express Listener Installation and Configuration Guide.

  • Resource Templates are now known as RESTful Services.

    The Resource Templates functionality has been enhanced and integrated with Oracle Application Express 4.2. Now known as RESTful Services, services are now defined using Oracle Application Express. See “Using RESTful Services” in the Oracle Application Express SQL Workshop Guide.

  • OAuth2 support for RESTful Services

    Oracle Application Express Listener now uses the recently finalized Open Authorization 2.0 (OAuth2) framework to secure access to resources generated using RESTful Services.

  • RESTful Services support Paging of results

    RESTful Services now support paging of results, enabling large result sets to be spread across many page resources instead of a single resource. The really nice thing about this feature is that the pagination can be done automatically simply by setting the pagination size to a non zero value on a Resource Handler. Alternatively if you need fine control over how pagination is done the Listener provides a number of implicit bind variables (:row_offset,:row_count,:page_offset,:page_size) that Resource Handlers can reference to customize how paging is done.

  • Cross Origin Resource Scripting (CORS) support

    RESTful Services support the Cross Origin Resource Sharing Specification. All public RESTful Services are automatically CORS enabled, this means any public RESTful Service can be accessed from any web origin via an XMLHttpRequest. For non public (protected) RESTful Services, Resource Handler definitions include a new Origins Allowed field that enables you to include a comma delimited list of other server names that are permitted to make cross origin requests to the RESTful Service.

  • RESTful Services Hyperlinks

    RESTful Services now support a mechanism for result sets to include hyperlinks to other resources.