[
https://issues.apache.org/jira/browse/MYFACES-2005?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12638155#action_12638155
]
Leonardo Uribe commented on MYFACES-2005:
-----------------------------------------
This issue is not blocker and it is not a bug, rather it is an improvement.
Really, it is related to MYFACES-1999, because GuiceResolver actually does not
handle create managed beans and its related tasks (this is one of it).
> GuiceELResolver doesnt populate fields in managedBean
> -----------------------------------------------------
>
> Key: MYFACES-2005
> URL: https://issues.apache.org/jira/browse/MYFACES-2005
> Project: MyFaces Core
> Issue Type: Improvement
> Components: Extension Feature
> Affects Versions: 1.2.0, 1.2.2, 1.2.3, 1.2.4
> Environment: eny env with myFaces impl ver 1.2.*
> Reporter: Anton Gavazuk
> Priority: Minor
>
> org.apache.myfaces.el.unified.resolver.GuiceResolver does not work properly
> it creates new instance of managedBean class, and injects needed features in
> it, but parameters from form remain in previous bean (created by default
> ManagedBeanResolver)
> And now execution path of resolvers is unclear - because every managedBean
> will be created for 3 or 4 times per request.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
