This list contains only a selection of higher priority bugs, customer bugs and issues raised by the community on the OTN Forum since the release of version 2.0.1.
Issue with the parsing of xml files (e.g. url-mapping.xml) on WebLogic when running on non Oracle JDK.
Improve the handling of URLs missing a trailing slash. For example /apex/mapped-url will be redirected to the proper URL of /apex/mapped-url/.
Handling of multi-byte characters in request URLs in standalone mode.
Issue with generation of PDF documents containing Non ASCII characters on Windows platforms.
Bind variables within comment blocks were not handled correctly.
Response of less than 32766 characters that includes multi-byte UTF-8 characters pushes the number of bytes in the response over 32766 bytes causes 'ORA-06502: PL/SQL: numeric or value error:
Modify the behavior of the PL/SQL Handler when processing JSON and HTML form data. IFF the PL/SQL statement references the implicit :body parameter then the JSON or HTML Form data is not automatically parsed by the listener. This enables PL/SQL handlers to do their own parsing of the data.
Problem with the Authorization Code OAuth 2.0 Flow that prevents the redirect completing successfully on second and subsequent approvals of an application.
Improve the display of the Authorization URI that applications should use to initiate an OAuth 2.0 Approval. The URI displayed is now a fully qualified URL.
Issue preventing some temporary redirects working correctly on GlassFish, causing the error: PWC3990: getWriter() has already been called.
Problems with RESTful Service responses (OWA or LOB based) > 32KB generating 'ORA-22922: nonexistent LOB value'.
Generating an OWA response in a RESTful Service produces the following error: SEVERE: oracle.jdbc.driver.OracleClobReader cannot be cast to java.io.InputStream.
INTERNAL Workspace and a regular workspace both contain a RESTful Service with the same URITemplate. The INTERNAL version was being chosen instead of the regular workspace version.