UIComponent class: org.apache.myfaces.trinidad.component.core.CoreForm
Component type: org.apache.myfaces.trinidad.CoreForm
<tr:form usesUpload="true"> <tr:inputFile columns="10"/> </tr:form>
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.|
|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.|
whether previous values of text fields in the form should be remembered and offered for auto completion.
||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.|
|defaultCommand||String||Yes||The id attribute of the command button whose action would be invoked by default for form submit on hitting enter on any of the input fields of the form.|
|id||String||No||the identifier for the component. The identifier
must follow a subset of the syntax allowed in HTML:
|inlineStyle||String||Yes||the CSS styles to use for this component.|
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.
Separate multiple triggers with a space. e.g., partialTriggers="cmp1 cmp2"
Identifiers must account for NamingContainers. You can use a single colon to start the search from the root, or use multiple colons to move up through the NamingContainer. For example, "::" will pop out of this component's naming container (it pops out of itself if it is a naming container), ":::" will pop out of two naming containers, etc. The search for the partialTrigger begins from there. e.g., partialTriggers=":::commandButton1" the search begins for the component with id = commandButton1 after popping out of two naming containers relative to this component. To go into naming containers, you separate the naming containers with ':', e.g.,partialTriggers= "nc1:nc2:nc3:componentId".
|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).|
|shortDesc||String||Yes||The short description of the component. This text is commonly used by user agents to display tooltip help text.|
|styleClass||String||Yes||a CSS style class to use for this component.|
|targetFrame||String||Yes||the target frame for the form|
whether the form supports file upload.
Not supported on the following agents: pda