Oracle Fusion Middleware Tag Reference for Oracle ADF Faces
11g Release 1 (



af:selectManyChoice selectManyChoice select many choice

UIComponent class:
Component type: oracle.adf.RichSelectManyChoice

The selectManyChoice component creates a menu-style component, which allows the user to select multiple values from a dropdown list of items. The selectManyChoice component contains any number of <f:selectItem>, <f:selectItems>, or <af:selectItem> components, each of which represents an available option that the user may select.

The attributes "disabled", "immediate", "readOnly", "required", "requiredMessageDetail", "value" are not settable from the client for security reasons.

Code Example(s)

<af:selectManyChoice value="#{bean.aValue}" required="true">
  <f:selectItem itemLabel="Option1" itemValue="1"/>
  <f:selectItem itemLabel="Option1" itemValue="2"/>
  <f:selectItem itemLabel="Option1" itemValue="3"/>


Type Phases Description
javax.faces.event.ValueChangeEvent Process Validations,
Apply Request Values
The valueChange event is delivered when the value attribute is changed.
org.apache.myfaces.trinidad.event.AttributeChangeEvent Invoke Application,
Apply Request Values
Event delivered to describe an attribute change. Attribute change events are not delivered for any programmatic change to a property. They are only delivered when a renderer changes a property without the application's specific request. An example of an attribute change events might include the width of a column that supported client-side resizing.

Supported Facets

Name Description
help This facet is deprecated, helpTopicId should be used for providing help. This is a no-op for form components.


Name Type Supports EL? Description
accessKey char Yes a character used to gain quick access to the form element specified by the for, if set (or this component itself, if it is a "non-simple" form element). For accessibility reasons, this functionality is not supported in screen reader mode. If the same access key appears in multiple locations in the same page of output, the rendering user agent will cycle among the elements accessed by the similar keys.

This attribute is sometimes referred to as the "mnemonic".

Note that the accessKey is triggered by browser-specific and platform-specific modifier keys. It even has browser-specific meaning. For example, Internet Explorer 7.0 will set focus when you press Alt+<accessKey>. Firefox 2.0 on some operating systems you press Alt+Shift+<accessKey>. Firefox 2.0 on other operating systems you press Control+<accessKey>. Refer to your browser's documentation for how it treats accessKey.

attributeChangeListener javax.el.MethodExpression Only EL a method reference to an attribute change listener. Attribute change events are not delivered for any programmatic change to a property. They are only delivered when a renderer changes a property without the application's specific request. An example of an attribute change events might include the width of a column that supported client-side resizing.
autoSubmit boolean Yes an attribute which if set to TRUE on a form element, the component will automatically submit when an appropriate action takes place (a click, text change, etc.). Since autoSubmit is a partial submit, also submitted and re-rendered are any other components with partialTriggers pointing to this component.
binding Only EL an EL reference that will store the component instance on a bean. This can be used to give programmatic access to a component from a backing bean, or to move creation of the component to a backing bean.
changed boolean Yes an attribute which if set to true, the changed indicator icon will be displayed on the component. This value defaults to false.
changedDesc String Yes the text commonly used by user agents to display tooltip text on the changed indicator icon. Default value is "Changed". The behavior of the tooltip is controlled by the user agent, e.g. Firefox 2 truncates long tooltips.
clientComponent boolean Yes whether a client-side component will be generated. A component may be generated whether or not this flag is set, but if client Javascript requires the component object, this must be set to true to guarantee the component's presence. Client component objects that are generated today by default may not be present in the future; setting this flag is the only way to guarantee a component's presence, and clients cannot rely on implicit behavior. However, there is a performance cost to setting this flag, so clients should avoid turning on client components unless absolutely necessary.
contentDelivery String Yes Valid Values: immediate, lazy

whether the selectable items are delivered with the initial page. The legal values are:

  • immediate - the content is inlined into the initial page. By default, contentDelivery is immediate, which means the selectable items will be sent to the client on initial rendering.
  • lazy - the lazySelectedLabels attribute will be used in order to generate the string of items that are initially rendered in the box, see the lazySelectedLabels attribute documentation for more information. The full list of items will only be sent once the end user tries to drop the box to make a selection. More specifically we will avoid pulling the full list of items at all until the first request to show the selectable items. We will, however, call the value attribute during initial rendering.

There are several limitations when using contentDelivery is "lazy".

  • Caching - we expect the list to be cached on the server after it's first retrieved, at least at view scope level. Once the full list of items has been sent down to the client then the component will behave as if contentDelivery is immediate for as long as the page is posting back. One reason is that after postback we may need to render either the submitted value or the local value stored on the component (rather than the value coming from the model). Because of this it's not easy to keep the lazySelectedLabels synchronized with what should be rendered. Here are some examples where we may need to render the submitted value or the local component value
    • immediate button was pressed, so the submitted value is set, but the validation phase is skipped, therefore the valueChangeListener never called and the new value not pushed to model
    • another component failed validation, so the local value on the component is set and the valueChangeListener is called, but the new value not pushed to model
  • Value Attribute - cannot be request scope when contentDelivery="lazy". One purpose of contentDelivery="lazy" is to avoid pulling the full list of items. If the full list of items was never sent to the client, then we also want to avoid pulling the full list of item during postback. The full list of items might be needed during postback if valuePassThru is false (meaning we're using indexes), because we have to pull the full list in order to look up the value at the appropriate index. Meaning if the end user selected item number 8, then we need the list of possible items in order to figure out the value for item number 8. If the end user hasn't dropped down the full list of items, then we will avoid pulling the full list of items and just use the current value, but this means that the value attribute cannot be request scope.
  • Converter - won't be called in certain cases when contentDelivery="lazy" in order to avoid pulling the full list of items, see previous point for more info.
  • ScreenReader mode - contentDelivery is ignored in screen reader mode, it behaves as if it's "immediate".
contentStyle String Yes the style of the content piece of the component. You can style width by setting this attribute like this: width: 100px.
converter javax.faces.convert.Converter Yes a converter object
customizationId String Yes This attribute is deprecated. The 'id' attribute should be used when applying persistent customizations. This attribute will be removed in the next release.
disabled boolean Yes whether the element is disabled. Unlike a readonly component, a disabled component is unable to receive focus. If the component has the potential to have a scrollbar, and you want the user to be able to scroll through the component's text or values, use the 'readOnly' attribute, not the 'disabled' attribute.
editable String Yes Valid Values: inherit, always, onAccess

the editable look and feel to use for input components. 'always' indicates that the input component should always look editable. 'onAccess' indicates that the input will only look editable when accessed (hover, focus). 'inherit' indicates that we want to use the component parent's setting. None of the ancestor components define 'always' or 'onAccess', then 'always' will be used.
helpTopicId String Yes the id used to look up a topic in a helpProvider.
id String No the identifier for the component. The identifier must follow a subset of the syntax allowed in HTML:
  • Must not be a zero-length String.
  • First character must be an ASCII letter (A-Za-z) or an underscore ('_').
  • Subsequent characters must be an ASCII letter or digit (A-Za-z0-9), an underscore ('_'), or a dash ('-').
immediate boolean Yes whether the value is converted and validated immediately in the Apply Request Values phase, or is handled in the Process Validators phase, the default. By default, values are converted and validated together in the Process Validators phase. However, if you need access to the value of a component during Apply Request Values - for example, if you need to get the value from an actionListener on an immediate commandButton - then setting this to "immediate" makes that possible.
inlineStyle String Yes the CSS styles to use for this component. This is intended for basic style changes. The inlineStyle is a set of CSS styles that are applied to the root DOM element of the component. If the inlineStyle's CSS properties do not affect the DOM element you want affected, then you will have to create a skin and use the skinning keys which are meant to target particular DOM elements, like ::label or ::icon-style.
label String Yes the label of the component. If you want the label to appear above the control, use a panelFormLayout.
labelAndAccessKey String Yes an attribute that will simultaneously set both the "value" and "accessKey" attributes from a single value, using conventional ampersand ('&') notation.

For example, setting this attribute to "L&amp;abel" will set the label to "Label" and the access key to 'a'.

lazySelectedLabels String[] Yes

An array of strings that are initially shown in the box when contentDelivery=lazy, these will be concatenated by the selectManyChoice

If the array length is 1, and the string is "_ALL_", the localized string for "All" will be used, for example in English the word 'All' will appear, in French the word "Tout" will appear, etc.

Whether or not lazySelectedLabels is available the value attribute will still be called on the component.

partialTriggers String[] Yes the IDs of the components that should trigger a partial update. This component will listen on the trigger components. If one of the trigger components receives an event that will cause it to update in some way, this component will request to be updated too. Identifiers are relative to the source component (this component), and must account for NamingContainers. If your component is already inside of a naming container, you can use a single colon to start the search from the root of the page, or multiple colons to move up through the NamingContainers - "::" will pop out of the component's naming container (or itself if the component is a naming container) and begin the search from there, ":::" will pop out of two naming containers (including itself if the component is a naming container) and begin the search from there, etc.
readOnly boolean Yes whether the control is displayed as an editable field or as an output-style text control. Unlike a disabled component, a readonly component is able to receive focus.
rendered boolean Yes whether the component is rendered. When set to false, no output will be delivered for this component (the component will not in any way be rendered, and cannot be made visible on the client). If you want to change a component's rendered attribute from false to true using PPR, set the partialTrigger attribute of its parent component so the parent refreshes and in turn will render this component.
required boolean Yes whether a non-null, non-empty value must be entered. If false, validators will not be executed when the value is null or empty.
requiredMessageDetail String Yes the message to be displayed, if 'required' validation fails.


  • {0} the label that identifies the component
selectAllVisible boolean Yes whether the select-all option is visible.
Not supported on the following renderkits: org.apache.myfaces.trinidad.core
shortDesc String Yes the short description of the component. This text is commonly used by user agents to display tooltip help text, in which case the behavior for the tooltip is controlled by the user agent, e.g. Firefox 2 truncates long tooltips. For form components, the shortDesc is displayed in a note window. For components that support the helpTopicId attribute it is recommended that helpTopicId is used as it is more flexible and is more accessibility-compliant.
showRequired boolean Yes whether the associated control displays a visual indication of required user input. If a "required" attribute is also present, both the "required" attribute and the "showRequired" attribute must be false for the visual indication not to be displayed. An example of when it can be desirable to use the showRequired property is if you have a field that is initially empty and is required only if some other field on the page is touched.
simple boolean Yes a boolean value that controls whether the component provides label support; when set to "true", the component will not display the label (these may be ignored: label, labelAndAccessKey, accessKey, showRequired, help facet) and may use simpler layout primitives. One of the usecases can be when the component is used in repeatable elements like in table, for-each etc., where label is not required.
styleClass String Yes a CSS style class to use for this component. The style class can be defined in your jspx page or in a skinning CSS file, for example, or you can use one of our public style classes, like 'AFInstructionText'.
unsecure java.util.Set Yes A whitespace separated list of attributes whose values ordinarily can be set only on the server, but need to be settable on the client. Currently, this is supported only for the "disabled" attribute.
validator javax.faces.el.MethodBinding Only EL a method reference to a validator method
value Object Yes the value of the component. If the EL binding for the "value" points to a bean property with a getter but no setter, and this is an editable component, the component will be rendered in read-only mode.
valueChangeListener javax.faces.el.MethodBinding Only EL a method reference to a value change listener
valuePassThru boolean Yes whether or not the values are passed through to the client. When valuePassThru is false the value and the options' values are converted to indexes before being sent to the client. Therefore, when valuePassThru is false, there is no need to write your own converter when you are using custom Objects as your values and/or options.

If you need to know the actual values on the client-side, then you can set valuePassThru to true. This will pass the values through to the client, using your custom converter if it is available; a custom converter is needed if you are using custom objects. For drag and drop it is recommended to set valuePassThru to true for both the drag source and drop target since values are usually required on the client for drag and drop operations.

The default is false.

visible boolean Yes the visibility of the component. If it is "false", the component will be hidden on the client. Unlike "rendered", this does not affect the lifecycle on the server - the component may have its bindings executed, etc. - and the visibility of the component can be toggled on and off on the client, or toggled with PPR. When "rendered" is false, the component will not in any way be rendered, and cannot be made visible on the client. In most cases, use the "rendered" property instead of the "visible" property.
Not supported on the following renderkits: org.apache.myfaces.trinidad.core