[
https://issues.apache.org/jira/browse/MYFACES-3786?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13795319#comment-13795319
]
Leonardo Uribe commented on MYFACES-3786:
-----------------------------------------
First, we only need to support the scopes JSF artifacts require. For now it is
only application scope, because all JSF injected artifacts are application
scope, and that will not change until 2.3. Forget about the problem with n
scopes. It is just smoke.
#0 +1 because we can extend it in the future if we require to do so.
#1 +0.5
#2/#3 +1 because we can extend it in the future if we require to do so.
#4 -1
#5 -1
Conclusion: #0 (keep things as is)
> 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,
> MYFACES-3786_internal_bean-entry_draft.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)
