The following topics introduce the new and changed features of Oracle Mobile Application Development Framework (Oracle MAF) and other significant changes, which are described in this guide.
Oracle MAF Release 2.3.1 includes the following new and changed development features, which are described in this guide.
MAF applications can now access REST services through the client data model introduced in this release. The client data model provides a wizard to identify the data objects exposed by REST services that you can include in your MAF application’s data model. Once identified, you can specify:
Data to persist on users’ devices when your application is offline
Specify parent-child relationships between data objects
Identify the REST resources that perform CRUD actions on the data
Synchronize data from your application to the server when your application returns online
For more information, see Creating the Client Data Model in a MAF Application.
The client data model also includes a reusable application feature that you can add to your MAF application to inspect web service calls from the application. For more information, see Inspecting Web Service Calls in a MAF Application.
MAF applications that you deploy to Android emulators or iOS simulators now support a quick deployment where only new and revised files are deployed after an initial full deployment of the application. You can always trigger a full deployment, if required. For more information, see Overview of MAF Quick Deployment of Applications.
This release of MAF supports a new grant type (client credentials) for the OAuth authentication server type. Use the client credentials grant type so that your MAF application can access Oracle Mobile Cloud Service APIs anonymously without requiring an end user ID or user credentials. For more information, see How to Configure OAuth Authentication.
New version of the mobileAlta skin (mobileAlta-1.6) that is the default for MAF applications created using this release. For more information, see Skinning MAF Applications.
MAF now enables you to configure properties in your MAF application that an Enterprise Mobile Management administrator can set values for when your application is deployed to end users. For more information, see Configuring Properties For Use By Enterprise Mobile Management.
This document has been updated in several ways for this release. Following are the sections that have been added or changed.
Added information describing how you can configure your MAF application so that an end user can send an email recipient the MAF application log file from their device. For more information, see How to Access the Application Log.
Added information for the addXXX and removeXXX methods of Data Control. For more information, see addXXX and removeXXX Methods of Data Control.
Revised to note that you must implement a getKey() method in a class where you use the ProviderChangeSupport object or, alternatively, specify an attribute on the associated data control as a key attribute. Implementing one of these changes is required to ensure successful synchronization of data change events. For more information, see Working with Data Change Events.