[
https://issues.jboss.org/browse/RF-10755?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12600644#comment-12600644
]
Martin Kočí commented on RF-10755:
----------------------------------
With MyFaces 2.1 it is now possible to filter out unwanted ELResolver including
ManagedBeanELRsolver:
http://www.mail-archive.com/[email protected]/msg52082.html
https://issues.apache.org/jira/browse/MYFACES-3075
> managed-bean in richfaces-core-impl
> -----------------------------------
>
> Key: RF-10755
> URL: https://issues.jboss.org/browse/RF-10755
> Project: RichFaces
> Issue Type: Enhancement
> Security Level: Public(Everyone can see)
> Components: compatibility
> Affects Versions: 4.0.0.CR1
> Environment: Richfaces 4.0.0 branch
> Reporter: Martin Kočí
> Assignee: Konstantin Mishin
> Fix For: 4.1.0.Milestone1
>
>
> richfaces-core-impl contains three definitions of managed-beans:
> a4j
> a4jSkin
> richSkin
> By mistake one of our coders created CDI bean named "richSkin" and that
> caused malfunction of richfaces skinning.
> Suggestion: do not provide those beans but implement them as implicit object
> (similar like JSF implicit object "view" or "sessionScope")
> There is SkinPropertiesELResolver already, all what needs to be done is
> define new implicit object "richSkin" and handle it there in similar way how
> JSF impl handle implicit objects.
> a4jSkin managed-bean seems to be obsolete, about a4j(VerionBean) I'm not sure.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
_______________________________________________
richfaces-issues mailing list
[email protected]
https://lists.jboss.org/mailman/listinfo/richfaces-issues
