[
https://issues.apache.org/jira/browse/MYFACES-3786?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13795334#comment-13795334
]
Gerhard Petracek commented on MYFACES-3786:
-------------------------------------------
initially i said that we can change it for custom scopes once it's needed and
you said that you don't like to change the spi later on.
however, the positive effect is that we have an approach which doesn't need
unique-ids per instance to find the meta-data for that instance (in
#preDestroy). that's imo the most important reason for using #1 or #5 (and not
using #2-#4).
since we have the patches already, there is no reason to postpone it. i'll
commit #1 soon.
we can to the internal change suggested by dora at any time.
> 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, cdirevised.patch,
> cdiValidatorSource.zip, cdiValidator.war, MYFACES-3786-1.patch,
> MYFACES-3786-2.patch, MYFACES-3786_bean-entry_draft_01.patch,
> MYFACES-3786_internal_bean-entry_draft.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)
