Skip Headers
Oracle® Fusion Middleware Mobile Developer's Guide for Oracle Application Development Framework
11g Release 1 (11.1.1)

Part Number E10140-02
Go to Documentation Home
Go to Book List
Book List
Go to Table of Contents
Go to Index
Go to Feedback page
Contact Us

Go to previous page
Go to next page
View PDF

3 Component Support

This chapter describes the ADF Components that are supported by ADF Mobile.

This chapter includes the following sections:

3.1 Introduction to Apache My Faces Trinidad Components

ADF Mobile supports more than 60 of Apache MyFaces Trinidad components, enabling you to build applications with a rich component set that renders appropriately to the screens of mobile devices. For more information, refer to the Apache MyFaces Trinidad site (

3.1.1 Supported Features

ADF Mobile supports the following renderer-specific features for the supported browsers:

3.1.2 Partial Page Rendering

The high latency and low bandwidth of networks in mobile environments decrease application responsiveness for mobile users. Screens refresh slowly, diminishing the mobile user experience. ADF Mobile's support of Partial Page Rendering (PPR) compensates for the negative impact that slow connections have on screen updates by minimizing the amount of data requested from the server; using PPR, mobile device screen updates do not require a full refresh. Browsers that do not support AJAX (Asynchronous JavaScript and XML) use full page rendering instead of PPR. For example, a page submission on basic HTML browsers (which do not support JavaScript) results in the refresh of a full page.


Browsers for BlackBerry 4.5 and earlier versions do not support PPR. Specifying the autosubmit attribute on certain form components results in the submission of the page after the user exits the field. A full, not partial, refresh of the page then follows.

3.1.3 Dialogs

ADF Mobile supports dialogs, pages used by applications to obtain user input. Because mobile browsers cannot open a new window that contains a dialog (a pop-up window), dialogs appear as new pages within the main browser window after automatically preserving the state of the current page.

3.1.4 Rendering Specific to the BlackBerry Browser 4.5 and Earlier Browsers

On browsers for BlackBerry 4.5 and earlier versions, the bullets in a list sublevel (such as those in a tr:panelList component) appear large and are not indented. The BlackBerry browser's table handling may affect complex layouts; the BlackBerry browser does not allow horizontal scrolling. Instead, it wraps a table row onto multiple display lines which may disturb the layout. For more information, see Chapter 6, "Design Guidelines for RIM BlackBerry 4.2 to 4.5."

3.2 Input Components

This section describes the ADF Faces core components that support user input. This section includes the following topics:

3.2.1 Creating Input Text Fields

You can create input fields using the following components:

  • tr:inputColor


    Mobile browsers do not support an inline chooseColor or a color dialog for the tr:inputColor component.
  • tr:inputDate

  • tr:inputHidden

  • tr:inputText


    Basic HTML browsers do not support the autosubmit attribute of the tr:inputText component.

3.2.2 Creating Lists

You can create lists using the following components:

  • tr:panelChoice

  • tr:panelList

  • tr:selectBooleanCheckBox

  • tr:selectBooleanRadio

  • tr:selectItem


    Mobile browsers do not support the disabled attribute for the tr:selectItem component.
  • tr:selectManyCheckBox

  • tr:selectManyListBox

  • tr:selectOneChoice

  • tr:selectOneListBox

  • tr:selectOneRadio

  • tr:resetButton


Basic HTML browsers do not support the autosubmit attribute for the tr:resetButton component.

3.3 Output Components

This section describes the Apache MyFacesTrinidad core components that support output on mobile device applications. This section includes the following topics:

3.3.1 Displaying Text

The following components enable you to display text:

  • tr:iterator

  • tr:message

  • tr:messages


    When using the tr:message and tr:messages components, the component-specific messages do not display as they do in a desktop browser. Instead, they display in the region where the message component is placed on the Web page.
  • tr:outputDocument

  • tr:outputForwarded

  • tr:outputLabel

  • tr:outputText

3.3.2 Displaying Images

The following components enable you to display images:

  • tr:icon

  • tr:image

  • tr:panelTip

3.3.3 Showing (or Hiding) Components

The following components enable showing or hiding items:

  • tr:panelAccordion


    Mobile browsers only support a full-page update; they do not support the partialTriggers attribute of the tr:panelAccordion component.
  • tr:panelTabbed


    To save space on mobile devices, the renderer intentionally prevents the display of tab bars on both the top and bottom of the tr:panelTabbed component. Valid values for the attribute positions are top and bottom. If both is specified, then the renderer displays the tabs on top.
  • tr:showDetail


    For the tr:showDetail component, the disclosure arrow does not display; instead [+] and [-] display.
  • tr:showDetailHeader


    For the tr:showDetailHeader component, the disclosure arrow does not appear on mobile browsers.
  • tr:showDetailItem


    For the tr:showDetailItem component, the disclosure arrow does not appear on mobile browsers and flex is not supported.

3.4 Layout Components

The following sections describes the layout components supported by ADF Mobile:

3.4.1 Managing the Page

The following components enable you to manage the page:

  • tr:document

  • tr:form


    Mobile browsers do not support the defaultCommand attribute of the tr:form component.
  • tr:page


Mobile browsers do not support the tr:page facet of the tr:page component.

3.4.2 Laying Out Sections of the Page

The following ADF Faces core tags support page layout for mobile device applications:

  • tr:group

  • tr:panelBorderLayout


    Only the top and bottom facets are supported for the tr:panelBorderLayout component. Mobile browsers do not support the following facets:
    • left

    • right

    • start

    • end

    • innerLeft

    • innerRight

    • innerStart

    • innerEnd

    The tr:panelBorderLayout component does not render if you use any of these unsupported facets.

  • tr:panelBox

  • tr:panelFormLayout

  • tr:panelGroupLayout

  • tr:panelHeader

  • tr:panelHorizontalLayout


    Mobile devices do not support the halign=end in the tr:panelHorizontalLayout component.
  • tr:panelLabelAndMessage

  • tr:panelPage

  • tr:panelPageHeader


    Mobile devices only support the following facets of the tr:panelPageHeader component:
    • branding

    • brandingApp

    • navigation1

    • navigation2

  • tr:panelRadio

  • tr:panelCaptionGroup

3.4.3 Inserting Spaces

The following components control the space allocation on pages:

  • tr:separator

  • tr:spacer

  • tr:subform

3.5 Navigation Components

The following sections describe the components that enable users to navigate to other pages of the application or to external locations.

3.5.1 Creating Buttons

ADF Mobile supports the following button types:

  • tr:commandButton


    Because the text attribute cannot display if the icon attribute has been set, buttons on mobile devices can have either text or an image, but not both. If you set the disabled attribute to true, then the tr:commandButton component with an icon attribute renders as a static image with no links.
  • tr:goButton

See Chapter 7, " Extending ADF Mobile Applications" for information on how to use the tr:goButton component to integrate e-mail, telephony, and Google maps into an application.

3.5.2 Creating Links

ADF Mobile supports the following components for creating hyper-links:

See Chapter 7, " Extending ADF Mobile Applications" for information on how to use the tr:goLink component to integrate e-mail, telephony, and Google maps into an application.

3.5.3 Navigation Components

ADF mobile supports the following navigation components:

  • tr:breadcrumbs

  • tr:commandNavigationItem


    tr:commandNavigationItem does not render when you set the disabled attribute to true for the following:
    • tr:selectOneListBox

    • tr:selectOneChoice

    • tr:processChoiceBar

    • tr:navigationPane with hint, "choice"

    • tr:selectRangeChoiceBar

  • tr:navigationPane


    tr:navigationPane hint = "choice" with a destination value is not supported for basic HTML browsers.
  • tr:train


The tr:train component appears as x of y instead of listing each item. This is a display-only component in ADF Mobile; users cannot navigate through the application by clicking the x of y component. To enable navigation, you must add a separate link or button.

3.6 Data Visualization (Graphs and Gauges)

ADF Mobile supports data visualization components (DVTs) used to create a wide variety of graphs and gauges in mobile application pages, such as the area graph representing a user's bank balance in Figure 3-1.

Figure 3-1 Graph Displays in Mobile Applications

Area graph for a checking account balance

ADF Mobile supports the following types of graphs:

ADF Mobile supports the following types of gauges:

Because Oracle JDeveloper incorporates DVTs, you can quickly add graphs and gauges. To add these components to an application, first move a data control into the editor window using a drag-and-drop operation and then select Trinidad Gauges or Trinidad Graphs from the context menu. For example, Figure 3-2 illustrates the context menu that appears when a data control called BalanceView1 is dragged and dropped into the editor window.

Figure 3-2 Selecting a Data Control

Data control context menu

After you select either the Trinidad Graphs or Trinidad Gauges options, the DVT wizard appears and opens to the Component Gallery page (Figure 3-3), where you select the DVT type.


For Oracle Fusion Middleware 11g release 1, ADF Mobile supports only static graphs and gauges which are rendered as PNG images. Any mobile device that supports this image format can display graphs and gauges.

Figure 3-3 The Component Gallery for the DVT Wizard

DVT wizard Component Gallery

3.7 Tables and Trees

This section includes the following topics:

3.7.1 Creating Tables

ADF Mobile supports tables comprised of the following components:

  • tr:table


    ADF Mobile does not support the allDetailsEnabled attribute for the tr:table component; this attribute is always set to false.
  • tr:column


    When you nest tr:column tags to create column groups, the header facets do not render for the column groups.

3.7.2 Creating Trees

ADF mobile supports the tr:tree component.


tr:tree may not render on basic HTML browsers.

3.8 Unsupported Components and Attributes

This section lists the components and attributes that ADF Mobile 11g does not support and includes the following sections:

3.8.1 Unsupported Components

ADF Mobile 11g does not support the following:

  • tr:chart

  • tr:chooseColor

  • tr:chooseDate

  • tr:inputFile

  • tr:inputListOFVariables

  • tr:inputNumberSpinbox

  • tr:legend

  • tr:media

  • tr:navigationTree

  • tr:panelButtonBar

  • tr:panelPopup

  • tr:panelSideBar

  • tr:poll

  • tr:progressIndicator

  • tr:selectManyShuttle

  • tr:selectOrderShuttle

  • tr:singleStepButtonBar

  • tr:statusIndicator

  • tr:switcher

  • tr:treeTable

3.8.2 Unsupported Attributes

ADF Mobile 11g does not support the following component attributes on any component.

  • accessKey

  • shortDesc (tooltip)