Facelets is a JSF-centric view technology. For conditional display of elements, the rendered= attribute works well. {      class="#{class}" JSF provides special tags to create common layout for a web application called facelets tags. return value == null ? jsf - Conditionally including a Facelet file via - i have 2 facelets files (index.xhtml , report.xhtml). JSF EL â Referring object properties using value expressions To access the managed bean properties, elements in a collection or implicit objects we use . }. { Such approach doesn't work with the validator attribute, whereas it works with converter attribute. } To workaround the problem you should prevent null to "" conversion in the EL. return new Object() Attributes: Name: Required: Request-time: Type: Description: binding: false: false: javax.el.ValueExpression (must evaluate to javax.faces.component.UIComponent) Value binding expression to a backing bean property bound to the component instance for the UIComponent created by this custom action.  Output will contain all mentioned In the Core Java Server Faces book I got to know that this feature was meant for use in JavaScript code inside comments. value - a data binding; Right click on the project 4. The reason is in the EL! Click on Validate        Attributes used in The first version that you will probably think of is something like  A Facelets application may consist of compositions defined in different Facelets pages and run as an application.    JSF provides a special set of tags that gives the flexibility to manage common tags/parts in one place for more than one application. style - an optional element inline style; Again, we suffer from ugly JSF implementation of UOutput component. JSF/Facelets, conditional attributes.