Developer Partner Community

  • October 26, 2014

Mobile Persistence Extension for Oracle MAF by Steven Davelaar

Jürgen Kress
PaaS Partner Adoption

Oracle has released Oracle Mobile Application Framework (MAF), the new cross-platform development framework for mobile applications that supersedes ADF Mobile. Oracle A-Team has upgraded its Mobile Persistence Extension to work with Oracle MAF. This mobile persistence extension adds significant value to Oracle MAF: it allows easy consumption of RESTful services, and provides a complete persistence layer that allows you to use the mobile application in offline mode. You can read and write data while not connected to the internet, and synchronize any pending data changes later when you are online again.

Oracle MAF product development has acknowledged the value of this extension and will incorporate the functionality of this extension in a new release of MAF that will become available later this year. This article introduces the new MAF release of this persistence extension that you can start using today. It discusses the enhanced REST-JSON wizard in great detail and provides download and getting started instructions at the end of this article.

Main Article
The Case for REST-JSON
With the availablity of Oracle SOA Suite 12c, it has become much easier to convert back-end SOAP web services to REST-JSON services. SOA Suite 12c is a release that focusses on “RESTifying” your back end services, and provides powerful declarative features to publish a RESTful API for mobile consumption. Here are some articles that provide more information about this functionality:

You might wonder why this is so important since Oracle MAF (and its predecessor ADF Mobile) provide strong support for consuming SOAP-based web services. Well, to make a simple and clear statement: if you are planning to build mobile applications, Oracle A-Team strongly recommends to communicate through REST-JSON services with your back-end applications. The reason for this is simplicity and performance. The REST architectural pattern is very easy to work with. The performance overhead with SOAP web services is bigger. XML payloads are more verbose than JSON, which means the size of the data packets sent over the wire is bigger. In the mobile client, XML parsing is a relatively expensive task compared to JSON payloads that can be used directly in JavaScript. So, if you have existing SOAP-based web services you want to consume in a mobile application, we recommend to transform these web services to RESTful services using Oracle Service Bus (OSB) 12c. For new web services that you still need to build, you might consider using JAX-RS which is a standard Java API that makes it fast and easy to disclose your back-end data and business logic through a RESTful API. Note that even if the back-end service is already in REST-JSON format it is still a good idea to virtualize access to it using OSB, decoupling your mobile application from the actual back-end service implementation.
A Sample HR REST API Created with EclipseLink/Toplink RESTful Data Services Read the complete article here.

WebLogic Partner Community

For regular information become a member in the WebLogic Partner Community please visit: http://www.oracle.com/partners/goto/wls-emea ( OPN account required). If you need support with your account please contact the Oracle Partner Business Center.

Blog Twitter LinkedIn Mix Forum Wiki

Be the first to comment

Comments ( 0 )
Please enter your name.Please provide a valid email address.Please enter a comment.CAPTCHA challenge response provided was incorrect. Please try again.