Igor, There is a way of creating your version of DefaultELHelper.
Look at the method org.apache.myfaces.extensions.validator.util.ExtValUtils#getELHelper. So this is what you have to do; 1. Create your implementation of the helper (it needs to implement org.apache.myfaces.extensions.validator.core.el.ELHelper, you can extends DefaultELHelper) 2. Create an implementation of org.apache.myfaces.extensions.validator.core.el.AbstractELHelperFactory where you return your version of the helper in the createELHelper() method. 3. Register this helperfactory in an AbstractStartupListener using something like this * ExtValContext.getContext().getFactoryFinder().getFactory(FactoryNames.EL_HELPER_FACTORY, AbstractELHelperFactory.class).setCustomELHelperFactory(new CustomHelper()); * Where CustomHelper is your AbstractELHelperFactory implementation class of step 2. If you need more help with this or another issue, you can always reach us on the mailing list. Best regards Rudy -- Rudy De Busscher http://www.c4j.be On 13 January 2012 13:06, Igor Guimaraes (Commented) (JIRA) < dev@myfaces.apache.org> wrote: > > [ > https://issues.apache.org/jira/browse/EXTVAL-140?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13185556#comment-13185556] > > Igor Guimaraes commented on EXTVAL-140: > --------------------------------------- > > Gerhard, > > The point is that I have to fix a bug for I can use the ExtVal, and I'm > trying to help solve. > > If there were an extension point for that class, or a way to override the > class DefaultELHelper, I would do it through here. > > Although not a bug of ExtVal, is preventing me to use you project of our > framework. > > This bug has been open for over a year, for a person who works with me, > Rogerio Baldini, who also was in the email copy sent to Rudy. > > We are currently using version 1.1.4-Final and 1.1.5-Final of Weld with > this bug still happening, and we can not use of ExtVal because of it. > > We corrected the problem in our framework, rather than waiting staff Weld > correct. > > I thought we could try something like that, but I see that this is not so. > > I tried the mailing list, but could not find it, and I am still searching > for... > As I will use the project for you here, I need to interact more with > mailing list. > > Thanks. > > > Error when rendering components trinidad > > ---------------------------------------- > > > > Key: EXTVAL-140 > > URL: https://issues.apache.org/jira/browse/EXTVAL-140 > > Project: MyFaces Extensions Validator > > Issue Type: Bug > > Components: Trinidad Support > > Affects Versions: 2.0.5 > > Environment: Projecto using > > - JSF 2.0.3 > > - Trinidad 2.0.0-beta-2 > > or > > - JSF 2.1.7-SNAPSHOT > > - Trinidad 2.0.2-SNAPSHOT > > Both > > Weld 1.1.4-Final > > Weld 1.1.5-Final > > Reporter: Igor Guimaraes > > Attachments: validation.zip, validation.zip > > > > > > Error processing trinidad components. > > For testing, I override the encodeBegin method, and it worked without > super.encodeBegin > > There is a solution for this error? > > Caused by: java.lang.IllegalStateException: No CreationalContext > registered for EL evaluation, it is likely that the the expression factory > has not been wrapped by the CDI BeanManager, which must be done to use the > ELResolver from CDI > > at > org.jboss.weld.el.AbstractWeldELResolver.getELCreationalContext(AbstractWeldELResolver.java:148) > > at > org.jboss.weld.el.AbstractWeldELResolver.lookup(AbstractWeldELResolver.java:123) > > at > org.jboss.weld.el.AbstractWeldELResolver.getValue(AbstractWeldELResolver.java:96) > > at > org.jboss.weld.environment.servlet.util.ForwardingELResolver.getValue(ForwardingELResolver.java:49) > > at > javax.el.CompositeELResolver.getValue(CompositeELResolver.java:54) > > at > com.sun.faces.el.DemuxCompositeELResolver._getValue(DemuxCompositeELResolver.java:176) > > at > com.sun.faces.el.DemuxCompositeELResolver.getValue(DemuxCompositeELResolver.java:203) > > at > org.apache.myfaces.extensions.validator.core.el.DefaultELHelper.getBean(DefaultELHelper.java:79) > > at > org.apache.myfaces.extensions.validator.beanval.util.BeanValidationUtils.addMetaDataToContext(BeanValidationUtils.java:119) > > at > org.apache.myfaces.extensions.validator.beanval.interceptor.ExtValBeanValidationMetaDataExtractionInterceptor.processExtValBeanValidationMetaData(ExtValBeanValidationMetaDataExtractionInterceptor.java:82) > > at > org.apache.myfaces.extensions.validator.beanval.interceptor.ExtValBeanValidationMetaDataExtractionInterceptor.afterExtracting(ExtValBeanValidationMetaDataExtractionInterceptor.java:61) > > at > org.apache.myfaces.extensions.validator.util.ExtValUtils.invokeMetaDataExtractionInterceptors(ExtValUtils.java:268) > > at > org.apache.myfaces.extensions.validator.util.ExtValUtils.access$100(ExtValUtils.java:79) > > at > org.apache.myfaces.extensions.validator.util.ExtValUtils$1.extract(ExtValUtils.java:236) > > at > org.apache.myfaces.extensions.validator.beanval.BeanValidationModuleValidationInterceptorInternals.extractPropertyDetails(BeanValidationModuleValidationInterceptorInternals.java:64) > > at > org.apache.myfaces.extensions.validator.beanval.BeanValidationModuleValidationInterceptor.initComponent(BeanValidationModuleValidationInterceptor.java:55) > > at > org.apache.myfaces.extensions.validator.core.interceptor.AbstractValidationInterceptor.beforeEncodeBegin(AbstractValidationInterceptor.java:112) > > at > org.apache.myfaces.extensions.validator.core.renderkit.ExtValRendererWrapper.encodeBegin(ExtValRendererWrapper.java:162) > > at > org.apache.myfaces.trinidad.component.UIXComponentBase.encodeBegin(UIXComponentBase.java:987) > > -- > This message is automatically generated by JIRA. > If you think it was sent incorrectly, please contact your JIRA > administrators: > https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa > For more information on JIRA, see: http://www.atlassian.com/software/jira > > >
