[
https://issues.apache.org/jira/browse/MYFACES-3786?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13790719#comment-13790719
]
Leonardo Uribe commented on MYFACES-3786:
-----------------------------------------
This problem is not about CDI at all. Is about support of JavaEE 5 and 6
annotations, and that includes CDI too. In this case we need to track down not
only JSF spec but JavaEE spec too. I have done some tests and now I have an
idea how to fix it properly. It seems we need a CDI extension for this one, but
only as a fallback in those cases where there is not a JavaEE server (for
example, when you are using CDI and Tomcat or Jetty only). I'll start to work
on a patch for this one, the trick with this one is how to assemble all pieces
together.
> 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)
