[
https://issues.apache.org/jira/browse/MYFACES-3786?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13791940#comment-13791940
]
Gerhard Petracek commented on MYFACES-3786:
-------------------------------------------
yes and no - there are good arguments for both - you are just talking about the
minimal requirement (which is fine for the beginning and even easier - see e.g.
BeanProvider#injectFields + keep CreationalContext and InjectionTarget for the
cleanup at the end.)
the spec. wording you mentioned is highly ambiguous, however, the spec. also
contains a better wording which is "...Eligible for Injection...".
@faces-config.xml
agreed - you just have to handle classes/beans which are configured. imo nobody
questioned that at all.
> 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
> Attachments: cdiELresolverWeb.zip, cdiELResolver.zip,
> cdiPartialViewContext.war, cdiPartialViewContext.zip, cdi.patch,
> cdiphaselistener1.patch, cdiphaselistener2.patch, cdiValidatorSource.zip,
> cdiValidator.war
>
>
> 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)
