[
https://issues.apache.org/jira/browse/MYFACES-3786?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13792718#comment-13792718
]
Dora Rajappan commented on MYFACES-3786:
----------------------------------------
According to what @Gerhard via injectionTarget.
Also the weld reference says
"The first thing that a framework developer is going to look for in the
portable extension SPI is a way to inject CDI
beans into objects which are not under the control of CDI. The InjectionTarget
interface makes this very easy.
We recommend that frameworks let CDI take over the job of actually
instantiating the frameworkcontrolled
objects. That way, the framework-controlled objects can take advantage of
constructor
injection. However, if the framework requires use of a constructor with a
special signature, the
framework will need to instantiate the object itself, and so only method and
field injection will be
supported. "
> 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)
