Re: Bug EXTVAL-130?

hi howard, please ensure that you are using the current snapshot from [1]. if you still have issues, please provide a link to a simple demo. (maybe you are facing an issue which affects codi but which isn't an issue of codi itself.) regards, gerhard [1]

[ANNOUNCE] MyFaces Core v2.0.16 Release

The Apache MyFaces team is pleased to announce the release of MyFaces Core 2.0.16. MyFaces Core is a JavaServer(tm) Faces 2.0 implementation as specified by JSR-314. MyFaces Core has passed Sun's JSR-314 TCK and is 100% compliant with the JSR-314 specification. MyFaces Core 2.0.16 is available

[ANNOUNCE] MyFaces Core v2.1.10 Release

The Apache MyFaces team is pleased to announce the release of MyFaces Core 2.1.10. MyFaces Core is a JavaServer(tm) Faces 2.1 implementation as specified by JSR-314. MyFaces Core has passed Sun's JSR-314 TCK and is 100% compliant with the JSR-314 specification. MyFaces Core 2.1.10 is available

Re: Bug EXTVAL-130?

hi gerald, @ veto: ClassDeactivator is just for classes which are listed in config files of cdi, jsf,... (and the specs. don't provide a possibility to disable them). in your case you just need the std. ProcessAnnotatedType#veto provided by cdi itself. @ BeanValidation#modelValidation i wrote

Re: el issue with weld (was: Bug EXTVAL-130?)

hi gerald, @ el issue with weld: that sounds like a serious weld bug. extval is just using the std. jsf-api (in this case: javax.faces.application.Application#evaluateExpressionGet). brian leathem confirmed the weld-issue - maybe jozef can provide further details. regards, gerhard

Re: el issue with weld (was: Bug EXTVAL-130?)

short addition: in this case it's actually Application#getELResolver#getValue (brian confirmed it for Application#evaluateExpressionGet which is needed by extval as well) regards, gerhard http://www.irian.at Your JSF/JavaEE powerhouse - JavaEE Consulting, Development and Courses in English and