[
https://issues.apache.org/jira/browse/MYFACES-3786?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13792881#comment-13792881
]
Gerhard Petracek commented on MYFACES-3786:
-------------------------------------------
@dora:
yes - only the dependent-scope (-> dependent to the application) makes sense
for those artifacts (for now). other scopes only make sense for MYFACES-3797.
@leo:
afair nobody said that cdi is mandatory. you can easily handle it with
different strategies.
imo it's also clear that we need to do the instantiation on our own (because no
additional default constructor is required by jsf - otherwise it would be
possible with dyn. added qualifiers). manual instantiation isn't typical for
cdi, however, it also doesn't conflict with cdi.
i'll have a look at your latest patch within the next days.
in general:
e.g. @Inject isn't a cdi annotation (it's from jsr-330). if there is no cdi
container or any other container we know/support, we can't provide injection
for it at all (from our side). outside of a specified ee-container it's
unlikely that we can support everything. imo the main question is what we need
to support on our side and which spis are needed for other containers and/or
servers like tomee for doing the rest. the more we delegate to the container
(if available), the more will work for users (as expected).
(in addition we should think about providing an alternative (proprietary)
approach which requires users to use cdi-decorators for creating the chain.
once we have a nice solution, we could suggest it to the eg for jsf 2.3+.)
> 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, 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)
