org.apache.myfaces.extensions.validator.beanval.interceptor
Class ExtValBeanValidationMetaDataExtractionInterceptor

java.lang.Object
  org.apache.myfaces.extensions.validator.beanval.interceptor.ExtValBeanValidationMetaDataExtractionInterceptor

All Implemented Interfaces:

MetaDataExtractionInterceptor, ValidationModuleAware

@InvocationOrder(value=200)
public class ExtValBeanValidationMetaDataExtractionInterceptor
extends Object
implements MetaDataExtractionInterceptor, ValidationModuleAware

extracts and adds the extval bv meta-data (e.g. validation groups) to the ExtValBeanValidationContext

Since:

x.x.3

Constructor Summary

ExtValBeanValidationMetaDataExtractionInterceptor()

Method Summary

void	afterExtracting(PropertyInformation propertyInformation) Allows to execute additional actions on the PropertyInformation data after the extraction is performed and before it is used to determine validation strategies or UIComponent adjustments.
String[]	getModuleKeys() during the registration process the information gets evaluated instead of a class array a string array is used so that it's possible to implement an artifact for different modules.

Methods inherited from class java.lang.Object

clone, equals, finalize, getClass, hashCode, notify, notifyAll, toString, wait, wait, wait

Constructor Detail

ExtValBeanValidationMetaDataExtractionInterceptor

public ExtValBeanValidationMetaDataExtractionInterceptor()

Method Detail

afterExtracting

public void afterExtracting(PropertyInformation propertyInformation)

Description copied from interface: MetaDataExtractionInterceptor

Allows to execute additional actions on the PropertyInformation data after the extraction is performed and before it is used to determine validation strategies or UIComponent adjustments.

Specified by:

afterExtracting in interface MetaDataExtractionInterceptor

Parameters:

propertyInformation - the information entry which contains information about the property

getModuleKeys

public String[] getModuleKeys()

Description copied from interface: ValidationModuleAware

during the registration process the information gets evaluated
instead of a class array a string array is used so that it's possible to implement an artifact for different modules. if an add-on restricts an artifact to specific modules, not all modules have to be used by the webapp. if a module key is unknown, the artifact won't get registered for this module. if an artifact doesn't implement this interface, it gets registered for all modules

Specified by:

getModuleKeys in interface ValidationModuleAware

Returns:

an array of fully qualified class names of the module keys