AW: ExtVal: NullPointer during EL resolving for custom component

Hi Gerhard, a demo is available as war-file: http://www.humyo.de/10453303/TestProject.war?a=fojK9Jp2984. Just follow the links, enter a value and press the button. In org.apache.myfaces.extensions.validator.core.el.ExtValELResolver: public ValueExpression getCompositeComponentExpression()

AW: ExtVal: Rendering component with visual indication for required fields

d > > > attribute of it, it will return false, no matter what annotations > there > > are > > > placed on the property in the backing bean. (except of course when > you > > have > > > set the required attribute in the screen). > > > > > > S

AW: ExtVal: Rendering component with visual indication for required fields

Hi Gerhard, what I had already used before asking in the mailing list was: - ExtVal Core - BeanValidation (using JSR-303 annotations) - PropertyValidation (using basic code for custom cross validation annotation and provided out-of-the-box annotations such as @RequiredIf) - I did not want to use T

AW: ExtVal: Rendering component with visual indication for required fields

Hi Gerhard, hi Rudy, thank you for your quick response. I tried to proceed just like you suggested but the meta data for the bean validation annotations is not found. ExtValUtils.getTransformedMetaData() always returns an empty map. The reason seems to be that DefaultValidationStrategyFactory.cre