[
https://issues.apache.org/jira/browse/MYFACES-3786?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13795241#comment-13795241
]
Leonardo Uribe commented on MYFACES-3786:
-----------------------------------------
"... if you bypass the cdi context-management, you have to do the equivalent on
your own. ..." that depends on how far you want to go in the integration. The
minimum is go as far as the reference implementation (Mojarra) goes. Going
further is insist in solve a problem that clearly is out of the scope of JSF
2.2, and no matter how hard we try, it will be always a partial solution.
Does JSF need to know what's inside the metadata? no. The only thing that JSF
needs to know is that this piece of information needs to be stored somewhere.
In #5, it introduce some extra objects that are only used in the context of the
InjectionProvider, which means JSF doesn't care about that. #1 avoid extra
instantiation.
> 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)
