You see the Properties window for a Standard JavaServer Faces Formatted Output component when you select the component on a page that you are editing in the Visual Designer.
This standard JavaServer Faces component has the following properties.
General
escape. Type: boolean
Selecting this checkbox causes characters like '<' that can cause problems with XML and HTML to be escaped. For example, with this checkbox selected, '<' is represented as <.
id. Type: text
The name of the Formatted Output component in the page bean and the JSP file.
Appearance
style. Type: String
Cascading Style Sheet rules (CSS level 2) to be applied to the component. This property overrides any settings in the project CSS file. For example:
position: absolute; left: 288px; top: 312px
You can enter values directly or click the ellipsis (...) button to use the Style Editor.
For a list of CSS2 style attributes, see the web page at
styleClass. Type: String
Enter a space-separated list of CSS2 style classes to be applied when the component is rendered. The style classes must be defined in the project's style sheet. If you click the ellipsis button (...), you see a list of all styles you can add to this property. For information on adding CSS classes and rules to the project's cascading style sheet, see CSS Editor.
title. Type: String
Information about the component that is readable by a screen reader and can be displayed as a tool tip.
If the component is disabled, the tool tip will not display in most browsers.
Data
converter. Type: Converter
A JavaServer Faces converter that produces the correct type of value for the value property. If the user enters the wrong type of value, such as a word instead of a number for an Integer converter, the converter sends a message that you can display in an Inline Message component.
value. Type: Object
The text that displays on the page.
Advanced
rendered. Type: boolean
If selected, the component is to be rendered and processed on any subsequent page submission. If not selected, the component doesn't appear on the page at all, not even as a hidden component.
You can bind this property to a variable that determines when the component does get rendered. For example, an airline reservation form might show a text field for frequent flyers and not show it for the general public. To bind this property, right-click the component in the Visual Designer and choose Property Bindings, and then select the All radio button to display all properties so you can bind the rendered property.