<af:dynamicComponent>

af:dynamicComponent dynamicComponent dynamic component

UIComponent class: oracle.adf.view.rich.component.rich.RichDynamicComponent
Component type: oracle.adf.DynamicComponent

The dynamicComponent is a component whose real type is defined by its attribute ComponentType. The values of attribue ComponentType and other attributes are provided by attribute AttributeModel.

Code Example(s)

Simple text input box with some default text and a label.

<af:form>
  <af:inputText label="Input:" 
                value="Some text"/>
</af:form>

The following is an example that dyanmicComponent is used for a form. Converters and validators are used.

<af:panelFormLayout id="pfl1">
                    <af:iterator id="i1" value="#{bindings.EmpVO1.descriptorCollection.attributes}" var="attr">
                        <af:dynamicComponent value="#{bindings[attr.containerName][attr.name].inputValue}" id="it1" label="#{attr.label}"
                                             attributeModel="#{attr.properties}">
                           <af:convertDateTime disabled="#{attr.name == 'Hiredate' ? false : true}"
                                               pattern="yyyy/MM/dd"/>
                           <af:convertNumber disabled="#{attr.name == 'Sal' ? false : true}" pattern="#,###,###" />
                           <af:validateLength disabled="#{attr.dataType.canonicalName == 'java.lang.String' ? false : true}"
                                              maximum="10" hintMaximum="maxmum length is 10"/>
                           <af:validateLongRange disabled="#{attr.name == 'Sal' ? false : true}" minimum="10000"/>
                        </af:dynamicComponent>
                    </af:iterator>
                </af:panelFormLayout>

The following is an example that dyanmicComponent is used for columns of a table inside a panelCollection.

<af:panelCollection id="pc1">
              <f:facet name="menus"/>
              <f:facet name="toolbar"/>
              <f:facet name="statusbar"/>
              <af:table value="#{bindings.EmpVO1.collectionModel}" var="row" rows="#{bindings.EmpVO1.rangeSize}"
                        emptyText="#{bindings.EmpVO1.viewable ? 'No data to display.' : 'Access Denied.'}"
                        fetchSize="#{bindings.EmpVO1.rangeSize}" rowBandingInterval="0"
                        filterModel="#{bindings.EmpVO1Query.queryDescriptor}"
                        queryListener="#{bindings.EmpVO1Query.processQuery}" filterVisible="true" varStatus="vs"
                        selectionListener="#{bindings.EmpVO1.collectionModel.makeCurrent}" rowSelection="multiple" id="t1"
                        contentDelivery="immediate">       
                <af:iterator value="#{bindings.EmpVO1.descriptorCollection.attributes}" id="itr1" var="column">
                  <af:column headerText="#{column.label}" id="dcc1"  filterable="true" sortable="true" sortProperty="#{column.name}">
                    <af:dynamicComponent value="#{row.bindings[column.name].inputValue}" attributeModel="#{column.properties}" id="dc1">
                      <af:validateLongRange disabled="#{column.name == 'Sal' ? false : true}" minimum="10000"/>
                    </af:dynamicComponent>
                  </af:column>          
                </af:iterator>
              </af:table>
            </af:panelCollection>

Events

Type	Phases	Description
oracle.adf.view.rich.event.LaunchPopupEvent	Invoke Application	LaunchPopupEvent is delivered when a user's action on an input component results in the launching of a popup dialog. For example, clicking the search icon on the inputListOfValues component or the "Search..." entry at the bottom of the drop down panel of the inputComboboxListOfValues component or tabbing-out of either of the above components with a non null value set, and autoSumit set to "true" will result in the queueing and broadcasting of LaunchPopupEvent on the input*ListOfValues component.
oracle.adf.view.rich.event.ReturnPopupDataEvent	Invoke Application,Apply Request Values	Deprecated, will be removed in the future release
oracle.adf.view.rich.event.ReturnPopupEvent	Invoke Application	The ReturnPopupEvent is delivered after the the popup/dialog data is packaged and returned.
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 event might include the width of a column that supported client-side resizing.

Type

Phases

Description

oracle.adf.view.rich.event.LaunchPopupEvent

Invoke Application

LaunchPopupEvent is delivered when a user's action on an input component results in the launching of a popup dialog. For example, clicking the search icon on the inputListOfValues component or the "Search..." entry at the bottom of the drop down panel of the inputComboboxListOfValues component or tabbing-out of either of the above components with a non null value set, and autoSumit set to "true" will result in the queueing and broadcasting of LaunchPopupEvent on the input*ListOfValues component.

oracle.adf.view.rich.event.ReturnPopupDataEvent

Invoke Application,Apply Request Values

Deprecated, will be removed in the future release

oracle.adf.view.rich.event.ReturnPopupEvent

Invoke Application

The ReturnPopupEvent is delivered after the the popup/dialog data is packaged and returned.

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 event might include the width of a column that supported client-side resizing.

Supported Facets

Name	Description
context	Location for contextual information. A contextInfo component is expected. This facet is ignored when 'mode' is 'compact'.
customActions	Allows user to specify custom entries in the choice list (drop down panel). It can be one commandLink or multiple commandLinks that are wrapped in a group component. It is the developer's responsibility to wire up the action for the custom commandLink to, say, a popup dialog.
help	This facet is deprecated, helpTopicId should be used for providing help. This is a no-op for form components.
resultsTable	Table component to be used in the Search and Select dialog. Supports sub classes of RichTable. Table columns should not be configured as they are auto generated by LOV. Only one of 'searchContent' or 'resultsTable' facet can be configured.
searchContent	Content in the Search and Select popup dialog.

Name

Description

context

Location for contextual information. A contextInfo component is expected. This facet is ignored when 'mode' is 'compact'.

customActions

Allows user to specify custom entries in the choice list (drop down panel). It can be one commandLink or multiple commandLinks that are wrapped in a group component. It is the developer's responsibility to wire up the action for the custom commandLink to, say, a popup dialog.

help

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

resultsTable

Table component to be used in the Search and Select dialog. Supports sub classes of RichTable. Table columns should not be configured as they are auto generated by LOV. Only one of 'searchContent' or 'resultsTable' facet can be configured.

searchContent

Content in the Search and Select popup dialog.

Attributes

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). 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 will set focus when you press Alt+<accessKey>. Firefox sets focus on some operating systems when you press Alt+Shift+<accessKey>. Firefox on other operating systems sets focus when you press Control+<accessKey>. Refer to your browser's documentation for how it treats access keys.
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.
attributeModel	oracle.adf.view.rich.model.Descriptor	Yes	Dynamic component attributeMap is a map of String and Object, or name and value of the component's attributes.
autoComplete	String	Yes	Valid Values: on, off whether previous values of text fields in the form should be remembered and offered for auto completion.
autoSubmit	boolean	Yes	Default Value: false 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.
autoTab	boolean	Yes	Default Value: false an attribute which if set to TRUE, tells the component to automatically tab to the next focusable, when the maxlength for the current component has been reached.
binding	oracle.adf.view.rich.component.rich.RichDynamicComponent	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	Default Value: false an attribute which if set to true, the changed indicator icon will be displayed on the component.
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.
chooseId	String	Yes	the id of the chooseDate component which can be used to pick the Date value for this inputDate. If set, attributes maxValue, minValue, disabledDays, disabledDaysOfWeek and disabledMonths are ignored. 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.
clientComponent	boolean	Yes	Default Value: false 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. For the components outputText and outputFormatted, setting the clientComponent to true will render id attribute for the html DOM. This ID attribute can alternatively be generated by setting oracle.adf.view.rich.SUPPRESS_IDS to "auto" in web.xml.
columns	int	Yes	the size of the text control specified by the number of characters shown. The default value depends on the browser.
contentDelivery	String	Yes	Valid Values: immediate, lazy Default Value: immediate 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. Be aware that because of browser CSS precedence rules, CSS rendered on a DOM element takes precedence over external stylesheets like the skin file. Therefore skins will not be able to override what you set on this attribute.
converter	javax.faces.convert.Converter	Yes	a converter object
createPopupId	String	Yes	the id of the user-defined popup component relative to this component (accounting for NamingContainers). If this attribute is supplied, an af:toolbar with a button will be created internally, which will be displayed as create icon in the Search and Select dialog. Clicking the button launches the user-defined popup component. If the developer has added a dialog within the popup, then the decision to refresh the table is made by the component intelligently(table will be refreshed on pressing Ok button in the dialog). If the developer has not added a dialog to the popup, then the table will be refreshed always. Identifiers are relative to the component, and must account for NamingContainers. You can use a single colon to start the search from the root, or multiple colons to move up through the NamingContainers - "::" will pop out of the component's naming container and begin the search from there, ":::" will pop out of two naming containers and begin the search from there, etc.
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.
dimensionsFrom	String	Yes	Valid Values: auto, content, parent Default Value: content determines how the component will handle geometry management (when the simple attribute is true). This specifies where the dimensions of the inputText come from: auto - either "content" or "parent", depending on the container the inputText is inside; if the inputText is being stretched by its ancestor then "parent" will be used, otherwise "content" will be used. content - the inputText will get its dimensions from the component content. parent - the inputText will get its dimensions from the inlineStyle and if not provided from there then from its parent or if not provided from the parent then from the skin.
disabled	boolean	Yes	Default Value: false 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.
disabledDays	org.apache.myfaces.trinidad.model.DateListProvider	Yes	a binding to an implementation of the org.apache.myfaces.trinidad.model.DateListProvider interface. The getDateList method should generate a List of individual java.util.Date objects which will be rendered as disabled. The Dates must be in the context of the given base Calendar. Note: this binding requires periodic roundtrips. If you just want to disable certain weekdays (e.g. Saturday and Sunday), use the disabledDaysOfWeek attribute!
disabledDaysOfWeek	java.util.Set	Yes	a whitespace delimited list of weekdays that should be rendered as disabled in every week. The list should consist of one or more of the following abbreviations: sun, mon, tue, wed, thu, fri, sat. By default all days are enabled.
disabledMonths	java.util.Set	Yes	a whitespace delimited list of months that should be rendered as disabled in every year. The list should consist of one or more of the following abbreviations: jan, feb, mar, apr, may, jun, jul, aug, sep, oct, nov, dec. By default all months are enabled.
editMode	String	Yes	Valid Values: input, select Default Value: input the mode that controls how the user specifies a value. This attribute is only applicable when the 'readOnly' attribute is set to false. input: this mode allows the user to type in a value as well as browse and select from a list of available values. select: this mode allows the user only to browse and select from a list of available values.
editable	String	Yes	Valid Values: inherit, always, onAccess Default Value: inherit 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.
group	String	Yes	the "group" the radio buttons will be placed in. Radio buttons in the same group will have mutually exclusive selection, regardless of their physical placement on the page. See selectOneRadio - it groups the radios automatically. The reason you would use selectBooleanRadio instead of selectOneRadio is that you have more control over the placement of each radio. Using a selectBooleanRadio alone is uncommon; in any case, you must set the group attribute.
helpTopicId	String	Yes	the id used to look up a topic in a helpProvider.
id	String	No	the identifier for the component. Every component may be named by a component identifier that must conform to the following rules: They must start with a letter (as defined by the Character.isLetter() method) or underscore ( _ ). Subsequent characters must be letters (as defined by the Character.isLetter() method), digits as defined by the Character.isDigit() method, dashes ( - ), or underscores ( _ ). To minimize the size of responses generated by JavaServer Faces, it is recommended that component identifiers be as short as possible. If a component has been given an identifier, it must be unique in the namespace of the closest ancestor to that component that is a NamingContainer (if any).
immediate	boolean	Yes	Default Value: false 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. Be aware that because of browser CSS precedence rules, CSS rendered on a DOM element takes precedence over external stylesheets like the skin file. Therefore skins will not be able to override what you set on this attribute. 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.
items	java.util.List	Yes	a list of data for the live content inside the drop down panel of the inputComboboxListOfValues component.
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 "label" and "accessKey" attributes from a single value, using conventional ampersand notation. For example, setting this attribute to "T&ext" will set the label to "Text" and the access key to 'e'.
labelStyle	String	Yes	the CSS styles to use for the label of this component. The labelStyle is a set of CSS styles that are applied to the label DOM element of the component. This allows a label to be styled without requiring a new skin definition.
launchPopupListener	javax.el.MethodExpression	Only EL	a method reference to a LaunchPopupListener (called in response to a LaunchPopupEvent).
layout	String	Yes	Valid Values: horizontal, vertical Default Value: vertical whether the control displays the buttons horizontally or vertically. The default is "vertical".
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.
maxValue	java.util.Date	Yes	the maximum value allowed for the Date value. When set to a fixed value on a tag, this will be parsed as an ISO 8601 date. ISO 8601 dates are of the form "yyyy-MM-dd" (for example: 2002-02-15) and the created Date object will be in the application's timezone, with the time components (hours, minutes, seconds, milliseconds) maximized. All other uses require java.util.Date objects.When binding to Date objects, it is advised to create the Date object with maximum value for any date-time components that aren't displayed (usually hours, minutes, seconds, milliseconds) to allow the largest range of values to be accepted.
maximumLength	int	Yes	the maximum number of characters per line that can be entered into the text control.
minValue	java.util.Date	Yes	the minimum value allowed for the Date value. When set to a fixed value on a tag, this will be parsed as an ISO 8601 date. ISO 8601 dates are of the form "yyyy-MM-dd" (for example: 2002-02-15) and the created Date object will be in the application's timezone, with the time components (hours, minutes, seconds, milliseconds) zeroed-out. All other uses require java.util.Date objects.When binding to Date objects, it is advised to create the Date object with zeroed-out values for any date-time components that aren't displayed (usually hours, minutes, seconds, milliseconds) to allow the largest range of values to be accepted.
mode	String	Yes	Valid Values: default, compact Default Value: default the mode of the component. When set to "compact", the selected value box is hidden, the drop down icon changes to smaller one, and the component can never be disabled. If compact and disabled are both true, the component is hidden.
model	oracle.adf.view.rich.model.ListOfValuesModel	Yes	A ListOfValuesModel object that represents the model for the LOV component. The ListOfValuesModel currently provides methods for use within the LOV component and in addition, to retrieve a QueryModel and TableModel in order to display a table and/or a query component (which are then used to search and select a value for the LOV component). For details, please refer to the Javadocs for oracle.adf.view.rich.model.ListOfValuesModel
nullValueMeans	String	Yes	Valid Values: null, mixed Default Value: null an attribute used to indicate how the null value should be treated by the renderer.
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.
placeholder	String	Yes	Text to be displayed in the input component when a value is not present.
popupTitle	String	Yes	the title of the Search and Select popup dialog.
protectionKey	String	Yes	protection key for this component
readOnly	boolean	Yes	Default Value: false 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.
recentItems	java.util.List	Yes	a customized list of options that is part of a "Favorites" list. The recent items list is displayed before the list of items and can be a list of the most recently used (MRU) items in the dataset.
rendered	boolean	Yes	Default Value: true 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	Default Value: false 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. Parameters: {0} the label that identifies the component
resultsTableColumnStretching	String	Yes	Valid Values: last, none, blank Default Value: last Indicates what kind of stretching you want applied to the columns of results table in search and select dialog.The default value is last which stretches the last column to fill up any unused space.If you want to have an empty blank column be automatically inserted and have it stretch (so the row background colors will span the entire width of the table), use the "blank" option. Note that row headers and frozen columns will not be stretched because doing so could easily leave the user unable to access the scrollable data body of the table. Not supported on the following renderkits: org.apache.myfaces.trinidad.core
returnPopupDataListener	javax.el.MethodExpression	Only EL	A method reference to a ReturnPopupDataListener (called in response to a ReturnPopupDataEvent).
returnPopupDataValue	Object	Yes	an attribute for returning the set value in custom popup by the user in listOfValues component.
returnPopupListener	javax.el.MethodExpression	Only EL	a method reference to a ReturnPopupListener (called in response to a ReturnPopupEvent).
rows	int	Yes	Default Value: 1 the height of the text control specified by the number of characters shown. The default value is 1, which generates a one-row input field. The number of rows is estimated based on the default font size of the browser.
searchDesc	String	Yes	used to override the search description. The search description appears in the tooltip when user does a mouseover on the Search icon. By default this value will be 'Search: ' followed by the label name. If a searchDesc is specified, that value is used instead.
searchDialog	String	Yes	Valid Values: default, none Default Value: default this attribute can be used to selectively render the search link in InputComboboxListOfValues dropdown and to suppress the default "Search and Select" dialog functionality. Note: Even when this attribute is set to 'none', launchPopup event will still be queued to support auto-complete of partial values on tab out
secret	boolean	Yes	Default Value: false a boolean value that only applies to single line text controls. When set to "true", it hides the actual value of the text from the user, and will prevent the actual "value" from being shown to the user. When the user manually enters a value, each character will appear as an . After the value is posted to the server, the value (if not null) will always appear (and be sent to the client) as "*****", or whichever value is defined in UIConstants.SECRET_FIELD_DEFAULT_VALUE. If secret is set to true, be sure to not use a converter or validator tag with this inputText which would expose the value the user entered via its messages.
selectAllVisible	boolean	Yes	Default Value: true 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. The shortDesc text may be used in two different ways, depending on the component. For components with images, the shortDesc is often used to render an HTML alt attribute for the image. Please see the accessibility guidelines section for correct alt text usage of the shortDesc attribute. shortDesc is also commonly used to render an HTML title attribute, which is used by user agents to display tooltip help text. In this 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 and are not using the shortDesc as image alt text, it is recommended that helpTopicId is used instead of shortDesc as it is more flexible and provides more accessible descriptive text than the use of the title attribute.
showRequired	boolean	Yes	Default Value: false 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	Default Value: false 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.
size	int	Yes	Default Value: 4 the number of items that should be visible in the list. The renderer may constrain the maximum and minimum number of items shown.
spellCheck	String	Yes	Valid Values: on, off, default Default Value: default determines if the inputText will highlight misspelled words. on - spellcheck attribute will be rendered with a value of 'true' off - spellcheck attribute will be rendered with a value of 'false' default - spellcheck attribute will not be rendered (browser default behavior)
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'.
text	String	Yes	the text of the checkbox.
textAndAccessKey	String	Yes	an attribute that will simultaneously set both the "text" and "accessKey" attributes from a single value, using conventional ampersand notation. For example, setting this attribute to "T&ext" will set the text to "Text" and the access key to 'e'.
timeZoneList	java.util.List	Yes	A list of timezones this inputDate exposes. If set, and the inputDate is set up to display timezones (by modifying the dateTimeConverter pattern), the timezone dropdown selector will contain this list in the order given.
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. Note that when you are able to set a property on the client, you will be allowed to by using the the .setProperty('attribute', newValue) method, but not the .setXXXAttribute(newValue) method. For example, if you have unsecure="disabled", then on the client you can use the method .setProperty('disabled', false), while the method .setDisabled(false) will not work and will provide a javascript error that setDisabled is not a function.
unselectedLabel	String	Yes	the label for an additional item that indicates no selection has been made. When the user selects this item, "required" validation will not pass, or a null value will be set if the component is not "required".
usage	String	Yes	Valid Values: auto, text, search Default Value: auto The usage attribute will set the type of the input to allow for different html types (such as search). Currently only auto, text and search are valid. auto is the default. Currently, auto will default to text but may in the future conditionally default to some other type.
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	Default Value: false 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.
var	String	No	the name of the EL variable used to reference each row inside the drop down panel. Once this component has completed rendering, this variable is removed (or reverted back to it's previous value).
visible	boolean	Yes	Default Value: true 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
wrap	String	Yes	Valid Values: soft, hard, off the type of text wrapping to be used in a multi-row text control. This attribute is ignored for single row inputText. By default (or "soft"), multirow text wraps visually, but does not include carriage returns in the submitted value. Setting this to "off" will disable wrapping; the multirow text will scroll horizontally. Setting it to "hard" specifies that the value of the text should include any carriage returns needed to wrap the lines.

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). 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 will set focus when you press Alt+<accessKey>. Firefox sets focus on some operating systems when you press Alt+Shift+<accessKey>. Firefox on other operating systems sets focus when you press Control+<accessKey>. Refer to your browser's documentation for how it treats access keys.

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.

attributeModel

oracle.adf.view.rich.model.Descriptor

Yes

Dynamic component attributeMap is a map of String and Object, or name and value of the component's attributes.

autoComplete

String

Yes

Valid Values: on, off

whether previous values of text fields in the form should be remembered and offered for auto completion.

autoSubmit

boolean

Yes

Default Value: false

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.

autoTab

boolean

Yes

Default Value: false

an attribute which if set to TRUE, tells the component to automatically tab to the next focusable, when the maxlength for the current component has been reached.

binding

oracle.adf.view.rich.component.rich.RichDynamicComponent

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

Default Value: false

an attribute which if set to true, the changed indicator icon will be displayed on the component.

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.

chooseId

String

Yes

the id of the chooseDate component which can be used to pick the Date value for this inputDate. If set, attributes maxValue, minValue, disabledDays, disabledDaysOfWeek and disabledMonths are ignored. 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.

clientComponent

boolean

Yes

Default Value: false

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.
For the components outputText and outputFormatted, setting the clientComponent to true will render id attribute for the html DOM. This ID attribute can alternatively be generated by setting oracle.adf.view.rich.SUPPRESS_IDS to "auto" in web.xml.

columns

int

Yes

the size of the text control specified by the number of characters shown. The default value depends on the browser.

contentDelivery

String

Yes

Valid Values: immediate, lazy
Default Value: immediate

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. Be aware that because of browser CSS precedence rules, CSS rendered on a DOM element takes precedence over external stylesheets like the skin file. Therefore skins will not be able to override what you set on this attribute.

converter

javax.faces.convert.Converter

Yes

a converter object

createPopupId

String

Yes

the id of the user-defined popup component relative to this component (accounting for NamingContainers). If this attribute is supplied, an af:toolbar with a button will be created internally, which will be displayed as create icon in the Search and Select dialog. Clicking the button launches the user-defined popup component.
If the developer has added a dialog within the popup, then the decision to refresh the table is made by the component intelligently(table will be refreshed on pressing Ok button in the dialog). If the developer has not added a dialog to the popup, then the table will be refreshed always.
Identifiers are relative to the component, and must account for NamingContainers. You can use a single colon to start the search from the root, or multiple colons to move up through the NamingContainers - "::" will pop out of the component's naming container and begin the search from there, ":::" will pop out of two naming containers and begin the search from there, etc.

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.

dimensionsFrom

String

Yes

Valid Values: auto, content, parent
Default Value: content

determines how the component will handle geometry management (when the simple attribute is true). This specifies where the dimensions of the inputText come from:

auto - either "content" or "parent", depending on the container the inputText is inside; if the inputText is being stretched by its ancestor then "parent" will be used, otherwise "content" will be used.
content - the inputText will get its dimensions from the component content.
parent - the inputText will get its dimensions from the inlineStyle and if not provided from there then from its parent or if not provided from the parent then from the skin.

disabled

boolean

Yes

Default Value: false

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.

disabledDays

org.apache.myfaces.trinidad.model.DateListProvider

Yes

a binding to an implementation of the org.apache.myfaces.trinidad.model.DateListProvider interface. The getDateList method should generate a List of individual java.util.Date objects which will be rendered as disabled. The Dates must be in the context of the given base Calendar. Note: this binding requires periodic roundtrips. If you just want to disable certain weekdays (e.g. Saturday and Sunday), use the disabledDaysOfWeek attribute!

disabledDaysOfWeek

java.util.Set

Yes

a whitespace delimited list of weekdays that should be rendered as disabled in every week. The list should consist of one or more of the following abbreviations: sun, mon, tue, wed, thu, fri, sat. By default all days are enabled.

disabledMonths

java.util.Set

Yes

a whitespace delimited list of months that should be rendered as disabled in every year. The list should consist of one or more of the following abbreviations: jan, feb, mar, apr, may, jun, jul, aug, sep, oct, nov, dec. By default all months are enabled.

editMode

String

Yes

Valid Values: input, select
Default Value: input

the mode that controls how the user specifies a value. This attribute is only applicable when the 'readOnly' attribute is set to false.

input: this mode allows the user to type in a value as well as browse and select from a list of available values.
select: this mode allows the user only to browse and select from a list of available values.

editable

String

Yes

Valid Values: inherit, always, onAccess
Default Value: inherit

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.

group

String

Yes

the "group" the radio buttons will be placed in. Radio buttons in the same group will have mutually exclusive selection, regardless of their physical placement on the page. See selectOneRadio - it groups the radios automatically. The reason you would use selectBooleanRadio instead of selectOneRadio is that you have more control over the placement of each radio. Using a selectBooleanRadio alone is uncommon; in any case, you must set the group attribute.

helpTopicId

String

Yes

the id used to look up a topic in a helpProvider.

String

the identifier for the component. Every component may be named by a component identifier that must conform to the following rules:

They must start with a letter (as defined by the Character.isLetter() method) or underscore ( _ ).
Subsequent characters must be letters (as defined by the Character.isLetter() method), digits as defined by the Character.isDigit() method, dashes ( - ), or underscores ( _ ). To minimize the size of responses generated by JavaServer Faces, it is recommended that component identifiers be as short as possible. If a component has been given an identifier, it must be unique in the namespace of the closest ancestor to that component that is a NamingContainer (if any).

immediate

boolean

Yes

Default Value: false

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. Be aware that because of browser CSS precedence rules, CSS rendered on a DOM element takes precedence over external stylesheets like the skin file. Therefore skins will not be able to override what you set on this attribute. 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.

items

java.util.List

Yes

a list of data for the live content inside the drop down panel of the inputComboboxListOfValues component.

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 "label" and "accessKey" attributes from a single value, using conventional ampersand notation. For example, setting this attribute to "T&ext" will set the label to "Text" and the access key to 'e'.

labelStyle

String

Yes

the CSS styles to use for the label of this component. The labelStyle is a set of CSS styles that are applied to the label DOM element of the component. This allows a label to be styled without requiring a new skin definition.

launchPopupListener

javax.el.MethodExpression

Only EL

a method reference to a LaunchPopupListener (called in response to a LaunchPopupEvent).

layout

String

Yes

Valid Values: horizontal, vertical
Default Value: vertical

whether the control displays the buttons horizontally or vertically. The default is "vertical".

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.

maxValue

java.util.Date

Yes

the maximum value allowed for the Date value. When set to a fixed value on a tag, this will be parsed as an ISO 8601 date. ISO 8601 dates are of the form "yyyy-MM-dd" (for example: 2002-02-15) and the created Date object will be in the application's timezone, with the time components (hours, minutes, seconds, milliseconds) maximized. All other uses require java.util.Date objects.When binding to Date objects, it is advised to create the Date object with maximum value for any date-time components that aren't displayed (usually hours, minutes, seconds, milliseconds) to allow the largest range of values to be accepted.

maximumLength

int

Yes

the maximum number of characters per line that can be entered into the text control.

minValue

java.util.Date

Yes

the minimum value allowed for the Date value. When set to a fixed value on a tag, this will be parsed as an ISO 8601 date. ISO 8601 dates are of the form "yyyy-MM-dd" (for example: 2002-02-15) and the created Date object will be in the application's timezone, with the time components (hours, minutes, seconds, milliseconds) zeroed-out. All other uses require java.util.Date objects.When binding to Date objects, it is advised to create the Date object with zeroed-out values for any date-time components that aren't displayed (usually hours, minutes, seconds, milliseconds) to allow the largest range of values to be accepted.

mode

String

Yes

Valid Values: default, compact
Default Value: default

the mode of the component. When set to "compact", the selected value box is hidden, the drop down icon changes to smaller one, and the component can never be disabled. If compact and disabled are both true, the component is hidden.

model

oracle.adf.view.rich.model.ListOfValuesModel

Yes

A ListOfValuesModel object that represents the model for the LOV component. The ListOfValuesModel currently provides methods for use within the LOV component and in addition, to retrieve a QueryModel and TableModel in order to display a table and/or a query component (which are then used to search and select a value for the LOV component). For details, please refer to the Javadocs for oracle.adf.view.rich.model.ListOfValuesModel

nullValueMeans

String

Yes

Valid Values: null, mixed
Default Value: null

an attribute used to indicate how the null value should be treated by the renderer.

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.

placeholder

String

Yes

Text to be displayed in the input component when a value is not present.

popupTitle

String

Yes

the title of the Search and Select popup dialog.

protectionKey

String

Yes

protection key for this component

readOnly

boolean

Yes

Default Value: false

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.

recentItems

java.util.List

Yes

a customized list of options that is part of a "Favorites" list. The recent items list is displayed before the list of items and can be a list of the most recently used (MRU) items in the dataset.

rendered

boolean

Yes

Default Value: true

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

Default Value: false

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.

Parameters:

{0} the label that identifies the component

resultsTableColumnStretching

String

Yes

Valid Values: last, none, blank
Default Value: last

Indicates what kind of stretching you want applied to the columns of results table in search and select dialog.The default value is last which stretches the last column to fill up any unused space.If you want to have an empty blank column be automatically inserted and have it stretch (so the row background colors will span the entire width of the table), use the "blank" option. Note that row headers and frozen columns will not be stretched because doing so could easily leave the user unable to access the scrollable data body of the table.
Not supported on the following renderkits: org.apache.myfaces.trinidad.core

returnPopupDataListener

javax.el.MethodExpression

Only EL

A method reference to a ReturnPopupDataListener (called in response to a ReturnPopupDataEvent).

returnPopupDataValue

Object

Yes

an attribute for returning the set value in custom popup by the user in listOfValues component.

returnPopupListener

javax.el.MethodExpression

Only EL

a method reference to a ReturnPopupListener (called in response to a ReturnPopupEvent).

rows

int

Yes

Default Value: 1

the height of the text control specified by the number of characters shown. The default value is 1, which generates a one-row input field. The number of rows is estimated based on the default font size of the browser.

searchDesc

String

Yes

used to override the search description. The search description appears in the tooltip when user does a mouseover on the Search icon. By default this value will be 'Search: ' followed by the label name. If a searchDesc is specified, that value is used instead.

searchDialog

String

Yes

Valid Values: default, none
Default Value: default

this attribute can be used to selectively render the search link in InputComboboxListOfValues dropdown and to suppress the default "Search and Select" dialog functionality. Note: Even when this attribute is set to 'none', launchPopup event will still be queued to support auto-complete of partial values on tab out

secret

boolean

Yes

Default Value: false

a boolean value that only applies to single line text controls. When set to "true", it hides the actual value of the text from the user, and will prevent the actual "value" from being shown to the user. When the user manually enters a value, each character will appear as an *. After the value is posted to the server, the value (if not null) will always appear (and be sent to the client) as "******", or whichever value is defined in UIConstants.SECRET_FIELD_DEFAULT_VALUE. If secret is set to true, be sure to not use a converter or validator tag with this inputText which would expose the value the user entered via its messages.

selectAllVisible

boolean

Yes

Default Value: true

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. The shortDesc text may be used in two different ways, depending on the component.

For components with images, the shortDesc is often used to render an HTML alt attribute for the image. Please see the accessibility guidelines section for correct alt text usage of the shortDesc attribute.

shortDesc is also commonly used to render an HTML title attribute, which is used by user agents to display tooltip help text. In this 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 and are not using the shortDesc as image alt text, it is recommended that helpTopicId is used instead of shortDesc as it is more flexible and provides more accessible descriptive text than the use of the title attribute.

showRequired

boolean

Yes

Default Value: false

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

Default Value: false

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.

size

int

Yes

Default Value: 4

the number of items that should be visible in the list. The renderer may constrain the maximum and minimum number of items shown.

spellCheck

String

Yes

Valid Values: on, off, default
Default Value: default

determines if the inputText will highlight misspelled words.

on - spellcheck attribute will be rendered with a value of 'true'
off - spellcheck attribute will be rendered with a value of 'false'
default - spellcheck attribute will not be rendered (browser default behavior)

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'.

text

String

Yes

the text of the checkbox.

textAndAccessKey

String

Yes

an attribute that will simultaneously set both the "text" and "accessKey" attributes from a single value, using conventional ampersand notation. For example, setting this attribute to "T&ext" will set the text to "Text" and the access key to 'e'.

timeZoneList

java.util.List

Yes

A list of timezones this inputDate exposes. If set, and the inputDate is set up to display timezones (by modifying the dateTimeConverter pattern), the timezone dropdown selector will contain this list in the order given.

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. Note that when you are able to set a property on the client, you will be allowed to by using the the .setProperty('attribute', newValue) method, but not the .setXXXAttribute(newValue) method. For example, if you have unsecure="disabled", then on the client you can use the method .setProperty('disabled', false), while the method .setDisabled(false) will not work and will provide a javascript error that setDisabled is not a function.

unselectedLabel

String

Yes

the label for an additional item that indicates no selection has been made. When the user selects this item, "required" validation will not pass, or a null value will be set if the component is not "required".

usage

String

Yes

Valid Values: auto, text, search
Default Value: auto

The usage attribute will set the type of the input to allow for different html types (such as search). Currently only auto, text and search are valid. auto is the default. Currently, auto will default to text but may in the future conditionally default to some other type.

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

Default Value: false

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.

var

String

the name of the EL variable used to reference each row inside the drop down panel. Once this component has completed rendering, this variable is removed (or reverted back to it's previous value).

visible

boolean

Yes

Default Value: true

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

wrap

String

Yes

Valid Values: soft, hard, off

the type of text wrapping to be used in a multi-row text control. This attribute is ignored for single row inputText. By default (or "soft"), multirow text wraps visually, but does not include carriage returns in the submitted value. Setting this to "off" will disable wrapping; the multirow text will scroll horizontally. Setting it to "hard" specifies that the value of the text should include any carriage returns needed to wrap the lines.