A ADF Faces Configuration

This appendix describes how to configure JSF and ADF Faces features in various XML configuration files, as well as how to retrieve ADF Faces configuration values using the RequestContext API and how to use JavaScript partitioning.

This chapter includes the following sections:

• Section A.1, "Introduction to Configuring ADF Faces"

• Section A.2, "Configuration in web.xml"

• Section A.3, "Configuration in faces-config.xml"

• Section A.4, "Configuration in adf-config.xml"

• Section A.5, "Configuration in adf-settings.xml"

• Section A.6, "Configuration in trinidad-config.xml"

• Section A.7, "Configuration in trinidad-skins.xml"

• Section A.8, "Using the RequestContext EL Implicit Object"

• Section A.9, "Using JavaScript Library Partitioning"

<?xml version = '1.0' encoding = 'windows-1252'?><web-app xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
         xsi:schemaLocation="http://java.sun.com/xml/ns/javaee
         http://java.sun.com/xml/ns/javaee/web-app_2_5.xsd" version="2.5"
         xmlns="http://java.sun.com/xml/ns/javaee">
  <description>Empty web.xml file for Web Application</description>
  <servlet>
    <servlet-name>Faces Servlet</servlet-name>
    <servlet-class>javax.faces.webapp.FacesServlet</servlet-class>
    <load-on-startup>1</load-on-startup>
  </servlet>
  <servlet-mapping>
    <servlet-name>Faces Servlet</servlet-name>
    <url-pattern>/faces/*</url-pattern>
  </servlet-mapping>
  <session-config>
    <session-timeout>35</session-timeout>
  </session-config>
  <mime-mapping>
    <extension>html</extension>
    <mime-type>text/html</mime-type>
  </mime-mapping>
  <mime-mapping>
    <extension>txt</extension>
    <mime-type>text/plain</mime-type>
  </mime-mapping>
</web-app>

<context-param>
  <param-name>oracle.adf.view.rich.LOGGER_LEVEL</param-name>
  <param-value>ALL</param-value>
</context-param>

• javax.faces.DEFAULT_SUFFIX: Use .xhtml as the file extension for documents that use Facelets.

• A.2.3.9 Dialog Prefix

  To change the prefix for launching dialogs, set the org.apache.myfaces.trinidad.DIALOG_NAVIGATION_PREFIX parameter.

  The default is dialog:, which is used in the beginning of the outcome of a JSF navigation rule that launches a dialog (for example, dialog:error).

  A.2.3.10 Compression for CSS Class Names

  You can set the org.apache.myfaces.trinidad.DISABLE_CONTENT_COMPRESSION {/Emphasis> parameter

  The default is false. Set to true if you want to disable the compression.

  Performance Tip:

  In a production environment, set this parameter to false.

  A.2.3.11 Test Automation

  When you set the oracle.adf.view.rich.automation.ENABLED parameter to true and when the component ID attribute is null, the component testId attribute is used during automated testing to ensure the ID is not null. The testId is attribute only on the tag, it is not part of the Java component API.

  Note:

  When this context parameter is set to true, the oracle.adf.view.rich.security.FRAME_BUSTING context parameter behaves as though it is set to never. For more information, see Section A.2.3.16, "Framebusting".

  A.2.3.12 UIViewRoot Caching

  Use the org.apache.myfaces.trinidad.CACHE_VIEW_ROOT parameter to enable or disable UIViewRoot caching. When token client-side state saving is enabled, MyFaces Trinidad can apply an additional optimization by caching an entire UIViewRoot tree with each token. (Note that this does not affect thread safety or session failover.) This is a major optimization for AJAX-intensive systems, as postbacks can be processed far more rapidly without the need to reinstantiate the UIViewRoot tree.

  You set the org.apache.myfaces.trinidad.CACHE_VIEW_ROOT parameter to true to enable caching. This is the default. Set the parameter to false to disable caching.

  Note:

  This type of caching is known to interfere with some other JSF technologies. In particular, the Apache MyFaces Tomahawk saveState component does not work, and template text in Facelets may appear in duplicate.

  A.2.3.13 Themes and Tonal Styles

  Use the oracle.adf.view.rich.tonalstyles.ENABLED parameter to turn the use of tonal styles off or on. While the tonal style classes, .AFDarkTone, .AFMediumTone, .AFLightTone and .AFDefaultTone style classes are still available for the purpose of backward compatibility, themes are provided as a replacement style. Themes are easier to author than tonal styles, rely on fewer selectors, and avoid CSS containment selectors; therefore, they are less prone to bugs. Due to the limitation on the number of selectors in one CSS file, both tonal styles and themes cannot be supported in the same application. Set to false to disable tonal styles.

  A.2.3.14 Partial Page Navigation

  Use the oracle.adf.view.rich.pprNavigation.OPTIONS parameter to turn partial page navigation on and off. By default, the value is off. Partial page navigation uses the same base page throughout the application, and simply replaces the body content of the page with each navigation. This results in better performance as JavaScript libraries and style sheets do not need to be reloaded with each new page. For more information, see Section 7.4, "Partial Page Navigation".

  Valid values are:

  • on: PPR navigation is turned on for the application.

    Note:

    If you set the parameter to on, then you need to set the partialSubmit attribute to true for any command components involved in navigation. (for more information about partialSubmit, see Section 5.1.1, "Events and Partial Page Rendering")

  • off: PPR navigation is turned off for the application.

  • onWithForcePPR: When an action on a command component results in navigation, the action will always be delivered using PPR, as if the component had partialSubmit set to true (for more information about partialSubmit, see Section 5.1.1, "Events and Partial Page Rendering"). Therefore, if the component already has partialSubmit set to true, the framework does nothing. Otherwise, the entire document is refreshed to ensure that old page refresh behavior is preserved. The entire document is also refreshed if the action component does not contain navigation.

  A.2.3.15 JavaScript Partitioning

  Use the oracle.adf.view.rich.libraryPartitioning.ENABLED parameter to turn JavaScript partitioning on and off. By default, the value is true (enabled). JavaScript partitioning allows a page to download only the JavaScript needed by client components for that page.

  Valid values are:

  • true: JavaScript partitioning is enabled (the default).

  • false: JavaScript partitioning is disabled.

  For more information about using and configuring JavaScript partitioning, see Section A.9, "Using JavaScript Library Partitioning".

  A.2.3.16 Framebusting

  Use the oracle.adf.view.rich.security.FRAME_BUSTING context parameter to use framebusting in your application. Framebusting is a way to prevent clickjacking, which occurs when a malicious web site pulls a page from another domain into a frame and overlays it with a counterfeit page, allowing only portions of the original, or clickjacked, page (for example, a button) to display. When the user clicks the button, they in fact are clicking a button on the clickjacked page, causing unexpected results.

  For example, say your application is a web-based email application that resides in DomainA and a web site in DomainB clickjacks your page by creating a page with an IFrame that points to a page in your email application at DomainA. When the two pages are combined, the page from DomainB covers most of your page in the IFrame, and exposes only a button on your page that deletes all email for the account. The user, not knowing they are actually in the email application may click the button and inadvertently delete all their email.

  Framebusting prevents clickjacking by using the following JavaScript to block the application's pages from running in frames:

  top.location.href = location.href;
  

  If you configure your application to use framebusting by setting the parameter to always, then whenever a page tries to run in a frame, an alert is shown to the user that the page is being redirected, and then the above code is run, which causes it to be the topmost page, thereby disallowing the page to run in the frame.

  If your application needs to use frames, you can set the parameter value to differentDomain. This setting causes framebusting to occur only if the frame is in a page that is from a different domain than your application. This is the default setting.

  For example, say you have a page named DomainApage1 in your application that uses a frame to include the page DomainApage2. Say the external DomainBpage1 tries to clickjack the page DomainApage1. The result would be the following window hierarchy:

  • DomainBpage1

    • DomainApage1

      • DomainApage2

  If the application has framebusting set to be differentDomain, then the framework walks the parent window hierarchy to determine whether any ancestor windows are from a different domain. Because DoaminBpage1 is from a different domain, the framebusting JavaScript code will run for the DomainApage1 page, causing it to become the top-level window. And because DomainApage2 is from the same domain as DomainApage1, it will be allowed to run in the frame.

  Valid values are:

  • always: The page will show an error and redirect whenever it attempts to run in a frame.

  • differentDomain: The page will show an error and redirect only when it attempts to run in a frame on a page in a different domain (the default).

  • never: The page can run in any frame on any domain.

    Note:

    This context parameter is ignored and will behave as if it were set to never when either of the following context parameters is set to true:

    • org.apache.myfaces.trinidad.util. ExternalContextUtils.isPortlet

    • oracle.adf.view.rich.automation.ENABLED

  A.2.4 What You May Need to Know About Other Context Parameters in web.xml

  Other optional, application-wide context parameters are:

  • javax.faces.CONFIG_FILE: Specifies paths to JSF application configuration resource files. Use a comma-separated list of application-context relative paths for the value, as shown in the following code. Set this parameter if you use more than one JSF configuration file in your application.

    <context-param>
      <param-name>javax.faces.CONFIG_FILES</param-name>
      <param-value>
       /WEB-INF/faces-config1.xml,/WEB-INF/faces-config2.xml
      </param-value>
    </context-param>
    

  • javax.faces.DEFAULT_SUFFIX: Specifies a file extension (suffix) for JSP pages that contain JSF components. The default value is .jsp.

    Note:

    This parameter value is ignored when you use prefix mapping for the JSF servlet (for example, /faces), which is done by default for you.

  • javax.faces.LIFECYCLE_ID: Specifies a lifecycle identifier other than the default set by the javax.faces.lifecycle.LifecycleFactory.DEFAULT_LIFECYCLE constant.

    Caution:

    Setting this to any other value will break ADF Faces.

  • org.apache.myfaces.trinidad.CHECK_FILE_MODIFICATION: Specifies whether JSP and CSS files require a restart in order to see changes at runtime. By default, set to false. Set to true if you want to be able to view changes without restarting the server.

  A.3 Configuration in faces-config.xml

  The JSF configuration file is where you register a JSF application's resources such as custom validators and managed beans, and define all the page-to-page navigation rules. While an application can have any JSF configuration file name, typically the file name is the faces-config.xml file. Small applications usually have one faces-config.xml file.

  When you use ADF Faces components in your application, JDeveloper automatically adds for you the necessary configuration elements into faces-config.xml. For more information about the faces-config.xml file, see the Java EE 5 tutorial on Sun's web site (http://java.sun.com).

  A.3.1 How to Configure for ADF Faces in faces-config.xml

  In JDeveloper, when you create a project that uses JSF technology, an empty faces-config.xml file is created for you in the /WEB-INF directory. An empty faces-config.xml file is also automatically added for you when you create a new application workspace based on an application template that uses JSF technology (for example, the Java EE Web Application template. For more information, see Section 2.2, "Creating an Application Workspace".

  When you use ADF Faces components in your application, the ADF default render kit ID must be set to oracle.adf.rich. When you insert an ADF Faces component into a JSF page for the first time, or when you add the first JSF page to an application workspace that was created using the Fusion template, JDeveloper automatically inserts the default render kit for ADF components into the faces-config.xml file, as shown in Example A-2.

  Example A-2 ADF Default Render Kit Configuration in faces-config.xml

  <?xml version="1.0" encoding="windows-1252"?>
  <faces-config version="1.2" xmlns="http://java.sun.com/xml/ns/javaee">
    <application>
      <default-render-kit-id>oracle.adf.rich</default-render-kit-id>
    </application>
  </faces-config>
  

  Typically, you would configure the following in then faces-config.xml file:

  • Application resources such as message bundles and supported locales

  • Page-to-page navigation rules

  • Custom validators and converters

  • Managed beans for holding and processing data, handling UI events, and performing business logic

  Note:

  If your application uses the ADF Controller, these items are configured in the adfc-config.xml file. For more information, see the "Getting Started With Task Flows" chapter of the Oracle Fusion Middleware Fusion Developer's Guide for Oracle Application Development Framework.

  In JDeveloper, you can use the declarative overview editor to modify the faces-config.xml file. If you are familiar with the JSF configuration elements, you can use the XML editor to edit the code directly.

  To edit faces-config.xml in JDeveloper:

  1. In the Application Navigator, double-click faces-config.xml to open the file.

     By default, JDeveloper opens the faces-config.xml file in the overview editor, as indicated by the active Overview tab at the bottom of the editor window.

     When you use the overview editor to add for example, managed beans and validators declaratively, JDeveloper automatically updates the faces-config.xml file for you.

  2. To edit the XML code directly in the faces-config.xml file, click Source at the bottom of the editor window.

     When you edit elements in the XML editor, JDeveloper automatically reflects the changes in the Overview editor.

  Tip:

  JSF allows more than one <application> element in a single faces-config.xml file. The Overview mode of the JSF Configuration Editor allows you to edit only the first <application> instance in the file. For any other <application> elements, you will need to edit the file directly using the XML editor.

  A.4 Configuration in adf-config.xml

  The adf-config.xml file is used to configure application-wide features, like security, caching, and change persistence. Other Oracle components also configure properties in this file.

  A.4.1 How to Configure ADF Faces in adf-config.xml

  Before you can provide configuration for your application, you must first create the adf-config.xml file. Then you can add configuration for any application-wide ADF features that your application will use.

  To create and edit adf-config.xml in JDeveloper:

  1. If not already created, create a META-INF directory for your project.

  2. Right-click the META-INF directory, and choose New from the context menu.

  3. In the Categories pane of the New Gallery, under the General node, select XML, and in the Items pane, select XML Document.

     Tip:

     If you don't see the General node, click the All Technologies tab at the top of the Gallery.

  4. Enter adf-config.xml as the file name and save it in the META-INF directory.

  5. In the source editor, replace the generated code with the code shown in Example A-3.

     Example A-3 XML for adf-config.xml File

     <?xml version="1.0" encoding="utf-8" ?>
     <adf-config xmlns="http://xmlns.oracle.com/adf/config"
                 xmlns:ads="http://xmlns.oracle.com/adf/activedata/config">
      
     </adf-config>
     

  6. You can now add the elements needed for the configuration of features you wish to use.

  A.5 Configuration in adf-settings.xml

  The adf-settings.xml file holds project- and library-level settings such as ADF Faces help providers. The configuration settings for the adf-settings.xml files are fixed and cannot be changed during and after application deployment. There can be multiple adf-settings.xml files in an application. ADF settings file users are responsible for merging the contents of their configurations.

  A.5.1 How to Configure for ADF Faces in adf-settings.xml

  Before you can provide configuration for your application, you must first create the adf-settings.xml file. Then you can add the configuration for any project features that your application will use. For more information about configurations in this file, see Section A.5.2, "What You May Need to Know About Elements in adf-settings.xml".

  To create and edit adf-settings.xml in JDeveloper:

  1. If not already created, create a META-INF directory for your project.

  2. Right-click the META-INF directory, and choose New from the context menu.

  3. In the Categories pane of the New Gallery, under the General node, select XML, and in the Items pane, select XML Document.

     Tip:

     If you don't see the General node, click the All Technologies tab at the top of the Gallery.

  4. In the source editor, replace the generated code with the code shown in Example A-4, with the correct settings for your web application root.

     Example A-4 XML for adf-settings.xml File

     <adf-settings xmlns="http://xmlns.oracle.com/adf/settings"
                   xmlns:wap="http://xmlns.oracle.com/adf/share/http/config" >
       <wap:adf-web-config xmlns="http://xmlns.oracle.com/adf/share/http/config">
         <web-app-root rootName="myroot" />
       </wap:adf-web-config>
     </adf-settings>
     

  5. You can now add the elements needed for the configuration of features you wish to use. For more information, see Section A.5.2, "What You May Need to Know About Elements in adf-settings.xml".

  A.5.2 What You May Need to Know About Elements in adf-settings.xml

  The following configuration elements are supported in the adf-settings.xml file.

  A.5.2.1 Help System

  You register the help provider used by your help system using the following elements:

  • <adf-faces-config>: A parent element that groups ADF Faces specific configurations.

  • <prefix-characters>: The provided prefix if the help provider is to supply help topics only for help topic IDs beginning with a certain prefix. This can be omitted if prefixes are not used.

  • <help-provider-class>: The help provider class.

  • <custom-property> and <property-value>: A property element that defines the parameters the help provider class accepts.

  Example A-5 shows an example of a registered help provider. In this case, there is only one help provider for the application, so there is no need to include a prefix.

  Example A-5 Help Provider Registration

  <adf-settings xmlns="http://xmlns.oracle.com/adf/settings">
  <adf-faces-config xmlns="http://xmlns.oracle.com/adf/faces/settings">
    <help-provider prefix="MYAPP">
      <help-provider-class>
        oracle.adfdemo.view.webapp.MyHelpProvider
      </help-provider-class>
      <property>
        <property-name>myCustomProperty</property-name>
        <value>someValue</value>
      </property>
    </help-provider>
  </adf-faces-config>
  </adf-settings>
  

  A.6 Configuration in trinidad-config.xml

  When you create a JSF application using ADF Faces components, you configure ADF Faces features (such as skin family and level of page accessibility support) in the trinidad-config.xml file. Like faces-config.xml, the trinidad-config.xml file has a simple XML structure that enables you to define element properties using the JSF Expression Language (EL) or static values.

  A.6.1 How to Configure ADF Faces Features in trinidad-config.xml

  In JDeveloper, when you insert an ADF Faces component into a JSF page for the first time, a starter trinidad-config.xml file is automatically created for you in the /WEB-INF directory. Example A-6 shows a starter trinidad-config.xml file.

  Example A-6 Starter trinidad-config.xml File Created by JDeveloper

  <?xml version="1.0" encoding="windows-1252"?>
  <trinidad-config xmlns="http://xmlns.oracle.com/trinidad/config">
   
    <skin-family>blafplus-rich</skin-family>
   
  </trinidad-config>
  

  By default, JDeveloper configures the blafplus-rich skin family for a JSF application that uses ADF Faces. You can change this to blafplus-medium, simple, or use a custom skin. If you wish to use a custom skin, create the trinidad-skins.xml configuration file, and modify trinidad-config.xml file to use the custom skin. For more information about creating custom skins, see Chapter 20, "Customizing the Appearance Using Styles and Skins".

  Typically, you would configure the following in the trinidad-config.xml file:

  • Page animation

  • Level of page accessibility support

  • Time zone

  • Enhanced debugging output

  • Oracle Help for the Web (OHW) URL

  You can also register a custom file upload processor for uploading files.

  In JDeveloper, you can use the XML editor to modify the trinidad-config.xml file.

  To edit trinidad-config.xml in JDeveloper:

  1. In the Application Navigator, double-click trinidad-config.xml to open the file in the XML editor.

  2. If you are familiar with the element names, enter them in the editor. Otherwise use the Structure window to help you insert them.

  3. In the Structure window:

     1. Right-click an element to choose from the Insert before or Insert after menu, and click the element you wish to insert.

     2. Double-click the newly inserted element in the Structure window to open it in the properties editor. Enter a value or select one from a dropdown list (if available).

        In most cases you can enter either a JSF EL expression (such as #{view.locale.language=='en' ? 'minimal' : 'blafplus-rich'}) or a static value (for example., <debug-output>true</debug-output>). EL expressions are dynamically reevaluated on each request, and must return an appropriate object (for example, a Boolean object).

  For a list of the configuration elements you can use, see Section A.6.2, "What You May Need to Know About Elements in trinidad-config.xml".

  Once you have configured the trinidad-config.xml file, you can retrieve the property values programmatically or by using JSF EL expressions. For more information, see Section A.8, "Using the RequestContext EL Implicit Object".

  A.6.2 What You May Need to Know About Elements in trinidad-config.xml

  All trinidad-config.xml files must begin with a <trinidad-config> element in the http://myfaces.apache.org/trinidad/config XML namespace. The order of elements inside of <trinidad-config> does not matter. You can include multiple instances of any element.

  A.6.2.1 Animation Enabled

  Certain ADF Faces components use animation when rendering. For example, trees and tree tables use animation when expanding and collapsing nodes. The following components use animation when rendering:

  • Table detail facet for disclosing and undisclosing the facet

  • Trees and tree table when expanding and collapsing nodes

  • Menus

  • Popup selectors

  • Dialogs

  • Note windows and message displays

  The type and time of animation used is configured as part of the skin for the application. For more information, see Chapter 20, "Customizing the Appearance Using Styles and Skins".

  You can set the animation-enabled element to either true or false, or you can use an EL expression that resolves to either true or false.

  A.6.2.2 Skin Family

  As described in Section A.6.1, "How to Configure ADF Faces Features in trinidad-config.xml", JDeveloper by default uses the blafplus-rich skin family for a JSF application that uses ADF Faces. You can change the <skin-family> value to blafplus-medium, simple, or use a custom skin. For information about creating and using custom skins, see Chapter 20, "Customizing the Appearance Using Styles and Skins".

  You can use an EL expression for the skin family value, as shown in the following code:

  <skin-family>#{prefs.proxy.skinFamily}</skin-family>
  

  A.6.2.3 Time Zone and Year

  To set the time zone used for processing and displaying dates, and the year offset that should be used for parsing years with only 2 digits, use the following elements:

  • <time-zone>: By default, ADF Faces uses the time zone used by the client browser. If needed, you can use an EL expression that evaluates to a TimeZone object. This value is used by org.apache.myfaces.trinidad.converter.DateTimeConverter while converting strings to Date.

  • <two-digit-year-start>: This defaults to the year 1950 if no value is set. If needed, you can use a static, integer value or an EL expression that evaluates to an Integer object. This value is used by org.apache.myfaces.trinidad.converter.DateTimeConverter to convert strings to Date.

  A.6.2.4 Enhanced Debugging Output

  By default, the <debug-output> element is false. ADF Faces enhances debugging output when you set <debug-output> to true. The following features are then added to debug output:

  • Automatic indenting

  • Comments identifying which component was responsible for a block of HTML

  • Detection of unbalanced elements, repeated use of the same attribute in a single element, or other malformed markup problems

  • Detection of common HTML errors (for example, <form> tags inside other <form> tags or <tr> or <td> tags used in invalid locations).

  Performance Tip:

  Set this parameter to false in a production environment.

  A.6.2.5 Page Accessibility Level

  Use <accessibility-mode> to define the level of accessibility support in an application. The supported values are:

  • default: Output supports accessibility features.

  • inaccessible: Accessibility-specific constructs are removed to optimize output size.

  • screenReader: Accessibility-specific constructs are added to improve behavior under a screen reader (but may have a negative effect on other users. For example, access keys are not displayed if the accessibility mode is set to screen reader mode).

  Use <accessibility-profile> to configure the color contrast and font size used in the application. The supported values are:

  • high-contrast: Application displays using high-contrast instead of the default contrast.

  • large-fonts: Application displays using large fonts instead of the default size fonts.

  To use more than one setting, separate the values with a space.

  A.6.2.6 Language Reading Direction

  By default, ADF Faces page rendering direction is based on the language being used by the browser. You can, however, explicitly set the default page rendering direction in the <right-to-left> element by using an EL expression that evaluates to a Boolean object, or by using true or false, as shown in the following code:

  <!-- Render the page right-to-left for Arabic -->
  <!-- and left-to-right for all other languages -->
  <right-to-left>
   #{view.locale.language=='ar' ? 'true' : 'false'}
  </right-to-left>
  

  A.6.2.7 Currency Code and Separators for Number Groups and Decimal Points

  To set the currency code to use for formatting currency fields, and define the separator to use for groups of numbers and the decimal point, use the following elements:

  • <currency-code>: Defines the default ISO 4217 currency code used by org.apache.myfaces.trinidad.converter.NumberConverter class to format currency fields that do not specify an explicit currency code in their own converter. Use a static value or an EL expression that evaluates to a String object. For example:

    <!-- Set the currency code to US dollars. -->
    <currency-code>USD</currency-code>
    

  • <number-grouping-separator>: Defines the separator used for groups of numbers (for example, a comma). ADF Faces automatically derives the separator from the current locale, but you can override this default by specifying a value in this element. You can use a static value or an EL expression that evaluates to a Character object. If set, this value is used by org.apache.myfaces.trinidad.converter.NumberConverter class while parsing and formatting.

    <!-- Set the number grouping separator to period for German -->
    <!-- and comma for all other languages -->
    <number-grouping-separator>
     #{view.locale.language=='de' ? '.' : ','}
    </number-grouping-separator>
    

  • <decimal-separator>: Defines the separator (for example., a period or a comma) used for the decimal point. ADF Faces automatically derives the separator from the current locale, but you can override this default by specifying a value in this element. You can use a static value or an EL expression that evaluates to a Character object. If set, this value is used by org.apache.mtfaces.trinidad.converter.NumberConverter class while parsing and formatting.

    <!-- Set the decimal separator to comma for German -->
    <!-- and period for all other languages -->
    <decimal-separator>
     #{view.locale.language=='de' ? ',' : '.'}
    </decimal-separator>
    

  A.6.2.8 Formatting Dates and Numbers Locale

  By default, ADF Faces and MyFaces Trinidad will format dates (including the first day of the week) and numbers in the same locale used for localized text (which by default is the locale of the browser). If, however, you want dates and numbers formatted in a different locale, you can use the <formatting-locale> element, which takes an IANA-formatted locale (for example, ja, fr-CA) as its value. The contents of this element can also be an EL expression pointing at an IANA string or a java.util.Locale object.

  A.6.2.9 Output Mode

  To change the output mode ADF Faces uses, set the <output-mode> element, using one of these values:

  • default: The default page output mode (usually display).

  • printable: An output mode suitable for printable pages.

  • email: An output mode suitable for emailing a page's content.

  A.6.2.10 Number of Active PageFlowScope Instances

  By default ADF Faces sets the maximum number of active PageFlowScope instances at any one time to 15. Use the <page-flow-scope-lifetime> element to change the number. Unlike other elements, you must use a static value; EL expressions are not supported.

  A.6.2.11 Custom File Uploaded Processor

  Most applications do not need to replace the default UploadedFileProcessor instance provided in ADF Faces, but if your application must support uploading of very large files, or if it relies heavily on file uploads, you may wish to replace the default processor with a custom UploadedFileProcessor implementation.

  For example, you could improve performance by using an implementation that immediately stores files in their final destination, instead of requiring ADF Faces to handle temporary storage during the request. To replace the default processor, specify your custom implementation using the <uploaded-file-processor> element, as shown in the following code:

  <uploaded-file-processor>
   com.mycompany.faces.myUploadedFileProcessor
  </uploaded-file-processor>
  

  A.6.2.12 Client-Side Validation and Conversion

  ADF Faces validators and converters support client-side validation and conversion as well as server-side validation and conversion. ADF Faces client-side validators and converters work the same way as the server-side validators and converters, except that JavaScript is used on the client.

  The JavaScript-enabled validators and converters run on the client when the form is submitted; thus errors can be caught without a server round-trip.

  The <client-validation-disabled> configuration element is not supported in the rich client version of ADF Faces. This means you cannot turn off client-side validation and conversion in ADF Faces applications.

  A.7 Configuration in trinidad-skins.xml

  By default, JDeveloper uses the blafplus-rich skin family when you create JSF pages with ADF Faces components. The skin family is configured in the trinidad-config.xml file, as described in Section A.6.1, "How to Configure ADF Faces Features in trinidad-config.xml". If you wish to use a custom skin for your application, create a trinidad-skins.xml file, which is used to register custom skins in an application.

  For detailed information about creating custom skins, see Chapter 20, "Customizing the Appearance Using Styles and Skins".

  A.8 Using the RequestContext EL Implicit Object

  In ADF Faces, you can use the EL implicit object requestContext to retrieve values from configuration properties defined in the trinidad-config.xml file. The requestContext implicit object, which is an instance of the org.apache.myfaces.trinidad.context.RequestContext class, exposes several properties of type java.util.Map, enabling you to use JSF EL expressions to retrieve context object property values.

  For example, the EL expression #{requestContext} returns the RequestContext object itself, and the EL expression #{requestContext.skinFamily} returns the value of the <skin-family> element from the trinidad-config.xml file.

  You can also use EL expressions to bind a component attribute value to a property of the requestContext implicit object. For example, in the EL expression that follows, the <currency-code> property is bound to the currencyCode attribute value of the JSF ConvertNumber component:

  <af:outputText>
    <f:convertNumber currencyCode="#{requestContext.currencyCode}"/>
  </af:outputText>
  

  The requestContext implicit object properties you can use include the following:

  • requestContext.accessibilityMode: Returns the value of the <accessibility-mode> element from the trinidad-config.xml file.

  • requestContext.agent: Returns an object that describes the client agent that is making the request and that is to display the rendered output. The properties in the agent object include:

    • agentName: Canonical name of the agent browser, (for example, gecko and ie).

    • agentVersion: Version number of the agent browser.

    • capabilities: Returns a Map of capability names (for example, height, width) and their values for the current client request.

    • hardwareMakeModel: Canonical name of the hardware make, and model (for example, nokia6600 and sonyericssonP900).

    • platformName: Canonical name of the platform (for example, ppc, windows, and mac).

    • platformVersion: Version number of the platform.

    • type: Agent type (for example, desktop, pda, and phone).

  • requestContext.clientValidationDisabled: Returns the value of the <client-validation-disabled> element from the trinidad-config.xml file.

  • requestContext.colorPalette: Returns a Map that takes color palette names as keys, and returns the color palette as a result. Each color palette is an array of java.awt.Color objects. Provides access to four standard color palettes:

    • web216: The 216 web-safe colors

    • default49: A 49-color palette, with one fully transparent entry

    • opaque40: A 49-color palette, without a fully transparent entry

    • default80: An 80-color palette, with one fully transparent entry

  • requestContext.currencyCode: Returns the value of the <currency-code> element from the trinidad-config.xml file.

  • requestContext.debugOutput: Returns the value of the <debug-output> element from the trinidad-config.xml file.

  • requestContext.decimalSeparator: Returns the value of the <decimal-separator> element from the trinidad-config.xml file.

  • requestContext.formatter: Returns a Map object that performs message formatting with a recursive Map structure. The first key must be the message formatting mask, and the second key is the first parameter into the message.

  • requestContext.helpSystem: Returns a Map object that accepts help system properties as keys, and returns a URL as a result. For example, the EL expression #{requestContext.helpSystem['frontPage']} returns a URL to the front page of the help system. This assumes you have configured the <oracle-help-servlet-url> element in the trinidad-config.xml file.

  • requestContext.helpTopic: Returns a Map object that accepts topic names as keys, and returns an URL as a result. For example, the EL expression #{requestContext.helpTopic['foo']} returns a URL to the help topic "foo". This assumes you have configured the <oracle-help-servlet-url> element in the trinidad-config.xml file.

  • requestContext.numberGroupingSeparator: Returns the value of the <number-grouping-separator> element from the trinidad-config.xml file.

  • requestContext.oracleHelpServletUrl: Returns the value of the <oracle-help-servlet-url> element from the trinidad-config.xml file.

  • requestContext.outputMode: Returns the value of the <output-mode> element from the trinidad-config.xml file.

  • requestContext.pageFlowScope: Returns a Map of objects in the pageFlowScope object.

  • requestContext.rightToLeft: Returns the value of the <right-to-left> element from the trinidad-config.xml file.

  • requestContext.skinFamily: Returns the value of the <skin-family> element from the trinidad-config.xml file.

  • requestContext.timeZone: Returns the value of the <time-zone> element from the trinidad-config.xml file.

  • requestContext.twoDigitYearStart: Returns the value of the <two-digit-year-start> element from the trinidad-config.xml file.

  For a complete list of properties, refer to the Javadoc for org.apache.myfaces.trinidad.context.RequestContext.

  Note:

  One instance of the org.apache.myfaces.trinidad.context.RequestContext class exists per request. The RequestContext class does not extend the JSF FacesContext class.

  To retrieve a configuration property programmatically, first call the static getCurrentInstance() method to get an instance of the RequestContext object, then call the method that retrieves the desired property, as shown in the following code:

  RequestContext context = RequestContext.getCurrentInstance();
  
  // Get the time-zone property
  TimeZone zone = context.getTimeZone();
  
  // Get the right-to-left property
  if (context.isRightToLeft())
  {
    .
    .
    .
  }
  

  A.9 Using JavaScript Library Partitioning

  ADF Faces groups its components' JavaScript files into JavaScript features. A JavaScript feature is a collection of JavaScript files associated with a logical identifier that describes the feature. For example, the panelStretchLayout client component is comprised of the following two JavaScript files

  • oracle/adf/view/js/component/rich/layout/AdfRichPanelStretchLayout.js

  • oracle/adfinternal/view/js/laf/dhtml/rich/AdfDhtmlPanelStretchLayoutPeer.js

  These two files are grouped into the AdfRichPanelStretchLayout feature.

  JavaScript features are further grouped into JavaScript partitions. JavaScript partitions allow you to group JavaScript features into larger collections with the goal of influencing the download size and number of round trips. For example, since the panelStretchLayout component is often used with the panelSplitter component, the features for these two components are grouped together in the stretch partition, along with the other ADF Faces layout components that can stretch their children. At runtime, when a page is loaded, the framework determines the components used on the page, and then from that, determines which features are needed (feature names are the same as the components' constructor name). Only the partitions that contain those features are downloaded.For more information about JavaScript partitioning, see Section 1.2.1.2, "JavaScript Library Partitioning".

  Features and partitions are defined using configuration files. ADF Faces ships with a default features and partitions configuration files. You can overwrite the default partitions file by creating your own implementation. When you create custom ADF Faces components, you can create your own features and partition configuration files for those components.

  By default, JavaScript partitioning is turned on. Whether or not your application uses JavaScript partitioning is determined by a context parameter in the web.xml file. For more information about enabling or disabling JavaScript partitioning, see Section A.2.3.15, "JavaScript Partitioning"

  A.9.1 How to Create a JavaScript Feature

  You create a JavaScript feature by creating an adf-js-features.xml file, and then adding entries for the features.

  Note:

  You create JavaScript features when you create custom ADF Faces components. All existing ADF Faces components already have features created for them, and these cannot be changed.

  To create a JavaScript feature:

  1. If not already created, create a META-INF directory for your component.

  2. Right-click the META-INF directory, and choose New from the context menu.

  3. In the Categories pane of the New Gallery, under the General node, select XML, and in the Items pane, select XML Document.

     Tip:

     If you don't see the General node, click the All Technologies tab at the top of the Gallery.

  4. Enter adf-js-features.xml as the file name and save it in the META-INF directory.

  5. In the source editor, replace the generated code with the code shown in Example A-3.

     Example A-7 XML for adf-js-features.xml File

     <?xml version="1.0" encoding="utf-8" ?>
     <adf-js-features xmlns="http://xmlns.oracle.com/adf/faces/feature"
      
     </adf-js-features>
     

  6. Add the following elements to populate a feature with the relevant component files and dependencies.

     • features: The root element of the configuration file.

     • feature: Create as a child to the features element. This element must contain one feature-name child element and can also contain any number of feature-class as well as any number of feature-dependency elements.

     • feature-name: Create as a child to the feature element. Specifies the name of the feature. You must use the client component's constructor name for this value.

     • feature-class: Create as a child to the feature element. Specifies the location of the single JavaScript file or class to be included in this feature. There can be multiple feature-class elements.

     • feature-dependency: Create as a child to the feature element. Specifies the name of another feature that this feature depends on. For example, if one component B extends component A, then the feature that represents component A must be listed as a dependency for component B. By noting dependencies, the framework can ensure any dependent classes are available, even if the two features are not in the same partition.

     Example A-8 shows the feature element for a fictitious custom component that uses popup components (and therefore has a dependency to the popup feature).

     Example A-8 JavaScript Features Configuration

     <features xmlns="http://xmlns.oracle.com/adf/faces/feature">
       <feature>
         <feature-name>AcmeMyPane</feature-name>
         <feature-class>
           oracle/adfdemo/acme/js/component/AcmeMyPane.js
         </feature-class>
         <feature-class>
           oracle/adfdemo/acme/js/event/AcmePaneSelectEvent.js
         </feature-class>
         <feature-class>
           oracle/adfdemo/acme/js/component/AcmeMyPanePeer.js
         </feature-class>
     
       <!-- Dependencies -->
      
       <!-- Popup hints -->
       <feature-dependency>AdfRichPopup</feature-dependency>
      
     </feature>
     

  A.9.2 How to Create JavaScript Partitions

  You create a JavaScript partition by creating an adf-js-partitions.xml file, and then adding entries for the features.

  Note:

  ADF Faces provides a default adf-js-partitions.xml file (see Example A-11). If you want to change the partition configuration, you need to create your own complete adf-js-partitions.xml file. At runtime, the framework will search the WEB-INF directory for that file. If one is not found, it will load the default partition file.

  To create JavaScript partitions:

  1. Right-click the WEB-INF directory, and choose New from the context menu.

  2. In the Categories pane of the New Gallery, under the General node, select XML, and in the Items pane, select XML Document.

     Tip:

     If you don't see the General node, click the All Technologies tab at the top of the Gallery.

  3. Enter adf-js-partitions.xml as the file name and save it in the WEB-INF directory.

  4. In the source editor, replace the generated code with the code shown in Example A-3.

     Example A-9 XML for adf-js-partitions.xml File

     <?xml version="1.0" encoding="utf-8" ?>
     <adf-js-features xmlns="http://xmlns.oracle.com/adf/faces/partition"
      
     </adf-js-partitions>
     

  5. Add the following elements to populate a partition with the relevant features.

     • partitions: The root element of the configuration file.

     • partition: Create as a child to the partitions element. This element must contain one partition-name child element and one or more feature elements.

     • partition-name: Create as a child to the partition element. Specifies the name of the partition. This value will be used to produce a unique URL for this partition's JavaScript library.

     • feature: Create as a child to the partition element. Specifies the feature to be included in this partition. There can be multiple feature elements.

     Tip:

     Any feature configured in the adf-js-features.xml file that does not appear in a partition is treated as if it is in its own partition

     Example A-10 shows the partition element for the tree partition that contains the AdfRichTree and AdfRichTreeTable features.

     Example A-10 JavaScript Partition Configuration

     <partition>
       <partition-name>tree</partition-name>
       <feature>AdfUITree</feature>
       <feature>AdfUITreeTable</feature>
       <feature>AdfRichTree</feature>
       <feature>AdfRichTreeTable</feature>
     </partition>
     

  A.9.3 What Happens at Runtime: JavaScript Partitioning

  ADF Faces loads the library partitioning configuration files at application initialization time. First, ADF Faces searches for all adf-js-features.xml files in the META-INF directory and loads all that are found (including the ADF Faces default feature configuration file).

  For the partition configuration file, ADF Faces looks for a single file named adf-js-partitions.xml in the WEB-INF directory. If no such file is found, the ADF Faces default partition configuration is used.

  During the render traversal, ADF Faces collects information about which JavaScript features are required by the page. At the end of the traversal, the complete set of JavaScript features required by the (rendered) page contents is known. Once the set of required JavaScript features is known, ADF Faces uses the partition configuration file to map this to the set of required partitions. Given the set of required partitions, the HTML <script> references to these partitions are rendered just before the end of the HTML document.

  A.9.4 What You May Need to Know About the ADF Faces Features

  Following are the ADF Faces features broken down by category.

  Table A-1 contains framework bootstrap features that are present on every page.

  Table A-1 Bootstrap Features

  Name	Description
  AdfBootstrap	The partition containing the AdfBootstrap feature is the first library partition to be loaded on every page.
  AdfCore	The partition containing the AdfCore feature is loaded on every page immediate following AdfPage construction.

  
  

  Table A-2 contains features that correspond to component base classes.

  Table A-2 Base Component Features

  Name	Description
  AdfUICalendar	Base feature class for the calendar components
  AdfUIChoose	Base feature class for choose components
  AdfUICollection	Base feature class for collection components
  AdfUIColumn	Base feature class for the column components
  AdfUICommand	Base feature class for command components
  AdfUIDeclarativeComponent	Base feature class for declarative components
  AdfUIDecorateCollection	Base feature class for decorate collection components
  AdfUIDialog	Base feature class for dialog components
  AdfUIDocument	Base feature class for the document component
  AdfUIEditableValue	Base feature class for editable value components
  AdfUIForm	Base feature class for the form component
  AdfUIGo	Base feature class for go components
  AdfUIInclude	Base feature class for include components
  AdfUIInput	Base feature class for input components
  AdfUIInputPopup	Base feature class for input popup components
  AdfUIIterator	Base feature class for iterator components
  AdfUIMessage	Base feature class for message components
  AdfUIMessages	Base feature class for messages components
  AdfUINavigationLevel	Base feature class for navigation level components
  AdfUINavigationPath	Base feature class for navigation path components
  AdfUIObject	Base feature class for object components
  AdfUIOutput	Base feature class for output components
  AdfUIPanel	Base feature class for panel components
  AdfUIPoll	Base feature class for poll components
  AdfUIPopup	Base feature class for popup components
  AdfUIProcess	Base feature class for process components
  AdfUIProgress	Base feature class for progress components
  AdfUIQuery	Base feature class for query components
  AdfUIRegion	Base feature class for region components
  AdfUIReset	Base feature class for reset components
  AdfUISelectBoolean	Base feature class for selectBoolean components
  AdfUISelectInput	Base feature class for selectInput components
  AdfUISelectMany	Base feature class for selectMany components
  AdfUISelectOne	Base feature class for selectOne components
  AdfUISelectOrder	Base feature class for selectOrder components
  AdfUIShowDetail	Base feature class for showDetail components
  AdfUIShowMany	Base feature class for showMany components
  AdfUIShowOne	Base feature class for showOne components
  AdfUISubform	Base feature class for the subform component
  AdfUITable2	Base feature class for table2 components
  AdfUITable	Base feature class for the table components
  AdfUITree	Base feature class for the tree component
  AdfUITreeTable	Base feature class for the treeTable component
  AdfUIValue	Base feature class for value components

  
  

  Table A-3 contains features that correspond to concrete component classes.

  Table A-3 Concrete Component Features

  Name	Component
  AdfRichBreadCrumbs	breadCrumbs
  AdfRichCalendar	calendar
  AdfRichChooseColor	chooseColor
  AdfRichChooseDate	chooseDate
  AdfRichColumn	column
  AdfRichCommandButton	commandButton
  AdfRichCommandImageLink	commandImageLink
  AdfRichCommandLink	commandLink
  AdfRichCommandMenuItem	commandMenuItem
  AdfRichCommandNavigationItem	commandNavigationItem
  AdfRichCommandToolbarButton	commandToolbarButton
  AdfRichCommandTrainStop	commandTrainStop
  AdfRichDeclarativeComponent	declarativeComponent
  AdfRichDecorativeBox	decorativeBox
  AdfRichDialog	dialog
  AdfRichDocument	document
  AdfRichForm	form
  AdfRichGoButton	goButton
  AdfRichGoLink	goLink
  AdfRichGoMenuItem	goMenuItem
  AdfRichIcon	icon
  AdfRichImage	image
  AdfRichInlineFrame	inlineFrame
  AdfRichInputColor	inputColor
  AdfRichInputComboboxListOfValues	inputComboboxListOfValues
  AdfRichInputDate	inputDate
  AdfRichInputFile	inputFile
  AdfRichInputListOfValues	inputListOfValues
  AdfRichInputNumberSlider	inputNumberSlider
  AdfRichInputNumberSpinbox	inputNumberSpinbox
  AdfRichInputRangeSlider	inputRangeSlider
  AdfRichInputText	inputText
  AdfRichMedia	media
  AdfRichMenu	menu
  AdfRichMenuBar	menuBar
  AdfRichMessage	message
  AdfRichMessages	messages
  AdfRichNavigationPane	navigationPane
  AdfRichNoteWindow	noteWindow
  AdfRichOutputFormatted	outputFormatted
  AdfRichOutputLabel	outputLabel
  AdfRichOutputText	outputText
  AdfRichPanelAccordion	panelAccordion
  AdfRichPanelBorderLayout	panelBorderLayout
  AdfRichPanelBox	panelBox
  AdfRichPanelCollection	panelCollection
  AdfRichPanelDashboard	panelDashboard
  AdfRichPanelFormLayout	panelFormLayout
  AdfRichPanelGroupLayout	panelGroupLayout
  AdfRichPanelHeader	panelHeader
  AdfRichPanelLabelAndMessage	panelLabelAndMessage
  AdfRichPanelList	panelList
  AdfRichPanelSplitter	panelSplitter
  AdfRichPanelStretchLayout	panelStretchLayout
  AdfRichPanelTabbed	panelTabbed
  AdfRichPanelWindow	panelWindow
  AdfRichPoll	poll
  AdfRichPopup	popup
  AdfRichProgressIndicator	progressIndicator
  AdfRichQuery	query
  AdfRichQuickQuery	quickQuery
  AdfRichRegion	region
  AdfRichResetButton	resetButton
  AdfRichSelectBooleanCheckbox	selectBooleanCheckbox
  AdfRichSelectBooleanRadio	selectBooleanRadio
  AdfRichSelectManyCheckbox	selectManyCheckbox
  AdfRichSelectManyChoice	selectManyChoice
  AdfRichSelectManyListbox	selectManyListbox
  AdfRichSelectManyShuttle	selectManyShuttle
  AdfRichSelectOneChoice	selectOneChoice
  AdfRichSelectOneListbox	selectOneListbox
  AdfRichSelectOneRadio	selectOneRadio
  AdfRichSelectOrderShuttle	selectOrderShuttle
  AdfRichSeparator	separator
  AdfRichShowDetail	showDetail
  AdfRichShowDetailHeader	showDetailHeader
  AdfRichShowDetailItem	showDetailItem
  AdfRichSpacer	spacer
  AdfRichStatusIndicator	statusIndicator
  AdfRichSubform	subform
  AdfRichTable	table
  AdfRichTextEditor	textEditor
  AdfRichToolbar	toolbar
  AdfRichToolbox	toolbox
  AdfRichTrain	train
  AdfRichTrainButtonBar	trainButtonBar
  AdfRichTree	tree
  AdfRichTreeTable	treeTable

  
  

  Table A-4 contains features that correspond to behaviors.

  Table A-4 Behavior Component Features

  Name	Behavior
  AdfAttributeDragSource	attributeDragSource
  AdfAttributeDropTarget	attributeDropTarget
  AdfCalendarDragSource	calendarDragSource
  AdfCalendarDropTarget	calendarDropTarget
  AdfCollectionDragSource	collectionDragSource
  AdfCollectionDropTarget	collectionDropTarget
  AdfComponentDragSource	componentDragSource
  AdfDashboardDropTarget	dashboardDropTarget
  AdfDropTarget	dropTarget
  AdfInsertTextBehavior	insertTextBehavior
  AdfPanelDashboardBehavior	panelDashboardBehavior
  AdfRichTextEditorInsertBehavior	richTextEditorInsertBehavior
  AdfScrollComponentIntoViewBehavior	scrollComponentIntoViewBehavior
  AdfShowPopupBehavior	showPopupBehavior
  AdfShowPrintablePageBehavior	showPrintablePageBehavior
  AdfStampedDropTarget	stampedDropTarget

  
  

  Table A-5 contains features that correspond to framework services.

  Table A-5 Framework Features

  Name	Description
  AdfActiveDataService	Base active data service support
  AdfDragAndDrop	Base drag and drop support
  AdfEndUserMonitoring	Base end user monitoring support
  AdfInlineEditing	Base inline editing support

  
  

  A.9.5 What You May Need to Know About the adf-js-partitions.xml File

  Example A-11 shows the default ADF Faces adf-js-partitions.xml file. You can override the partitions in this file by creating your own partitions file. For more information, see Section A.9.2, "How to Create JavaScript Partitions".

  Example A-11 The Default adf-js-partitions.xml File

  <?xml version="1.0" encoding="utf-8"?>
   
  <partitions xmlns="http://xmlns.oracle.com/adf/faces/partition">
   
    <partition>
      <partition-name>boot</partition-name>
      <feature>AdfBootstrap</feature>
    </partition>
   
    <partition>
      <partition-name>core</partition-name>
   
      <feature>AdfCore</feature>
   
      <!-- Behavioral component super classes -->
      <feature>AdfUIChoose</feature>
      <feature>AdfUICollection</feature>
      <feature>AdfUICommand</feature>
      <feature>AdfUIDialog</feature>
      <feature>AdfUIDocument</feature>
      <feature>AdfUIEditableValue</feature>
      <feature>AdfUIForm</feature>
      <feature>AdfUIGo</feature>
      <feature>AdfUIInput</feature>
      <feature>AdfUIObject</feature>
      <feature>AdfUIOutput</feature>
      <feature>AdfUIPanel</feature>
      <feature>AdfUIPopup</feature>
      <feature>AdfUISelectBoolean</feature>
      <feature>AdfUISelectInput</feature>
      <feature>AdfUISelectOne</feature>
      <feature>AdfUISelectMany</feature>
      <feature>AdfUIShowDetail</feature>
      <feature>AdfUISubform</feature>
      <feature>AdfUIValue</feature>
   
      <!-- These are all so common that we group them with core -->
      <feature>AdfRichDocument</feature>
      <feature>AdfRichForm</feature>
      <feature>AdfRichPopup</feature>
      <feature>AdfRichSubform</feature>
      <feature>AdfRichCommandButton</feature>
      <feature>AdfRichCommandLink</feature>
   
      <!-- 
        Dialog is currently on every page for messaging.  No use
        in putting these in a separate partition.
      -->
      <feature>AdfRichPanelWindow</feature>
      <feature>AdfRichDialog</feature>
   
      <!-- af:showPopupBehavior is so small/common, belongs in core -->
      <feature>AdfShowPopupBehavior</feature>
    </partition>
   
    <partition>
      <partition-name>accordion</partition-name>
      <feature>AdfRichPanelAccordion</feature>
    </partition>
   
    <partition>
      <partition-name>border</partition-name>
      <feature>AdfRichPanelBorderLayout</feature>
    </partition>
   
    <partition>
      <partition-name>box</partition-name>
      <feature>AdfRichPanelBox</feature>
    </partition>
    
    <partition>
      <partition-name>calendar</partition-name>
      <feature>AdfUICalendar</feature>
      <feature>AdfRichCalendar</feature>
      <feature>AdfCalendarDragSource</feature>
      <feature>AdfCalendarDropTarget</feature>
    </partition>
    
    <partition>
      <partition-name>collection</partition-name>
      <feature>AdfUIDecorateCollection</feature>
      <feature>AdfRichPanelCollection</feature>
    </partition>
   
    <partition>
      <partition-name>color</partition-name>
      <feature>AdfRichChooseColor</feature>
      <feature>AdfRichInputColor</feature>
    </partition>
   
    <partition>
      <partition-name>date</partition-name>
      <feature>AdfRichChooseDate</feature>
      <feature>AdfRichInputDate</feature>
    </partition>
   
    <partition>
      <partition-name>declarativeComponent</partition-name>
      <feature>AdfUIInclude</feature>
      <feature>AdfUIDeclarativeComponent</feature>
      <feature>AdfRichDeclarativeComponent</feature>
    </partition>
   
    <partition>
      <partition-name>detail</partition-name>
      <feature>AdfRichShowDetail</feature>
    </partition>
   
    <partition>
      <partition-name>dnd</partition-name>
      <feature>AdfDragAndDrop</feature>
      <feature>AdfCollectionDragSource</feature>
      <feature>AdfStampedDropTarget</feature>
      <feature>AdfCollectionDropTarget</feature>
      <feature>AdfAttributeDragSource</feature>
      <feature>AdfAttributeDropTarget</feature>
      <feature>AdfComponentDragSource</feature>
      <feature>AdfDropTarget</feature>    
    </partition>
    
    <partition>
      <partition-name>detailitem</partition-name>
      <feature>AdfRichShowDetailItem</feature>
    </partition>
   
    <partition>
      <partition-name>file</partition-name>
      <feature>AdfRichInputFile</feature>
    </partition>
   
    <partition>
      <partition-name>form</partition-name>
      <feature>AdfRichPanelFormLayout</feature>
      <feature>AdfRichPanelLabelAndMessage</feature>
    </partition>
   
    <partition>
      <partition-name>format</partition-name>
      <feature>AdfRichOutputFormatted</feature>
    </partition>
   
    <partition>
      <partition-name>frame</partition-name>
      <feature>AdfRichInlineFrame</feature>
    </partition>
   
    <partition>
      <partition-name>header</partition-name>
      <feature>AdfRichPanelHeader</feature>
      <feature>AdfRichShowDetailHeader</feature>
    </partition>
   
    <partition>
      <partition-name>imagelink</partition-name>
      <feature>AdfRichCommandImageLink</feature>
    </partition>
   
    <partition>
      <partition-name>iedit</partition-name>
      <feature>AdfInlineEditing</feature>
    </partition>
   
    <partition>
      <partition-name>input</partition-name>
      <feature>AdfRichInputText</feature>
      <feature>AdfInsertTextBehavior</feature>
    </partition>
   
    <partition>
      <partition-name>label</partition-name>
      <feature>AdfRichOutputLabel</feature>
    </partition>
   
    <partition>
      <partition-name>list</partition-name>
      <feature>AdfRichPanelList</feature>
    </partition>
   
    <partition>
      <partition-name>lov</partition-name>
      <feature>AdfUIInputPopup</feature>
      <feature>AdfRichInputComboboxListOfValues</feature>
      <feature>AdfRichInputListOfValues</feature>
    </partition>
   
    <partition>
      <partition-name>media</partition-name>
      <feature>AdfRichMedia</feature>
    </partition>
   
    <partition>
      <partition-name>message</partition-name>
      <feature>AdfUIMessage</feature>
      <feature>AdfUIMessages</feature>
      <feature>AdfRichMessage</feature>
      <feature>AdfRichMessages</feature>
    </partition>
   
    <partition>
      <partition-name>menu</partition-name>
      <feature>AdfRichCommandMenuItem</feature>
      <feature>AdfRichGoMenuItem</feature>
      <feature>AdfRichMenuBar</feature>
      <feature>AdfRichMenu</feature>
    </partition>
   
    <partition>
      <partition-name>nav</partition-name>
      <feature>AdfUINavigationPath</feature>
      <feature>AdfUINavigationLevel</feature>
      <feature>AdfRichBreadCrumbs</feature>
      <feature>AdfRichCommandNavigationItem</feature>
      <feature>AdfRichNavigationPane</feature>
    </partition>
   
    <partition>
      <partition-name>note</partition-name>
      <feature>AdfRichNoteWindow</feature>
    </partition>
   
    <partition>
      <partition-name>poll</partition-name>
      <feature>AdfUIPoll</feature>
      <feature>AdfRichPoll</feature>
    </partition>
   
    <partition>
      <partition-name>progress</partition-name>
      <feature>AdfUIProgress</feature>
      <feature>AdfRichProgressIndicator</feature>
    </partition>
   
    <partition>
      <partition-name>print</partition-name>
      <feature>AdfShowPrintablePageBehavior</feature>
    </partition>
   
    <partition>
      <partition-name>scrollComponentIntoView</partition-name>
      <feature>AdfScrollComponentIntoViewBehavior</feature>
    </partition>
   
    <partition>
      <partition-name>query</partition-name>
      <feature>AdfUIQuery</feature>
      <feature>AdfRichQuery</feature>
      <feature>AdfRichQuickQuery</feature>
    </partition>
   
    <partition>
      <partition-name>region</partition-name>
      <feature>AdfUIRegion</feature>
      <feature>AdfRichRegion</feature>
    </partition>
   
    <partition>
      <partition-name>reset</partition-name>
      <feature>AdfUIReset</feature>
      <feature>AdfRichResetButton</feature>
    </partition>
   
    <partition>
      <partition-name>rte</partition-name>
      <feature>AdfRichTextEditor</feature>
      <feature>AdfRichTextEditorInsertBehavior</feature>
    </partition>
   
    <partition>
      <partition-name>select</partition-name>
   
      <feature>AdfRichSelectBooleanCheckbox</feature>
      <feature>AdfRichSelectBooleanRadio</feature>
      <feature>AdfRichSelectManyCheckbox</feature>
      <feature>AdfRichSelectOneRadio</feature>
    </partition>
   
    <partition>
      <partition-name>selectmanychoice</partition-name>
      <feature>AdfRichSelectManyChoice</feature>
    </partition>
   
    <partition>
      <partition-name>selectmanylistbox</partition-name>
      <feature>AdfRichSelectManyListbox</feature>
    </partition>
   
    <partition>
      <partition-name>selectonechoice</partition-name>
      <feature>AdfRichSelectOneChoice</feature>
    </partition>
   
    <partition>
      <partition-name>selectonelistbox</partition-name>
      <feature>AdfRichSelectOneListbox</feature>
    </partition>
   
    <partition>
      <partition-name>shuttle</partition-name>
      <feature>AdfUISelectOrder</feature>
      <feature>AdfRichSelectManyShuttle</feature>
      <feature>AdfRichSelectOrderShuttle</feature>
    </partition>
   
    <partition>
      <partition-name>slide</partition-name>
      <feature>AdfRichInputNumberSlider</feature>
      <feature>AdfRichInputRangeSlider</feature>
    </partition>
   
    <partition>
      <partition-name>spin</partition-name>
      <feature>AdfRichInputNumberSpinbox</feature>
    </partition>
   
    <partition>
      <partition-name>status</partition-name>
      <feature>AdfRichStatusIndicator</feature>
    </partition>
   
    <partition>
      <partition-name>stretch</partition-name>
      <feature>AdfRichDecorativeBox</feature>
      <feature>AdfRichPanelSplitter</feature>
      <feature>AdfRichPanelStretchLayout</feature>
      <feature>AdfRichPanelDashboard</feature>
      <feature>AdfPanelDashboardBehavior</feature>
      <feature>AdfDashboardDropTarget</feature>
    </partition>
   
    <partition>
      <partition-name>tabbed</partition-name>
      <feature>AdfUIShowOne</feature>
      <feature>AdfRichPanelTabbed</feature>
    </partition>
   
    <partition>
      <partition-name>table</partition-name>
      <feature>AdfUIIterator</feature>
      <feature>AdfUITable</feature>
      <feature>AdfUITable2</feature>
      <feature>AdfUIColumn</feature>
      <feature>AdfRichColumn</feature>
      <feature>AdfRichTable</feature>
    </partition>
   
    <partition>
      <partition-name>toolbar</partition-name>
      <feature>AdfRichCommandToolbarButton</feature>
      <feature>AdfRichToolbar</feature>
    </partition>
   
    <partition>
      <partition-name>toolbox</partition-name>
      <feature>AdfRichToolbox</feature>
    </partition>
   
    <partition>
      <partition-name>train</partition-name>
      <feature>AdfUIProcess</feature>
      <feature>AdfRichCommandTrainStop</feature>
      <feature>AdfRichTrainButtonBar</feature>
      <feature>AdfRichTrain</feature>
    </partition>
   
    <partition>
      <partition-name>tree</partition-name>
      <feature>AdfUITree</feature>
      <feature>AdfUITreeTable</feature>
      <feature>AdfRichTree</feature>
      <feature>AdfRichTreeTable</feature>
    </partition>
   
    <!--
      Some components which typically do have client-side representation,
      but small enough that we might as well download in a single partition
      in the event that any of these are needed.
    -->
    <partition>
      <partition-name>uncommon</partition-name>
      <feature>AdfRichGoButton</feature>
      <feature>AdfRichIcon</feature>
      <feature>AdfRichImage</feature>
      <feature>AdfRichOutputText</feature>
      <feature>AdfRichPanelGroupLayout</feature>
      <feature>AdfRichSeparator</feature>
      <feature>AdfRichSpacer</feature>
      <feature>AdfRichGoLink</feature>
    </partition>
   
    <partition>
      <partition-name>eum</partition-name>
      <feature>AdfEndUserMonitoring</feature>
    </partition>
   
    <partition>
      <partition-name>ads</partition-name>
      <feature>AdfActiveDataService</feature>
    </partition>
   
    <partition>
      <partition-name>automation</partition-name>
      <feature>AdfAutomationTest</feature>
    </partition>
   
  </partitions>