What You See Is What You Get Element


Oracle REST Data Services 3.0.11.180.12.34


Release Notes

Date: July 2017


Oracle REST Data Services on OTN
| Downloads | Forum


Support

  • You are supported by Oracle Support under your current Oracle Database or Oracle NoSQL Database Support license for Oracle REST Data Services production releases.
  • Log Oracle REST Data Services bugs and issues using My Oracle Support.

    • For problems specific to SODA for REST, file a service request using "Oracle XML Developers Kit" as the product.
    • For all other problems, use "Oracle REST Data Services" as the product.

Documentation

  • Documentation for this release is provided on the OTN web site. Click here to view the documentation.
  • Documentation on using SODA for REST is provided on the OTN here.

Getting Started

  • A tutorial on getting started with developing RESTful Services is included in the product documentation, in the section titled 'Appendix E: Getting Started with RESTful Services'.
  • A tutorial on getting started with developing NoSQL RESTful Services is provided in this distribution, and can be viewed here.

Feedback

  • You can discuss issues on the forums.
    • Be sure to use clear subject lines to initiate a thread. Provide a complete and clear description of the issue, including steps to reproduce the issue.
    • Try to avoid using old, unrelated threads for a new issue.

Important Changes to Note

Excel worksheet to Application Express Collection upload feature removed

The facility to upload Excel Worksheets to Oracle Application Express collections has been removed. The facility is incompatible with Application Express 5.1. Concerns about the robustness of the library used to parse the Excel worksheets has forced removal of this feature from 3.0.10 and future releases.

APEX_PUBLIC_USER & wwv_flow_epg_include_modules.authorize

In line with security best practice and as recommended by the Oracle Application Express Documentation when a database pool is configured to use the APEX_PUBLIC_USER, Oracle REST Data Services will automatically set the value of the security.requestValidationFunction setting to be:

    WWV_FLOW_EPG_INCLUDE_MODULES.AUTHORIZE
  
This activates the white list of callable procedures which ships with Oracle Application Express and prohibits calls to other procedures. Please consult the Oracle Application Express Documentation for more information about this procedure and how to customize it's behaviour.

 

Extracting ORDS Scripts - Deprecated

The extract ords-scripts command is deprecated. Manual install, upgrade, validate and uninstall using SQL scripts will no longer be supported in ORDS future releases. Refer to Oracle REST Data Services documentation to install, upgrade, validate or uninstall Oracle REST Data Services.

Problems with Oracle Application Express Static Resources

A regression in APEX 5.0.3 and ORDS 3.0.3 prevents the proper functioning of APEX static resources and APEX based RESTful Services. Please upgrade to ORDS 3.0.4 to resolve this issue.

Using ORDS silent installation without specifying tablespaces

If you want to use the database default tablespaces (default and temporary tablespaces) for ORDS_METADATA schema and ORDS_PUBLIC_USER user when installing ORDS from the command line, you must install ORDS in silent (simple) mode and remove the following tablespace entries in your /path/to/params/ords_params.properties file:

schema.tablespace.default=SYSAUX
schema.tablespace.temp=TEMP
user.tablespace.default=USERS
user.tablespace.temp=TEMP

To install ORDS in silent (simple) mode using the database default tablespaces:

java -jar ords.war
java -jar ords.war install simple

404 Errors when configuring Oracle REST Data Services

There are two main causes of 404 - Not Found errors:

  • Using /ords instead of /ords/ (ORDS 3.0.0 only, fixed in 3.0.1 and later).

    Oracle REST Data Services is deployed at a context-root of /ords/, in previous versions there was logic to handle the case where a user accessed /ords instead of /ords/. In ORDS 3.0.0 this functionality was regressed, but it has been fixed in this release. If you access /ords your browser will be redirected to /ords/.

  • Not configuring the PL/SQL Gateway

    If you want to to use Oracle Application Express or you wish to access PL/SQL Stored Procedures, then you must enable the PL/SQL Gateway during the installation process.

    A quick way to check if you have completed this step is to check in the configuration folder if the file named: conf/apex.xml exists. If it does not exist then it implies that the PL/SQL Gateway was not configured.

    If you do not use Application Express then there will be no stored procedure available to serve the /ords/ resource. This means that accessing this URL will produce a 404 - Not Found status, this is expected.

    Use the misc.defaultPage configuration setting to specify the name of a PL/SQL procedure to serve the /ords/ resource. This must be a PL/SQL procedure that takes zero arguments, and uses Oracle Web Agent (OWA) APIs to produce a HTML response. This setting can be configured in SQL Developer under:

    View > REST Data Services > Administration

    and then when editing a configuration, under:

    REST Data Services > Environment > PL/SQL Gateway > Default Web Page

    If you don't wish to use Oracle Application Express or PL/SQL procedures then you do not need to configure the PL/SQL Gateway, however as explained above accessing /ords/ will always produce a 404 - Not Found status, since there is nothing to serve this resource, this is expected.

Standalone Mode Document Root

Standalone Mode can now serve aribtrary static resources via it's new document root feature. To see instructions on how to use the document root, use the help command:

  java -jar ords.war help standalone

  java -jar ords.war standalone [--port] [--apex-images] [--context-path] 
  [--static-context-path] [--doc-root] [--parameterFile]

  Launch Oracle REST Data Services in standalone mode

  Options:
             [--port]              HTTP listen port, default 8080

             [--apex-images]       Path to the folder containing
                                   static resources required by
                                   APEX

             [--context-path]      The context path where Oracle
                                   REST Data Services is
                                   located, defaults to /apex

             [--static-context-path]The Context path where
                                   Application Express static
                                   resources are located,
                                   defaults to /i

             [--doc-root]          Points to the location where
                                   static resources, to be
                                   served under the / root
                                   server path are located.

             [--parameterFile]     Specify the location of the
                                   parameter file to use.
                                   Defaults to
                                   params/ords_params.properties.

For example the following command would configure the document root to be /var/www/html:
  java -jar ords.war standalone --doc-root /var/www/html
  2015-06-16 22:33:19.899:INFO::main: Logging initialized @1253ms
  Jun 16, 2015 10:33:20 PM oracle.dbtools.standalone.StandaloneJetty setupDocRoot
  INFO: The document root is serving static resources located in: /var/www/html

The document root has the following features:

  • Files named index.html or index.htm are treated as welcome files, and are served in place of the folder resource that contains them.

    For example /var/www/html/index.html would serve as the resource for http://localhost:8080/

  • Files with a .html or .htm file extension are served without without their file extension.

    For example /var/www/html/docs/readme.html is served as: http://localhost:8080/docs/readme. If a client accesses http://localhost:8080/docs/readme.html, then the client will be redirected to http://localhost:8080/docs/readme.

Changes in 3.0.11

Issues Fixed in 3.0.11

The following changes and enhancements have been made since 3.0.10:
  • BUG:26372648 - Address regression causing 500 Internal Server error in ORDS 3.0.10 on Apache Tomcat 8.5 and later

New Features since 3.0.10

None

Changes in 3.0.10

Issues Fixed in 3.0.10

The following changes and enhancements have been made since 3.0.9:
  • BUG:26141329 - Remove Excel worksheet to Application Express Collection upload feature
  • BUG:25889314 - Improve performance of JSON serialization
  • BUG:25889943 - Uptake the latest Jetty release for Standalone Mode
  • BUG:25534690 - Fix regression that prevented disabling pagination at handler level in Application Express based REST Services
  • BUG:25477292 - Fix regression causing Apex-Session based First Party Authentication to fail
  • BUG:25712868 - Fix regression preventing POST operation on an AutoRest table which has a CLOB column

New Features since 3.0.9

Customers can now automatically enable RPC of PL/SQL objects via POST REST endpoints. The PL/SQL API and SQL Developer GUI is similar to what already exists for AUTO REST enabling tables and views. Overloaded package procedures and functions are not supported and attempting to execute them via AUTO PLSQL feature will result in a 404.

Changes in 3.0.9

Issues Fixed in 3.0.9

The following changes and enhancements have been made since 3.0.8:
  • BUG:25214859 - Fix regression causing ORA-01000 due to cursor leak when downloading files via PL/SQL Gateway
  • BUG:25072243 - Fix regression preventing url mapping of ORDS enabled schemas iff the PL/SQL Gateway pool does not exist
  • BUG:22447307 - Add missing ons.jar to ords.war

New Features since 3.0.8

None.

Changes in 3.0.8

Issues Fixed in 3.0.8

The following changes and enhancements have been made since 3.0.7:
  • BUG:23640212 - Fix regression preventing the externally authenticated user identity being propagated to the database via the REMOTE_USER CGI header variable

New Features since 3.0.7

None.

Changes in 3.0.7

Issues Fixed in 3.0.7

The following changes and enhancements have been made since 3.0.6:
  • BUG:24507612 - Fix regression preventing updating of an Application Express based OAuth Client Registration
  • BUG:24440967 - Address Connection resource leak that may occur under load.
  • BUG:24344949 - Show 503 Service unavailable status when database reports ORA-00018 Max Sessions Exceeded
  • BUG:24344949 - Retry request after jittered delay when database reports ORA-00018 Max Sessions Exceeded
  • BUG:23732108, BUG: 23732138 - Reduce overhead in dispatching all requests, improving performance.
The following changes and enhancements have been made to the Simple Oracle Document Access (SODA) functionality:
  • BUG:24450332 - Proper handling of 500 and 503 errors from ORDS. Now SODA JSON responses are returned, instead of ORDS responses.
  • BUG:24308373 - Support versioning in SODA URIs (version "v1" is supported, and is the only supported version at this time).

New Features since 3.0.6

  • ENH:24347162 - When PL/SQL Gateway uses APEX_PUBLIC_USER automatically add WWV_FLOW_EPG_INCLUDE_MODULES.AUTHORIZE to the security.requestValidationFunction setting

Changes in 3.0.6

Issues Fixed in 3.0.6

The following changes and enhancements have been made since 3.0.5:
  • BUG:23638987 - Fix regression causing APEX Based RESTful Services to fail if and only if the ORDS_PUBLIC_USER (???_pu.xml) connection pool is removed.
  • BUG:23625255 - Fix regression causing performance degradation due to unnecessary validation of database pools
  • BUG:23504343 - Fix the localization of the install help command
  • BUG:23347319 - Fix regression causing IllegalStateExecption when context path accessed without trailing slash
  • BUG:23291056 - Enable support for TLS 1.2 with JDBC connections, by upgrading to use the most recently available Oracle JDBC drivers for JDK 7
  • BUG:23314519 - Fix regression causing corruption of values in OWA CGI environment
The following change and enhancements have been made to the Simple Oracle Document Access (SODA) functionality:
  • BUG:23563847 - New default indexing mode: requires scalars, missing values allowed.
  • BUG:23500034 - Includes the following fixes:
    • New indexing modes: "scalarRequired", "lax".
    • Result limit applies to QBE queries as well as basics gets.
    • Order-bys and indexes no longer implicitly append [0] steps.
    • Rest error messages no longer hard-code "type" attribute to 400 code definition (correct definition now used).
  • BUG:23316761 - RestResponse needs to guard against null exception check.
  • BUG:23500034 - Includes the following fixes:
    • Fixes URI patterns issue for cloud.
    • Adds correct exception handling for future releases, in the case of deleting collection with uncommitted writes.
    • Fixes commit/rollback issues in SODA REST handler.
    • If-match headers (optimistic locking).

New Features since 3.0.5

None

Changes in 3.0.5

Issues Fixed in 3.0.5

The following changes and enhancements have been made since 3.0.4:
  • BUG:23146410 - Decrease per request overhead and improve database resource management
  • BUG:23084465 - Fix regression in handling of Integer OUT parameters
  • BUG:23081945 - Include Content-Length header when wpg_docload.download_file is used
  • BUG:23071135 - Fix problem with user defined RESTful Services conflicting with built in REST Services
  • BUG:23034547 - Fix problem with serving of HTML resources in Standalone Mode document root
  • BUG:23019615 - Fix Too Many Redirects problem when accessing ui/oauth2/clients/ over HTTPS
  • BUG:22983910 - Fix problem with ORDS reporting incorrect information to SQL Developer for RESTful Services Parameters marked as OUT
  • BUG:22909624 - Fix problem with processing of Content-Disposition filename attribute/li>
  • BUG:22909596 - Change behaviour to only produce filename* attribute if a value is not provided for it in a Content-Disposition response header
  • BUG:22891124 - Fix regression preventing the correct matching and dispatching of Route Patterns with the Optional Modifier
  • BUG:22851160 - Fix problem preventing execution of ords.enable_schema from Application Express SQL Workshop
  • BUG:22809620 - Fix problem with handling of a Resource Module with an empty base path
  • BUG:22763362 - Support use of owa_util.status_line in ORDS based PL/SQL REST Handlers
  • BUG:22665055 - Unable to run ORDS on non Oracle JDKs

New Features in 3.0.5

Standalone Mode HTTPS Support

Standalone Mode now supports HTTPS either by generating a self signed certificate or using a provided certificate. HTTPS can be configured using the installer when ORDS starts in standalone mode.

  • The default self signed certificate is valid for 365 days and will be regenerated if expired the next time ORDS is started.
  • If using an existing certificate, a DER encoded private key is required.
  • It is recommended to use Java 8 in order for Jetty to use the most recent cipher suites to establish secure connections.
  • Note: Self signed certificates will not be trusted by most clients including web browsers and Oracle SQL Developer, you will need to perform additional configuration on client applications to configure them to accept the self signed certificate.

Installer support for Bequeath Connection

Oracle REST Data Services installer supports Bequeath connection for install, upgrade, validate and uninstall. Refer to Oracle REST Data Services documentation for details on using the bequeath connection.

Changes in 3.0.4

Issues Fixed in 3.0.4

The following changes and enhancements have been made since 3.0.3:
  • BUG:22605437 - Fix issues causing ORA-01000 Maximum Open Cursors Exceeded error messsage
  • BUG:22525939 - Fix issues causing APEX static resources to give 404 Not Found errors
  • BUG:21890324 - Fix problem with conditional DELETE of NoSQL table resources
  • BUG:22550686 - Fix problem preventing install into PDB in Oracle Database 12.1.0.1
  • BUG:22342053 - Fix issue with the dispatching of Resource Modules with empty base path

New Features in 3.0.4

None

Changes in 3.0.3

Issues Fixed in 3.0.3

The following changes and enhancements have been made since 3.0.2:
  • BUG:22336058 - Fix issue by providing option to use the database default tablespaces (default and temporary tablespaces) when installing ORDS
  • BUG:22307714 - Fix regression preventing OAuth 2.0 end user approvals working
  • BUG:22165161 - Ensure ETag is included in response when generating a 304 status
  • BUG:22279980 - Fix regression causing 405 Method Not Allowed when registering OAuth client in ORDS enabled schema
  • BUG:21312132 - Fix problem with ORA-00001 error raised when a table is rest enabled more than once
  • BUG:22179327 - Fix regression introduced in 3.0.2 that required ORDS to be installed before APEX for RESTful services to function
  • BUG:22179327 - Fix problem with removing NoSQL Store configuration using SQL Developer
  • BUG:22129159 - For PL/SQL Gateway calls, use the application supplied status code when performing a redirect
  • BUG:22173839 - Fix problem causing ETag value to be calculated incorrectly when origins allowed specified for a resource module
  • BUG:22157870 - Fix regression causing APEX plugin static resources to give 404 status when using a url-mapping.xml URL mapping rule
  • BUG:22100841 - Fix for issue preventing serving of resources with numeric values in the content type, for example video/mp4

New Features in 3.0.3

  • BUG:22336058 - Provide option to use the database default tablespaces (default and temporary tablespaces) when installing ORDS
  • BUG:22312795 - Support simultaneous dispatching of RESTful Services defined in APEX metadata and ORDS metadata for schemas that are APEX workspaces and also ORDS enabled

Changes in 3.0.2

Issues Fixed in 3.0.2

The following changes and enhancements have been made since 3.0.1:
  • BUG:21875754 - Fix regression in the handling of nested cursors when rendering JSON responses
  • BUG:21841485 - Fix regression in the handling of paginated resources in APEX RESTful Services when accessed via CORS request
  • BUG:21833987 - Fix regression causing shorted OAuth access token lifetimes due to non UTC timezones
  • BUG:21487014 - Fix regression where a null base path value in a Resource Module made the schema inaccessible via REST
  • BUG:21448390 - Fix regression where multiple database mappings configured via url-mapping.xml failed to work correctly
  • BUG:21429494 - Fix handling of cursor expressions causing invalid JSON
  • BUG:21365668 - Fix problem with certain passwords causing ORA-06550 PLS-00103 during install
  • BUG:21155926 - Fix regression causing PL/SQL Gateway to process flexible URL parameters incorrectly
  • BUG:17255991 - Fix problem with large OWA responses terminating at 60MB in size

New Features in 3.0.2

  • BUG:21646804 - Add support for a version command to command line: java -jar ords.war version
  • BUG:20538961 - Add PL/SQL API for creating and editing RESTful Services. The ORDS package has numerous additional published APIs and documentation for same.

Changes in 3.0.1

Issues Fixed in 3.0.1

The following changes and enhancements have been made since 3.0.0:
  • BUG:21230076 - Accessing /ords instead of /ords/ produces a 404 Not Found error on Weblogic, GlassFish and Tomcat
  • BUG:21230822 - Accessing an Application Express RESTful service protected by a privilege produces a 500 - Internal Server Error
  • BUG:21230822 - Accessing an Application Express RESTful service protected by a privilege produces a 500 - Internal Server Error
  • BUG:21194216 - RESTful Query Filters do not handle certain column names
  • BUG:21170353 - Mapping of Application Express workspaces does not work properly with Pluggable Database (PDB) based URL Mapping
  • BUG:21169232 - Various problems with manual URL mapping, including a problem with the url-mapping.xml file being stored in the wrong folder
  • BUG:21157228 - Problem with specifying workspace id when creating manual URL mapping
  • BUG:21148830 - Unable to define parameters for Resource Handlers in SQL Developer
  • BUG:21148830 - Unable to define parameters for Resource Handlers in SQL Developer
  • BUG:21136646 - Report 400 - Bad Request when integrity constraint violated on AutoRest update operations
  • BUG:21129378 - AutoRest Batch CSV Loading not working
  • BUG:21121349 - AutoRest POST should handle insert with no generated key
  • BUG:21088925 - Error when dropping REST enablement from schema
  • BUG:21083867 - PL/SQL Gateway reporting port number -1 for HTTP on port 80
  • BUG:21053432 - Support creating static resources war file with custom context path
  • BUG:21024231 - Case of query parameters not being preserved when calling PL/SQL procedures
  • BUG:21024175 - Array ordering being shuffled when calling PL/SQL procedures

New Features in 3.0.1

  • BUG:20586521 - Add support for a document root to standalone mode.
  • BUG:20539027 - Support installing Oracle REST Data Services into a Oracle Database 12c Container Database (CDB).

Changes in 3.0.0

The following changes and enhancements have been made since EA1:

Issues Fixed in 3.0.0

  • BUG:20221841 - Handle escaped slash characters in JSON values correctly
  • BUG:20197577 - Ensure transaction for original resource handler is committed before forwarding request to GET handler
  • BUG:20536145 - Address regression in 3.0.0 EA1 that prevented tabular forms in APEX working correctly
  • BUG:20568202 - Ensure @ApplicationScoped services are not started when command line is active
  • BUG:20601219 - Enable PL/SQL Gateway support for HEAD operation

New Features in 3.0.0

  • PL/SQL API for creating RESTful Services - This release previews the PL/SQL API for creating and editing restful services using PL/SQL, enabling the creation and mainteance of RESTful services to be scripted via PL/SQL. The API also exposes all the OAuth 2.0 functionality, enabling OAuth Clients to be registered and managed. Note that this API is subject to change before the final release of 3.0.0.
  • OAuth 2.0 Client Credentials Grant Support - The OAuth 2.0 Client Credentials Grant type is now supported, enabling server to server authorization via OAuth 2.0, which is an important use case for enterprise applications.
  • RESTful Privileges can be mapped to URL patterns - RESTful Privileges can now be associated with arbitrary URL patterns, enabling RESTful Privileges to protect any database resource accessed via ORDS including SODA resources and AutoRest resources. Privilege to URL mappings can be configured using the PL/SQL API or using SQL Developer.
  • The above two features mean that SODA resources and AutoRest resources can now be protected by OAuth 2.0
  • Improved NoSQL Database Support - The /store prefix on NoSQL Database resources has been eliminated, support has been added for the new DDL capability introduced in NoSQL Database 3.2.5, enabling DDL statements to be issued via a RESTful Endpoint.
  • Installer Improvements - The installer has improved support for migrating RESTful Service definitions stored in APEX Workspaces to ORDS enabled schemas. The installer now has an uninstall command, see java -jar ords.war help uninstall for more information.
  • RESTful Services Query Filtering Support - RESTful Services (that perform SQL queries) now support the specification of a JSON based filtering clause to further constrain the query. The filter clause can either be specified by including it as a parameter of the service's query string, or by submitting a POST request with the filter clause as the body of the POST request.
  • Java API for ORDS Plugins - This release previews a Java API that enables third parties to contribute extensions to the ORDS runtime. The documentation for the API is located here. A tutorial demonstrating how to compile and add a plugin to ORDS is located here. Note that this API is subject to change before the final release of ORDS 3.0.0

New Features since 2.0.10

Oracle REST Data Services includes the following new functionality:

Installer

Oracle REST Data Services 2.0.x required Oracle Application Express 4.2 or later to be installed in order to define and use RESTful Services. In Oracle REST Data Services 3.0.x Oracle Application Express is not required. Instead Oracle REST Data Services is able to install it's own schema on the first run of Oracle REST Data Services. The installation process is simple and fast.

Simple Oracle Document Access (SODA) for REST

JSON documents can now be stored in and retrieved from document collections managed by Oracle Database. SODA for REST provides an interface to the Oracle Database Document Store for NoSQL style application development.

Auto Generated REST Endpoints for Tables and Views

Using Oracle SQL Developer 4.1 and later you can expose database tables and views as REST API endpoints, enabling data stored in the tables or views to be created, queried, updated and deleted using REST.

Oracle NoSQL Database Support

This release adds support for exposing Oracle NoSQL Database tables as REST API endpoints. The data stored in the tables can be created, queried, updated and deleted using REST.

Changed Behaviour since 2.0.10

The behvaiour of the following existing features has been enhanced:

RESTFul Services

RESTful Service Metadata

Oracle REST Data Services now stores it's metadata about RESTful Services in it's own schema (named: ORDS_METADATA). This means it is no longer required to install Oracle Application Express in order to define RESTful Services.

Since Application Express is not used to define the metadata this means that these RESTful Services cannot be edited by Application Express, instead you must use Oracle SQL Developer 4.1 or later to edit the RESTful Services.

Note that existing RESTful Services defined in Application Express continue to be fully supported, see more about this in the Application Express section below.

Any database schema can be enabled to define RESTful Services, before a schema can define RESTful Services, it must enabled for use with Oracle REST Data Services. This can be done using SQL Developer 4.1 or in SQLPlus by invoking the ords.enable_schema stored procedure:

SQL> connect scott
Enter password:
Connected.
SQL> exec ords.enable_schema;

PL/SQL procedure successfully completed.

SQL> commit;

Commit complete.

SQL>

Oracle REST API Standardization

New Source Types

Oracle is converging and unifying APIs and document formats across all products that support REST. To support this two new Source Types have been added for Resource Handlers:

  • 'JSON Collection' produces a JSON document showing the results of a query in the standardized Oracle JSON format. This source type replaces the 'JSON Query' and 'JSON Query Feed' source types.
  • 'JSON Item' produces a JSON document showing a single result in a query in the standardized Oracle JSON format. This source type replaces the 'Query (with one result only)' source type.

'JSON Collection' is the default source type. Note that 'Query', 'JSON Query Feed', and 'Query (with one result only)' continue to be supported, but deprecated and customers are encouraged to switch to using the source types instead.

Pagination

The standardization effort also affects how pagination is performed, previously resources were paginated using the ?page=N query parameter. This syntax conintues to be supported for existing source types, but the new 'JSON Collection' source type uses the standardized ?offset=O&limit=L query parameters. This syntax gives clients more flexibility about indicating the size of pages they can handle.

Security

First Party Authentication

This release introduces support for cookie based first party authentication of RESTful Services. This feature enables web applications deployed on the same web server (origin) as the the RESTful Services to authenticate with the the RESTful Services using a cookie instead of OAuth 2.0 access tokens.

This makes it much easier for first party applications to consume RESTful Services. This feature is supported in ORDS enabled schemas and NoSQL data stores.

User Repositories

Oracle REST Data Services can authenticate against any user repository configured in the host application server. In the previous release users were typically defined in the Application Express user repository, in this release users are typically defined in the application server user respository.

Standalone Mode

Standalone now uses Jetty to provide the JEE runtime environment required by Oracle REST Data Services. Jetty is well proven, mature and being continuously improved.

Oracle Application Express

Oracle REST Data Services continues to support RESTful Services defined in Oracle Application Express. The 'JSON Collection' and 'JSON Item' source types are not supported in RESTful Services defined in Oracle Application Express.

Oracle SQL Developer can be used to edit RESTful Services defined in Application Express or Oracle REST Data Services. A database schema that is associated with an Application Express workspace can be enabled for Oracle REST Data Services 3.0.x RESTful Services, but doing so will mean only the RESTful Services defined in the ORDS_METADATA schema will be editable via Oracle SQL Developer.

Known Issues

JDK Support

  • ORDS does not run in Standalone Mode on Oracle JDK 9. Support for JDK 9 will be added in a future release.

SODA

  • None

Application Express RESTful Service Migrations

  • BUG:21302877 - Cannot migrate RESTful Services from APEX 5, migration process not coping with database not containing any APEX version.

Autogenerated REST Endpoints

  • AutoRest resources support the OAuth 2.0 Client Credentials flow only.

RESTful Services

  • Application Express workspaces do not support first party authentication, and therefore do not support the /sign-in/ interactive sign in form. Accessing /sign-in/ in APEX workspaces will produce a 404 status.

NoSQL

  • It is not currently possible to access secured NoSQL REST Endpoints with OAuth 2.0, only first party cookie authentication is supported.