[
https://issues.apache.org/jira/browse/MYFACES-3786?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13793565#comment-13793565
]
Leonardo Uribe commented on MYFACES-3786:
-----------------------------------------
The proposed solution goes as far as the reference implementation (in this case
Mojarra) goes, so my interest in this stuff for now (I want to get a beta out
as soon as possible, and the solution committed allows that). Maybe you can
propose a way to modify InjectionProvider interface without include CDI
specific API to do what you want. Remember we have these cases:
- Web server not using CDI, but using other annotations or other injection
container.
- Web server using CDI as a library but not integrated.
- Web server integrated with CDI.
And the big question is how to fill the gap in all possible cases. Maybe you
understand better how CDI works, so from this point it is all yours.
> 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, 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)
