org.apache.myfaces.extensions.validator.core
Interface ValidationModuleAware

All Known Implementing Classes:

ExtValBeanValidationMetaDataExtractionInterceptor

public interface ValidationModuleAware

if an artifact (which supports this concept) should be used just for a/some specific module(s), the artifact has to implement this interface

Since:

x.x.3

Method Summary

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.

Method Detail

getModuleKeys

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. 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

Returns:

an array of fully qualified class names of the module keys