For Release 11.1.1.9.1, this guide has been updated in several ways. The following table lists the sections that have been added or changed.
Note:
This version of the guide may not contain the most recent content. To view the latest version, access the guide directly from the library on OTN. To see what has been added to this newer version, compare the What's New sections of each guide.For changes made to Oracle JDeveloper and Oracle Application Development Framework (Oracle ADF) for this release, see the New Features page on the Oracle Technology Network at http://www.oracle.com/technetwork/developer-tools/jdev/documentation/index.html.
| Sections | Changes Made |
|---|---|
| Chapter 5, "Defining SQL Queries Using View Objects" | |
| Section 5.8, "Working with View Objects in Declarative SQL Mode" | Revised section to describe how to enable runtime optimization for ADF REST resources by creating view objects created in declarative SQL mode, which allows the SQL SELECT statement to be determined by the attributes named in the fields query parameter of client requests. |
| Section 5.10.2, "How to Use View Criteria to Filter a View Object for the Current User" | Revised section to describe the ADF Security Context method to use in a Groovy expression that gets the current user. |
| Chapter 11, "Creating SOAP Web Services with Application Modules" | |
| Section 11.5, "Working with the Find Method Filter Model in the Consuming Application" | Added section to describe the containment hierarchy of the find method filter model and to provide examples of its usage. |
| Chapter 12, "Creating RESTful Web Services with Application Modules" | |
| Section 12.1, "Introduction to RESTful Web Services and ADF Business Components" | Revised section to describe the best practice for creating view objects using the Declarative option on the Query page of the Create View Object wizard to enable declarative SQL mode. |
| Section 12.5, "Versioning the ADF REST Runtime Framework" | Added section to describe how ADF REST application developers can declare a default ADF REST framework version for REST resources to utilize new features and enhancements at runtime, such as the advanced query capabilities offered in version 2 of the ADF REST runtime framework. Using this capability, REST application developers may opt into the features introduced by a specific ADF REST framework when they are ready. In JDeveloper release 11.1.1.9.1 framework versions 1, 2, and 3 exist. |
| Chapter 15, "Consuming RESTful Web Services Using the ADF REST Framework" | |
| Section 15.5.4, "Filtering a Resource Collection with a Query Parameter" | Revised section to describe GET requests that use advanced query capabilities to retrieve ADF REST resource. This query capability, introduced by version 2 of the ADF REST framework, supports rowmatch expressions. |
| Section 15.5.6, "Fetching Nested Child Resources" | Revised section to describe GET requests that retrieve nested child resources using the a payload structure that returns the child resource items as a resource collection, instead of as an array of resource items. This capability, introduced in version 3 of the ADF REST framework, supports pagination of nested child resources. |
| Section 15.13.1, "Querying With Filtering Attributes (Partial Get)" | Revised section to describe GET requests that retrieve nested child resources using the a payload structure that returns the child resource items as a resource collection, instead of as an array of resource items. This capability, introduced in version 3 of the ADF REST framework, supports pagination of nested child resources. |
| Section 15.12, "Working with ADF REST Framework Versions" | Added section to describe how service clients of the ADF REST application may pass a specific ADF REST framework version to execute requests using a particular ADF REST runtime. In JDeveloper release 11.1.1.9.1, framework versions 1, 2, and 3 exist. |
| Section 15.14.3, "ADF REST Data Types" | Added section to describe how the ADF REST framework maps ADF REST data types between ADF REST resource items and their backing ADF Business Components entity object attributes. |
| Section 15.14.5, "ADF REST HTTP Headers Support" | Revised section to describe the custom header REST-Framework-Version that allows service clients to specify a particular version of the ADF REST framework to use at runtime to process the request. The ADF REST framework version passed in the version header overrides the default framework declaration defined by the application. In JDeveloper release 11.1.1.9.1, framework versions 1, 2, and 3 exist. |
| Section 15.14.6.1, "GET Method Operations" | Revised section to describe the difference between GET operations are processed using the q query parameter syntax in ADF REST framework version 1 and version (or later). Starting with version 2 of the ADF REST framework, a backward-incompatible advanced query syntax is offered. |
| Chapter 16, "Getting Started with ADF Task Flows" | |
| Section 16.2.1, "How to Create a Task Flow" | Revised section to describe how the Create with Page Fragments checkbox in the Create Task Flow dialog may be used when defining a task flow activity for opening a dialog. |
| Chapter 25, "Creating ADF Databound Tables" | |
| Section 25.6, "Creating a Table with Dynamic Components" | Added section to describe the usage of a dynamic component to create tables where the binding metadata, columns, and the components used to display the bound content are determined at runtime. |
| Section 24.7, "Creating a Form with Dynamic Components" | Added section to describe the usage of a dynamic component to create forms where the binding metadata and the components used to display the bound content are determined at runtime. |
| Chapter 32, "Enabling ADF Security in a Fusion Web Application" | |
| Section 32.3.5, "What You May Need to Know About ADF Authentication" | Revised section to clarify the way WebLogic Server handles an existing anonymous user session upon user login. Also describes the best practice for getting the current user data from the authenticated session due to the way the anonymous user session is handled by WebLogic Server. |