[ https://issues.apache.org/jira/browse/MYFACES-3786?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13795246#comment-13795246 ]
Dora Rajappan commented on MYFACES-3786: ---------------------------------------- Thank @Gerald for explaining the rule when cdi context management is bypassed. Leonardo suggested scope to go in signature in #1 for supporting scope for artifacts. But that's not required these jsf aritifcats(Excluding Validator/Convertor). There is no way of jsf knowing the scope of these artifacts now. #5 is very good with bean entry having meta data. > 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, MYFACES-3786_bean-entry_draft_01.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)