Tuesday, June 18, 2013

ODTUG KScope 2013 : I'm Speaking

Next week the ODTUG KScope conference kicks of in New Orleans.


During this conference I will present 3 sessions:
Keep your eyes on this weblog for more information on ADF and Mobile stories of ODTUG KScope13.
 

Friday, May 31, 2013

ADF Mobile : Oracle eCourse available

Today Oracle published the first in a series of online eLearning training materials. The ADF Academy presents free and online : Developing Applications with ADF Mobile. The main goal is to deliver technical training material to everybody that needs it. You get an online training, where you can view audio and video to learn ADF. Whenever you want to you can stop the recordings to try out everything that you learned so far, or perhaps to get a drink.



Developing Applications with ADF Mobile is available here.
Take to opportunity and learn to work with a great framework to develop mobile applications for iOS and Adroid.

Also keep an eye on lucbors.blogspot.com for more ADF Mobile related content.

Thursday, February 28, 2013

ADF Mobile : Implementing the "Pull to Refresh" Pattern

One very common pattern in Mobile Apps is the use of "pull" to refresh a list of data in an App.
For one of my projects I suggested to use this pattern and I had to figure out a way to implement this in ADF Mobile. In this post I show you a way to implement this. If you are only interested in the refresh part, you might want to skip the first 5 steps. These explain in short the webservice and the basic ADF Mobile app. From step 6 on I explain how to implement the pattern.

1. The webservice
For this example I use a simple webservice that returns a List of Locations. The webservice is a service enabled Application Module. I simply created Business Component (EO and VO) on the Locations table from the HR schema. I exposed the Locations view object as AllLocations, and added a method called getCurrentCount() on the Application Module Impl class.  This method simply invokes the getEstimatedRowCount() to find out the number of rows. Next I created a new Service Interface on the Application Module. And that is about it for the service.
This all resides in a separate application and is deployed on a remote weblogic server. The mobile app will use this webservice.

2. The Mobile App
Create a simple ADF Mobile Application. In this application I need to call out to the webservice. For that I use a webservice datacontrol. Simply invoke the "create webservice" dialog, give the webservice a name and enter the URL of the WSDL.

In the second part of the wizard, I simply select the two operations that I need.

The webservice datacontrol is now finished. Both operations are now available from the datacontrol. The datacontrol looks like this:

3. The custom model
For the application I want to use a custom object model in order to be independent of the webservice data structure. This is common practice and recommended approach. The class that I use for this is called MyLocation.


I use the following properties:

 package nl.amis.technology.mob.objects;  
 public class MyLocation {  
 private int LocationId;  
 private String StreetAddress;  
 private String PostalCode;  
 private String City;  
 private String StateProvince;  
 private String CountryId;  
   public MyLocation() {  
     super();  
   }  
 }  

Simply generate accessors for these and the class is finished.

4. Invoking the webservice
Now I create a new class that I use in my mobile application to provide the app with data. This class is called LocationInfoDC. In this class I create a list of locations that I can display in the mobile app.

 public class LocationInfoDC {  
   private static List s_locationsList;   
   private transient ProviderChangeSupport providerChangeSupport =   
               new ProviderChangeSupport(this);  
   public LocationInfoDC() {  
     super();  
     if (s_locationsList == null) {  
       s_locationsList = new ArrayList();  
       retreiveLocationInformation();  
     }  
   }  
   public void AddLocation(MyLocation l) {  
     s_locationsList.add(l);  
   }  
   public MyLocation[] getAllLocations() {  
     MyLocation locs[] = null;  
     locs = (MyLocation[])s_locationsList.toArray(new MyLocation[s_locationsList.size()]);  
     return locs;  
   }  
  ......  

For webservice invocation I use AdfmfJavaUtilities.invokeDataControlMethod(). This enables me to invoke a Datacontrol Method whithout having a page Definition available. It is a powerful mechanism.

 // This calls the DC method and gives us the Return  
    GenericType result =  (GenericType)  
       AdfmfJavaUtilities.invokeDataControlMethod("HrWsDc"  
                                          , null  
                                          ,"findAllLocations"  
                                          ,pnames, params, ptypes);  

The AdfmfJavaUtilities.invokeDataControlMethod() returns a GenericType. This response needs to be "converted" to the custom object model described in step 3.

  // The Return wraps the findAllLocations Result, so get that out of the Result  
   s_locationsList.clear();          
    for (int i = 0; i < result.getAttributeCount(); i++)   
    {  
      GenericType row = (GenericType)result.getAttribute(i);  
      MyLocation locationInformation = (MyLocation)  
             GenericTypeBeanSerializationHelper.fromGenericType(MyLocation.class, row);  
      AddLocation(locationInformation);  
    }  

Another important part is the invocation of the client page refresh. The ProviderChangeSupport class is used for sending notifications relating to collection elements, so that components update properly when a change occurs in a Java bean data control. I refresh the collection delta, using the ProviderChangeSupport class. Since the provider change is required only when you have a dynamic collection exposed by a data control wrapped bean, there are only a few types of provider change events to fire:
  • fireProviderCreate—when a new element is added to the collection
  • fireProviderDelete—when an element is removed from the collection
  • fireProviderRefresh—when multiple changes are done to the collection at one time and you decide it is better to simply ask for the client to refresh the entire collection (this should only be used in bulk operations)
I use the fireProviderRefresh, asking for the client to refresh the entire collection.

The trick that does the magic:

 providerChangeSupport.fireProviderRefresh("allLocations");  

For this class I also generate a datacontrol so I can use it on the mobile page.

5. The Mobile Page
The view for the list is a simple amx page.
Create the page and drag the AllLocations collection from the datacontrol onto the page. In the popup menu pick "ADF Mobile List View".


Actually that is all that needs to be done. Now after deploying, the app looks like this.


Now it is time to implement the "pull to refresh".

6. Implementing the pull to refresh: Calling the service
In order to refresh the list, I need to know if there are actually new records available in the database.
This information is provided by the getCurrentCount webservice operation. First I create a new pageflowscoped backing bean to hold all logic involved in this functionality. In this bean I have one property. This is used to store the latest record count. This count is used to make sure that the findAllLocations webservice is only invoked if necessary.

 public class LocationsBackingBean {  
   String count="0";  
   private transient PropertyChangeSupport propertyChangeSupport =   
           new PropertyChangeSupport(this);  
   public LocationsBackingBean() {  
   }  
   public void setCount(String count) {  
     String oldCount = this.count;  
     this.count = count;  
     propertyChangeSupport.firePropertyChange("count", oldCount, count);  
   }  
   public String getCount() {  
     return count;  
   }  


To call the webservice that returns the current record count (getCurrentCount) I also use AdfmfJavaUtilities.invokeDataControlMethod().
The returned value (= the current number of rows in the database table) is compared to the previous amount returned by this service call. If there are more rows in the database table, I want to refresh the List. To do that, I simply call out to the  "findAllLocations" service. After successful invocation, the count is updated to the new value.

   public void checkForUpdates(ActionEvent ea) {  
    ......  
   String result;  
     try {  
       // This calls the DC method and gives us the Return  
       result = (String)   
             AdfmfJavaUtilities.invokeDataControlMethod("HrWsDc"  
                                                , null  
                                                , "getCurrentCount"  
                                                , pnames, params, ptypes);  
       // After service call, compare result to current count  
       // If new records are available, refresh the list by calling the webservice via invoking     
       // the corresponding method binding   
       if (Integer.valueOf(this.count).compareTo(Integer.valueOf(result))<0){  
         AdfELContext adfELContext = AdfmfJavaUtilities.getAdfELContext();  
         MethodExpression me =   
                AdfmfJavaUtilities.getMethodExpression(  
                     "#{bindings.retreiveLocationInformation.execute}"  
                    , Object.class, new Class[]{});  
         me.invoke(adfELContext, new Object[]{});  
         // after succesfully refreshing the list, update the current number of rows  
         setCount(result);  
        }  
     } catch (AdfInvocationException e) {  
        ............    }   
       catch (Exception e2) {  
       ...............    }  
   }  

7. Implementing the pull to refresh: Configure the Listview
I want to refresh the list with Locations whenever the list is pulled down.
For this I use the amx:actionlistener component. This component allows you to declaratively invoke an action. This component is meant to be a child component of any tag that has some kind of listener attribute like actionListener, or valueChangeListener, etc. The type attribute defines which listener of the parent this actionListener should be fired for. These methods fire before the listener on the parent component fires.
In the actionListener I invoke the checkForUpdates method that was described earlier.

The component has two attributes: type and binding. Type is set to swipeDown and in the binding attribute I use the checkForUpdates method that is implemented in the locationsbean.

  <amx:actionListener type="swipeDown"   
                  binding="#{pageFlowScope.locationsBackingBean.checkForUpdates}" />  

The complete code for this simple Listview now looks like this:
   <amx:listView var="row" value="#{bindings.allLocations.collectionModel}"  
          fetchSize="#{bindings.allLocations.rangeSize}"   
          id="lv1">  
    <amx:listItem id="li1">  
    <amx:actionListener type="swipeDown"   
                     binding="#{pageFlowScope.locationsBackingBean.checkForUpdates}" />  
     <amx:tableLayout width="100%" id="tl1">  
      <amx:rowLayout id="rl1">  
       <amx:cellFormat width="10px" id="cf3"/>  
       <amx:cellFormat width="60%" height="43px" id="cf1">  
        <amx:outputText value="#{row.streetAddress}" id="ot2" inlineStyle="font-size:x-small;"/>  
       </amx:cellFormat>  
       <amx:cellFormat width="10px" id="cf2"/>  
       <amx:cellFormat width="40%" halign="end" id="cf4">  
        <amx:outputText value="#{row.city}" styleClass="adfmf-listItem-highlightText" id="ot3"  
                inlineStyle="font-size:small;"/>  
       </amx:cellFormat>  
      </amx:rowLayout>  
     </amx:tableLayout>  
    </amx:listItem>  

8. The result
After deploying the app it is time to test the behavior. After starting the app and the list shows some Locations.

Now add 1 or 2 Locations to the database and commit these changes.



Swipe the list down, release  and see what happens.......

The new Locations are displayed.

9. Some Final Notes
This example (and actually the pattern) works for lists that show rather static data (no update or deletes). Every "pull down" gesture checks the server for new rows. That is, it checks if there are more rows then during the last call, and if so, the new rows are returned and added to the list. So whenever there are deleted or changed rows, this is not reflected in this sample. I could have implemented a service only returning the new Locations and add those to the list, but for this example I decided to simply fetch all Locations and rebuild the list. One other improvement is to only invoke the webservices if the "pull down" is invoked on the first row in the list.

Thursday, December 27, 2012

ADF Mobile : Device Interaction API - Pictures, GPS and Email With Attachments

During the AMIS ADF Masterclass I showed how to take a picture from within an ADF Mobile application, attach it to an Email and send that email out to several recipients. To top it of, I even added the GPS coordinates to the subject, so you know where the picture was taken. And all of that with the push of one single button. Sounds complicated ? Well actually it is very simple.

There are two ways to interact with device services. One is by using the page Definition, the second is by using the API.I decided not to use the pageDef, but to invoke the device datacontrol from java by using the API. Then it is also possible to invoke multiple actions in one java method. In this case I take a picture, get the coordinates and send an email.

How to take a picture ?
Taking a picture is easy. Just call the getPicture() method, and make sure (for this use case) to set Destination Type to File.
 public String getPicture(){  
   //destinationType = 1 so that the image is returned as a filename      
   String theImage = DeviceManagerFactory.getDeviceManager().getPicture(  
            100  
           ,DeviceManager.CAMERA_DESTINATIONTYPE_FILE_URI  
           ,DeviceManager.CAMERA_SOURCETYPE_CAMERA  
           , false  
           ,DeviceManager.CAMERA_ENCODINGTYPE_PNG  
           ,0  
           ,0);  
   return theImage;  
   }  

That takes care of taking the picture.

How to get the current coordinates ?
By invoking getCurrentPosition it is very easy to get the GPS coordinates. Simply call the getCurrentPosition() method, and you will get the current coordinates. The coordinates are refreshed every 60 seconds.
 public Location getPosition(){  
   Location currentPosition = DeviceManagerFactory.getDeviceManager().getCurrentPosition(  
                                    60000  
                                   , true);  
   return currentPosition;  
 }  


How to send an email ?
First take a look at the signature of the sendEmail() method. This immediately makes clear how to proceed from here...
 DeviceManagerFactory.getDeviceManager().sendEmail(  
         java.lang.String to  
         ,java.lang.String cc  
         ,java.lang.String subject  
         ,java.lang.String body  
         ,java.lang.String bcc  
         ,java.lang.String attachments  
         ,java.lang.String mimeTypes)  

The signature explains how it works. All that is needed are Strings. If you want to use multiple recipients, you need to separate them by comma's. The final question is: "how to attach the image that was just created ?".

Attaching the image.
You can do two things. Either use the String that is returned by calling getPicture(), or directly attach the file from the Temporary Directory which I do in this case.
 public void sendEmail(String attachment, Location here){  
   String directoryPathRoot = AdfmfJavaUtilities.getDirectoryPathRoot(0); //TemporaryDirectory  
   String content = "Amis wishes you all the best for 2013. This email contains an image as attachment. ";  
       content = content + "The picture was taken at: latitude=" + here.getLatitude() +  
            ", longitude=" + here.getLongitude();  
   attachment = directoryPathRoot+"/Pic.png";  
   DeviceManagerFactory.getDeviceManager().sendEmail("my.mail@company.org"  
                            , null  
                            , "Merry Xmas and a Happy new year"  
                            , content  
                            , bcc  
                            , attachment  
                            , "image/jpg");  

The content and bcc in the above code sample are Strings that can be set in the method.

Putting it all together
The only thing you need is a button to invoke a method in the bean.
 amx:commandButton text="Take Picture" id="cb3"  
                actionListener="#{pageFlowScope.interactionBean.executeLogic}"  

The method executeLogic() does the magic by invoking all three methods described above.
 public void executeLogic(ActionEvent actionEvent) {  
   String att = getPicture();    
   Location whereAmI = getPosition();  
   sendEmail(att, whereAmI);  
   }  


Push the button, the camera is invoked, and after that, the email client is invoked, showing an email with the attachment, the content (including GPS coordinates) and the recipients.

Sunday, December 16, 2012

Book Review : Oracle ADF Real World Developer's Guide

In October 2012 yet another ADF Book was published. This book "Oracle ADF Real World Developer's Guide" is authored by Jobinesh Purushothaman. Jobinsh works with Oracle as a Principal Solutions Architect for the Oracle Application Development Framework. The book is full of essential tips and tricks for building ADF applications. In this post I will share my book review with you and I give you the chance to win a free copy.



This book is suitable for ADF developers who are looking forward to build healthy and better performing applications using Oracle ADF. A book filled with step-by-step instructions and real-time examples with illustrations, diagrams, and tips that help developers learn the visual and declarative programming model offered by ADF. Using this book, readers will learn to get started with building business services using ADF business components, validate business data in different layers of an application and understand the use of EJB and web services in an ADF application.

The book contains 12 Chapters containing anything from getting started to Advcance topics.

Before I go into each chapter, I must say that this book has a couple of outstanding ways of explaining the ADF Framework. First of all there are many simple diagrams (and images) explaining the framework and parts of the framework. These diagrams are easy to understand, because thay only contain relevant information. You are not being distracted by colors or misleading images. It is just simple images, but very clear.

Next there are the sequence diagrams. These diagrams explain what exactly happens (at class level) when for instance you issue execute query from an ADF Application. As far as I know this is the first book that uses these sequence diagrams to explain ADF in a very clear way.

Finally I need to point out the valuable code samples that are in the book. Get yourself a digital copy so you can easy copy and past these code snippets into your ADF application.

Now lets take a look at the chapters.

Part I : getting started

1 : Getting Started with Oracle ADF
The most interesting part for me is the section on "Comparing the Fusion web application technology stack to the Java EE web application". This is explaining ADF in the context of a Java EE application. Currently I am involved in a project where we need to "rebuild" a Java EE application in ADF. There is a lot of discussion in this project about responsiblity of eaach layer. This chapter can help Java EE developers understand the ADF framework. The image on page 13 of the book ADF and Java EE by putting both in one diagram next to eachother.

Also the part about the generated Metadata files is valuable. Ussualy these files (like adf-settings, weblogic-application) are taken for granted, but Jobinesh explains what all the metadata files are about.

Part II : ADF Business Components

2 : Introduction to ADF Business Components
3 : Introducing Entity Object
4 : Introducing View Object
5 : Advanced Concepts on Entity Objects and View Objects
6 : Introducing the Application Module
This part provides a detailed look at how entities, view objects and application modules are defined and how they work at runtime. I was impressed by the level of detail in chapter 2. It is great that I have a couple of more chapters that go even into more detail.  This chapter really made me wanna continue reading. Chapters 3 and 4 are introducing the basic concepts of View Objects and Entity Objects. Both chapters contain very helpful sequence diagrams explaining what happens internally within entity objects and view objects.

At the start of chapter 5 Jobinesh tells the reader to "Take a deep breath and prepare yourself".  The part that follows takes a deep dive into entity objects. This chapter is full of in depth Entity Object knowledge. Allthough I have been working with ADF for many many years there were some interesting featured in this chapter that I did not know about. (mainly because I never had to use these). For instance, did you know that you can call getAttribute(attrIndex,EntityImpl.ORIGINAL_VERSION) on an entity object to read the originally retrieved value for an attribute ? I allways use(d) getPostedAttribute(int attribIndex).

At the end of the Entity Object section there is an interesting part on "Building programmatically managed entity objects" including code samples.

The most interesting part of the View Object section is about working with ViewCriteria Programmatically. Also the section about working with XML data is a noce one. I never got to use this functionallity in real life. Jobinesh explains very well how to do this, and I hope to get a use case soon. The chapter ends with a section about "Building business components dynamically".

After reading chapter 5 I can only say one thing: "I am impressed !".

Chapter 6 covers important topics like properties, passivation, activation, application module pooling.

7 : Binding Business Services with the User Interface
Chapter 7 really contained nothing new to me. However, if you are new to ADF, this chapter contains very good explanation of the binding layer. There is an interesting part about "Invoking an application module from a Java servlet". I did use this approach in several occassions. It is good to have a section on this in the book. Again in this chapter there are several simple diagrams that help you understand what happens in the binding layer.

8 : Building Data Bound Web User Interfaces

This is about building data bound web user interfaces. It has a small section on layout components. It also talks about working with tree and treetables programmatically. One of the things I learned form this chapter is how to use the "RowCountThreshold" attribute in an iterator binding. Never did that before.... On page 327 there is a "best practice" that you should know about: "If the scope of the managed bean is higher than the request, then you should not bind the UI components' elements in the JSF page with the UI component instances defined in a managed bean using the binding attribute in the component tag"

9 : Controlling the Page Navigation
For me there really wasn't anything new but, if you are new to ADF, it is again a very nice chapter.

10: Taking a Closer Look at the Bounded Task Flow
This chapter takes a deep dive into the bounded taskflow. There are sections on "dynamic taskflow calls, Lazy Loading and there is even a section on Contextual events.

11: More on Validations and Error Handling
Yet another chapter containing very valuable tips. Very interesting is the part where you learn how to vreate a custom validator containing client side java scriupt validation.
Also you learn how to define model layer validation which is in fact rarely used. And there is an interesting diagram that helps you understand how the framework engages
DCErrorHandlerImpl during the page life cycle for handling exceptions thrown by business components when accessing them in the binding context

12: Oracle ADF Best Practices
This chapter summarizes the best practices and coding tips that developers will find useful when building ADF applications. Learning the best practices will help you to avoid common pitfalls that others might have faced.  The content for this chapter is based on input from various teams who have successfully used ADF.

My advise is that you should really buy this book ! It is full of valuable tips and tricks ! When you buy this book, all code samples in this book are available online so you can download these and play with them.
The book is available here.

Get yourself a free Christmas present !

For the contest I have two copies of Oracle ADF Real World Developer’s Guide to be given away to two lucky winners.

How you can win:
To win your copy of this book, all you need to do is come up with a comment below highlighting the reason "why you would like to win this book”.

Please note: Winners residing only in the USA and Europe would get a chance to win print copies. Others would be provided with eBook copies.
Duration of the contest & selection of winners:The contest is valid for 7 days (contest ends 23-12-2012 23:59 GMT) , and is open to everyone. Winners will be selected on the basis of their comment posted.

Wednesday, October 31, 2012

ADF Mobile : Your First Navigation and Device Interaction

Now ADF Mobile is generally availble, it is now time to create your first ADF Mobile application. In this post I will show you how to create a simple application that contains of two pages with navigation. A bonus for this post is that you will see how to get a picture from the filesystem (or by using the device camera) from within your ADF mobile application Getting started To work with ADF mobile you need to download the JDeveloper 11.1.2.3 and the ADF mobile extension and install both. After installing JDeveloper and adding the ADF Mobile extension, you will be able to create a new ADF Mobile Application. In the new gallery you wil find the ‘Mobile Application’ under the applications node.
Accept all the defaults and the JDeveloper application is created for you. What you see are two projects. One called the application controller, and a second one, the viewController. JDeveloper also adds application-level and project-level artifacts.
The applicationController contains several artefacts such as the Datacontrol definition, files for skinning, and a class called LifeCycleListenerImpl. This class can be used to add your own functionality during the different stages of the application life cycle. In the viewController you only see a file called adfmf-feature.xml. This file is used to add, remove, or edit the application features embedded within the mobile application. At an application level, the adfmf-application.xml file is created, which enables you to configure the mobile application. You will also find application level files that are created for you such as platform specific images for splashscreens and application icons. These can be customized.
That is all you need to get started, and luckily, it is all created for you. Your first simple ADF Mobile Application Lets create a two simple java classes to be our data provider.
and ...
Now create a datacontrol based on the Contacts class.
With the datacontrol in place, it is now time to create the page that will use the Contact collection. Creating features, taskflows and pages Go to the adfmf-feature.xml file in order to add a new feature. This can be done by clicking the plus icon. For now, lets call this feature ‘contacts’.
This only adds an entry in the xml file, but the actual page or taskflow implementing the feature is not created. This is also an action that can be done from within the adfmf-feature.xml file. By clicking the plus icon (you must be on the content tab for the feature) you can pick either AMX page or taskflow. Choose taskflow and continue.
The taskflow editor now appears with the empty newly created taskflow. Now it is time to add view activities to the taskflow. If you are familiar with ADF development, this the exact same approach as if you were building a ‘regular’ ADF application. Just drag the viewactivities from the component pallet onto the taskflow diagram and add navigation between them. In this case I created two viewactivities. One to show the list, and a second on create a picture of the selected contact.
Creating the pages The next step is creating the actual pages. This can be done by doubleclicking the view activities on the taskflow diagram. Start with the list page. In the create page wizard, uncheck ‘both’ action checkboxes. There is no need got these now.
On the list page it makes sense to show the content in a ‘List’ layout. With ADF Mobile and JDeveloper you can create this exactly the way you want. Drag and drop the contact collection from the datacontrol onto the page and select ‘ADF Mobile List View’ from the context menu.
In the ListView gallery you can pick from a lot of different Lists, but for now, just stick with the default. For the list view only display the last name. No need for the firstname, however, if you really want to….. just add it. The result should look somewhat like this:
This page will work if all went according to plan. The next step is to add navigation to the second page. Adding navigation In order to navigate to the second page, and to see the selected trainee on this second page you need to do two things. The page needs to know when to navigate. For that, we can use the action property of the component. Change the action property to “add” which corresponds to the navigation case defined in the taskflow. Either type it, or select it from the dropdown.
Next make sure that the selected row is made available on the second page. For this a setPropertyListener can be used (Hey, you already knew that from your ADF experience). Set the from property to #{row}, and the to property to #{pageFlowScope.row}.
Now create the second page by doubleclicking on the viewactivity in the taskflow editor, or via invocing the new gallery and pick create new ADF Mobile Page (AMX). In the header facet the #{pageFlowScope.row} reference can be used to display the whole name of the selected contact. Now create the second page by doubleclicking on the viewactivity in the taskflow editor, or via invocing the new gallery and pick create new ADF Mobile Page (AMX). In the header facet the #{pageFlowScope.row} reference can be used to display the whole name of the selected contact.
 <amx:facet name="header"/>  
 <amx:outputText value="Take picture of #{pageFlowScope.row.firstname} #{pageFlowScope.row.lastname}" id="ot1"/>  
 <;/amx:facet>;  
Creating the picture This page will be used to take a picture of the contact. This looks pretty complicated but as a matter of fact, it is very straightforward. ADF Mobile ships with a deviceFeature datacontrol. On of the operations in here is the ‘getPicture’. Drag this operation from the datacontrol onto your page, and drop it as a ADF Mobile Button.
In the Edit Action Binding set destinationType to 1 so the image is returned as a fileName, and specify width and height for the image.
You might want to play with the sourcetype. On a simulator this makes no sense, but on an actual device you can invoke the camera by setting sourceType = 1. An action binding is added to the corresponding pagedefinition file. Again, you already know this from regular ADF development.
 <methodAction id="getPicture" RequiresUpdateModel="true" Action="invokeMethod" MethodName="getPicture"  
 IsViewObjectMethod="false" DataControl="DeviceFeatures"  
 InstanceName="data.DeviceFeatures.dataProvider"  
 ReturnName="data.DeviceFeatures.methodResults.getPicture_DeviceFeatures_dataProvider_getPicture_result">  
 <NamedData NDName="quality" NDType="int"/>  
 <NamedData NDName="destinationType" NDValue="1" NDType="int"/>  
 <NamedData NDName="sourceType" NDType="int"/>  
 <NamedData NDName="allowEdit" NDType="boolean"/>  
 <NamedData NDName="encodingType" NDType="int"/>  
 <NamedData NDName="targetWidth" NDValue="150" NDType="int"/>  
 <NamedData NDName="targetHeight" NDValue="200" NDType="int"/>  
 </methodAction>  
Now drop the returnvalue of the getPicture from the datacontrol on your page as an outputtext. Remove that textfield immediately. The Dnd action was only nessecary in order to create a binding for this returnvalue. It can now be used as the source for an component.
 <amx:image id="file" source="#{bindings.Return.inputValue}"/>  
Finally add a button to navigate back to the list page. The page would look like this:
 <?xml version="1.0" encoding="UTF-8" ?>  
 <amx:view xmlns:xsi="<a href="http://www.w3.org/2001/XMLSchema-instance">http://www.w3.org/2001/XMLSchema-instance</a>" xmlns:amx="<a href="http://xmlns.oracle.com/adf/mf/amx">http://xmlns.oracle.com/adf/mf/amx</a>"  
 xmlns:dvtm="<a href="http://xmlns.oracle.com/adf/mf/amx/dvt">http://xmlns.oracle.com/adf/mf/amx/dvt</a>">  
 <amx:panelPage id="pp1">  
  <amx:facet name="header">  
    <amx:outputText value="Take picture of #{pageFlowScope.row.firstname} #{pageFlowScope.row.lastname}" id="ot1"/>  
  </amx:facet>  
  <amx:commandButton actionListener="#{bindings.getPicture.execute}" text="getPicture" disabled="#{!bindings.getPicture.enabled}" id="cb1"/>  
  <amx:image id="file" source="#{bindings.Return.inputValue}"/>  
  <amx:commandButton action="return" text="List" id="cb2"/>  
 </amx:panelPage>  
 </amx:view>  
Deploying and testing Before being able to test the application you need to create a deployment profile. Go to your application properties and select “new deployment profile” and create one for ADF Mobile for iOS. Accept the defaults for now.
Now you can deploy the application to an iOS simulator or device. After deploying to an iOS simulator the application works. Click on the application icon to start the application. The app starts and you will see the list view. Click (or tab on a real device) on one of the names in the list view. The Picture view opens empty with the name of the selected contact in the header. Now you can invoke the getPicture button. .
On a real device the camera can be invoked if you would set sourcetype = camera (or 1), on the simulator, you get to pick an image from the gallery. After taking the picture (or selecting it), the image displays in the application, right where we want it.
I created this application on a Macbook so I can use the iOS simulator to run the application. However, the exact same application will run on an iPhone, iPad if you deploy it to the device instead of deploying it to the simulator. And it will also run on Android devices. The only thing you need to do is create a deployment profile for Android and deploy to the actual device. Footnote This blogpost (originally posted on the amis technology blog) is created under the assumption that you have already installed all SDK’s for Android Development, and the xCode for iOS development. Also all settings for Android and iOS development in JDeveloper need to be set and point to the android SDK and xCode locations. Running on Android Simulators is extemely slow, so you will probably need to connect your device and deploy to it in order to test your application. I will propbably write more on these topics in the near future.

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.

Sunday, September 30, 2012

My OOW 2012 Session Schedule, and more

This years visit to Oracle Open World is for me the best of both worlds. First of all I get to attend one of the biggest, if not the biggest, IT conferences in the world. Second, I have two presentations. Both are on Sunday afternoon. The first one is a Fusion Middleware Live Development session where we as a team show you the steps involved in creating an application using nearly all parts of Fusion Middleware. My role in the team is to explain how we build the UI part of the application and how we used ADF to do that. Also I will show you how you can create an interactive dashboard using DVT components such as graphs and gauges. More info on this session can be found here. Right in the middle of this session I have to leave the room in order to go to my next presentation. This presentation is called "mobile development with Oracle JDeveloper and ADF". In this session I show you some of the options that you have if you want to extend your enterprise application to mobile devices. I cannot go into much detail yet. Having said that, I've probably said enough. More info is available here. After my presentation I head straight to the Oracle Benelux Networking Event which is sponsored by AMIS. The rest of the week is also dedicated ADF and to mobile development. Monday, I'll be attending one of the 8 Hand on Labs where one can develop mobile applications for iOS and Android with ADF mobile. Tuesday is a mashup day containing session about ADF, Forms and SOA. After that, on Wednesday I have several more sessions on mobile development. Data Visualization best practices on mobile devices, spatial mashup on mobile devices, and about next generation infrastructure for HTML5 and mobile apps. And maybe I will meet you at the OOW 2012 Bloggers Meetup. Thursday I call a "whatever comes up day", where I will probably do a lot of handson stuff, and in the evening I have diner with all of the AMIS employees that are also at OOW. Keep an eye on this weblog and read all my Oracle Open World news and experiences. Now if your are trying to find me, this is where I am:
The conference season doesn't end here. After Oracle Open World I will present at one more international conference this year. In december I have two presentations at the UKOUG 2012 conference.I'm proud of having presentations at OBUG Connect 2012, ODTUG KScope12, Oracle Open World 2012 and UKOUG Conference 2012.