Skip to main content

ADF Mobile : Finally released and ready to use

After extensive beta testing oracle announced last week that ADF Mobile is now generally available and can be used to build multi platform on device apps. I finally am allowed to share my knowledge in blogposts and other kinds of publications. Using JDeveloper and the ADF Mobile extension, it is very easy to create apps for both the iOS and Android platform. If you only want to create apps for Android, you don’t need a mac, however if you want to create apps voor iOS you really do need a mac to compile the ADF mobile app for iOS.
ADF Mobile provides a natural extension of enterprise/internet applications to mobile clients by providing tools, services, and infrastructure to protect against technology shifts. An application built with ADF Mobile framework installs on a smart device, renders user interface via HTML5, and has access to device services. This means the programming model is primarily web-based, which offers consistency with other enterprise applications as well as easier migration to new platforms. But the application has access to device services, enabling a richer experience for users than a browser alone can offer. The architecture of ADF Mobile.
A short explanation of the components on the image: The Device Native Container represents an application container or template compiled as device native application binary which provides the run-time environment for an ADF Mobile application to run as an on-device, native application in the mobile device’s operation system (for example, Apple iOS). The Web View is a part of the device native container that uses a mobile device’s web engine to display and process web-based content. In an ADF Mobile application, the web view is the primary mechanism to render and deliver the application user interface. Server HTML represents a web-based user interface that is generated on the server (ADF Mobile browser and Oracle ADF Faces rich client-based pages) and delivered as a Web page to the ADF Mobile application. The Local HTML represents web pages developed using JDeveloper or third-party tools that are directly embedded within an ADF Mobile application. ADF Mobile AMX Views are based on the ADF Mobile AMX technology that delivers a JSF-like development experience to working with an HTML5-based user interface. ADF Mobile AMX views are defined using UI and code editors provided by JDeveloper. These views are embedded into an ADF Mobile application and deployed to a mobile device. At run time, the JavaScript engine in the web view renders ADF Mobile AMX view definitions into HTML5 components. ADF Mobile AMX components are built to deliver a mobile optimized user experience out of box. These components support the device native user experience through extensive animation and gesture support. The ADF Controller is represented by a mobile version of Oracle ADF controller that supports a subset of Oracle ADF task flow components available to a server-based Oracle ADF application. Java provides a Java run-time environment for an ADF Mobile application. This Java Virtual Machine (JVM) is implemented in device-native code, and is embedded (or compiled) into each instance of the ADF Mobile application as part of the native application binary. Managed Beans are Java classes that can be created to extend the capabilities of ADF Mobile, such as provide additional business logic for processing data returned from the server. The ADF Model in an ADF Mobile application supports a subset of business logic components available to a server-based Oracle ADF application. ADF model contains the binding layer that provides an interface between the business logic components and user interface, as well as the execution logic to invoke REST or SOAP-based web services. PhoneGap is an open-source code library that provides a common JavaScript API to access various mobile device services, such as the camera. PhoneGap provides a majority of the device services integration for an ADF Mobile application. Local Data refers to data stores that reside on the device. In ADF Mobile, these are implemented as encrypted SQLite databases. ADF mobile enables you to interact with mobile device services such as the camera, the email client, contacts and more. There is no need for you to know how to interact with the device because ADF mobile uses phonegap to abstract these device specific api’s. On top of that ADF mobile uses a device datacontrol to even abstract phonegap. The device datacontrol can be used in the exact same way as any other datacontrol. You can drag and drop operations from the data control onto your page. In ADF Mobile, data controls behave similarly to the way they work in Oracle ADF. Device data controls appear within the Data Controls panel in JDeveloper, allowing you to drag and drop the primary data attributes of data controls to your application as (text) fields, and the operations of data controls as command objects (buttons). Performing such drag and drop actions will generate standard EL bindings in your application in the appropriate properties for the controls that are created. The normal ADF bindings for those actions (represented by a general DataControls.dcx file, to point at the data control source, and the page bindings, to link the specific page’s reference to the data control) will be present, allowing the runtime to process the bindings when your application executes.


hellanadam said…
I wondered upon your blog and wanted to say that I have really enjoyed reading your blog posts. Any way I’ll be subscribing to your feed and I hope you post again soon.
ios App Development Company
Mobile App Development Company
Best Mobile App Development Company

Popular posts from this blog

ADF 12.1.3 : Implementing Default Table Filter Values

In one of my projects I ran into a requirement where the end user needs to be presented with default values in the table filters. This sounds like it is a common requirement, which is easy to implement. However it proved to be not so common, as it is not in the documentation nor are there any Blogpost to be found that talk about this feature. In this blogpost I describe how to implement this.

The Use Case Explained
Users of the application would typically enter today's date in a table filter in order to get all data that is valid for today. They do this each and every time. In order to facilitate them I want to have the table filter pre-filled with today's date (at the moment of writing July 31st 2015).

So whenever the page is displayed, it should display 'today' in the table filter and execute the query accordingly. The problem is to get the value in the filter without the user typing it. Lets first take a look at how the ADF Search and Filters are implemented by the f…

ADF 11g Quicky 3 : Adding Error, Info and Warning messages

How can we add a message programatically ? Last week I got this question for the second time in a months time. I decided to write a short blogpost on how this works.

Adding messages is very easy, you just need to know how it works.
You can add a message to your faces context by creating a new FacesMessage. Set the severity (ERROR, WARNING, INFO or FATAL ), set the message text, and if nessecary a message detail. The fragment below shows the code for an ERROR message.

1: public void setMessagesErr(ActionEvent actionEvent) {
2: String msg = "This is a message";
3: AdfFacesContext adfFacesContext = null;
4: adfFacesContext = AdfFacesContext.getCurrentInstance();
5: FacesContext ctx = FacesContext.getCurrentInstance();
6: FacesMessage fm =
7: new FacesMessage(FacesMessage.SEVERITY_ERROR, msg, "");
8: ctx.addMessage(null, fm);
9: }

I created a simple page with a couple of buttons to show the result of setting the message. When the butto…

How to: Adding Speech to Oracle Digital Assistant; Talk to me Goose

At Oracle Code One in October, and also on DOAG in Nurnberg Germany in November I presented on how to go beyond your regular chatbot. This presentation contained a part on exposing your Oracle Digital Assistant over Alexa and also a part on face recognition. I finally found the time to blog about it. In this blogpost I will share details of the Alexa implementation in this solution.
Typically there are 3 area's of interest which I will explain. Webhook Code to enable communication between Alexa and Oracle Digital AssistantAlexaDigital Assistant (DA) Explaining the Webhook Code The overall setup contains of Alexa, a NodeJS webhook and an Oracle Digital Assistant.
The webhook code will be responsible for receiving and transforming the JSON payload from the Alexa request. The transformed will be sent to a webhook configured on Oracle DA. The DA will send its response back to the webhook, which will transform into a format that can be used by an Alexa device. To code exposes two REST …