|Oracle® Fusion Middleware Developer's Guide for Application Development Framework Mobile
11g Release 1 (11.1.1)
Part Number E10140-01
This chapter describes the ADF Components that are supported by ADF Mobile. This chapter includes the following topics:
ADF Mobile supports more than 60 of Apache My Faces 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 My Faces Trinidad site (
ADF Mobile supports the following renderer-specific features for the supported browsers:
The high latency and low bandwidth of networks in mobile environments diminish application responsiveness for mobile users. Screens refresh slowly, lessening 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. ADF Mobile supports PPR for Microsoft Pocket Internet Explorer. For this browser, PPR support is limited to the
outputText components as partial targets (that is, these components specify a
partialTriggers attribute) and for the
table component for internal changes, such as sorting.
Note:BlackBerry Browser 4.x does not support PPR. Specifying the
autosubmitattribute on certain form components results in the submission of the page once the user exits the field. A full, not partial, refresh of the page then follows.
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.
On the BlackBerry Browser 4.x, the bullets in a list sublevel (such as those from a
tr:panelList) 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.
This section describes the ADF Faces core components that support user input. This section includes the following topics:
You can create input fields using the following components:
Note:Mobile browsers do not support an inline
You can create lists using the following components:
Note:Mobile browsers do not support the
This section describes the Apache MyFacesTrinidad core components that support output on mobile device applications. This section includes the following topics:
The following components enable you to display text:
Note:When using the
tr:messagescomponents, the component-specific messages do not pop up as they do in a desktop browser. Instead, they display in the region where the message component is placed on the Web page.
The following components enable you to display images:
The following components enable showing or hiding items:
Note:Mobile browsers only support a full-page update; they do not support the
partialTriggersattribute of the
Note:The disclosure arrow does not display; instead [+] and [-] display.
Note:The disclosure arrow does not appear on mobile browsers.
Note:The disclosure arrow does not appear on mobile browsers and
flexis not supported.
The following section describes the layout components supported by ADF Mobile:
The following components enable you to manage the page:
Note:Mobile browsers do not support the
The following ADF Faces core tags support page layout for mobile device applications:
Note:Mobile browsers do not support the following facets:
The following sections describe the components that enable users to navigate to other pages of the application or to external locations.
ADF Mobile supports the following button types:
textattribute cannot display if the
iconattribute has been set, buttons on mobile devices can have either text or an image, but not both. If you set the
true, then the
commandButtoncomponent with an
iconattribute renders as a static image with no links.
ADF Mobile supports the following components for creating hyper-links:
ADF mobile supports the following navigation components:
tr:commandNavigationItem-- The component does not render when you set the
truefor the following components:
tr:navigationPane with hint,
Note:Appears as x of y instead of listing each item.
This section includes the following topics:
ADF Mobile supports tables comprised of the following components:
This section lists the components and attributes that ADF Mobile 11g does not support and includes the following sections:
ADF Mobile 11g does not support the following: