[
https://issues.apache.org/jira/browse/MYFACES-3786?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13792253#comment-13792253
]
Leonardo Uribe commented on MYFACES-3786:
-----------------------------------------
I have attached a prototype for this issue. Basically the code refactor what we
have already in LifecycleProvider and include the new logic related to CDI, and
fix injection on Factories and in PhaseListener. I changed the name of the spi
interface to InjectionProvider too and add the method to check if the provider
is available or not. It also includes a trick to check if a bean is injected or
not using the web server api (tomcat 7). It has a pure CDI injection provider
in case there is no matching InjectionProvider and CDI is available on the
environment.
I have done some tests with tomee and it works so far. The solution still needs
more work, but I think the patch reflects the basic structure of the solution.
> 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, MYFACES-3786-1.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)
