[ https://issues.apache.org/jira/browse/MYFACES-3786?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13794076#comment-13794076 ]
Dora Rajappan commented on MYFACES-3786: ---------------------------------------- MYFACES-3786-2.patch is very good. No need to change the priority of discovering the injection provider factory. Let it be container first. For all of factory artifacts to be injected by container, you can use @Named the parent factory impl and the custom implementations can use a dependency injection for parentFactory and container can inject those custom factories also. I have changed the PhaseListener and ELResolver to use new _callInjectAndPostConstruct method in FacesConfigurator in the cdirevised.patch. Validator/Convertor you have omitted for this patch. > Web Container injection support should be provided for additional lifecycle > artifacts (not just managed beans) > -------------------------------------------------------------------------------------------------------------- > > Key: MYFACES-3786 > URL: https://issues.apache.org/jira/browse/MYFACES-3786 > Project: MyFaces Core > Issue Type: Task > Components: JSR-344 > Reporter: Leonardo Uribe > Assignee: Leonardo Uribe > Fix For: 2.2.0 > > Attachments: cdiELresolverWeb.zip, cdiELResolver.zip, > cdiPartialViewContext.war, cdiPartialViewContext.zip, cdi.patch, > cdiphaselistener1.patch, cdiphaselistener2.patch, cdirevised.patch, > cdiValidatorSource.zip, cdiValidator.war, MYFACES-3786-1.patch, > MYFACES-3786-2.patch > > > This issue is all about how to inject beans into jsf artifacts. > See JSF 2.2 section 5.4.1 > The problem here is in some point we need to give the control to the > underlying environment to inject beans into the artifacts, but we don't know > much about how to properly do it, so we need to try with examples. -- This message was sent by Atlassian JIRA (v6.1#6144)