org.apache.myfaces.extensions.validator.core.initializer.component
Interface ComponentInitializer

All Known Implementing Classes:

AbstractHtmlCoreComponentsComponentInitializer, HtmlCoreComponentsComponentInitializer, HtmlCoreComponentsComponentInitializer, TrinidadComponentInitializer

@InvocationOrderSupport
public interface ComponentInitializer

Allows to initialize components before UIComponent.encodeBegin(javax.faces.context.FacesContext).
e.g.: you can add information for client-side validation mechanisms,... MetaDataTransformers are used to convert specific information of constraints to a generic representation. A ComponentInitializer is just aware of the generic data. E.g. a ComponentInitializer doesn't have to care if the information was provided by @Length or @Size. But a ComponentInitializer has to be aware of specific JSF component types. Typically there is one ComponentInitializer per JSF component lib.

Since:

1.x.1

Method Summary

void	configureComponent(javax.faces.context.FacesContext facesContext, javax.faces.component.UIComponent uiComponent, Map<String,Object> metaData) Initialize components with information from the meta-data.

Method Detail

configureComponent

void configureComponent(javax.faces.context.FacesContext facesContext,
                        javax.faces.component.UIComponent uiComponent,
                        Map<String,Object> metaData)

Initialize components with information from the meta-data.

Parameters:

facesContext - The JSF Context

uiComponent - The component that should be initialized

metaData - Information from the MetaDataEntry in an abstract form (independent of the concrete constraint implementations).