[
https://issues.apache.org/jira/browse/MYFACES-3075?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Martin Kočí updated MYFACES-3075:
---------------------------------
Resolution: Fixed
Fix Version/s: 2.1.0-SNAPSHOT
Status: Resolved (was: Patch Available)
> Allow ELResolvers filtering
> ---------------------------
>
> Key: MYFACES-3075
> URL: https://issues.apache.org/jira/browse/MYFACES-3075
> Project: MyFaces Core
> Issue Type: New Feature
> Components: General
> Affects Versions: 2.0.5-SNAPSHOT
> Environment: myfaces trunk
> Reporter: Martin Kočí
> Assignee: Martin Kočí
> Priority: Minor
> Fix For: 2.1.0-SNAPSHOT
>
> Attachments: MYFACES-3075-v1.patch, MYFACES-3075.patch
>
>
> related to topic
> http://www.mail-archive.com/[email protected]/msg49177.html
> Problem:
> how to disable ELResolver smartly? Adding a context-param for each is an
> overkill.
> But we have https://cwiki.apache.org/MYFACES/elresolver-ordering.html in
> codebase already. I propose to add new feature "ELResolver filtering"
> and new context-param:
> <context-param>
> <param-name>org.apache.myfaces.EL_RESOLVER_PREDICATE</param-name>
> <param-value>org.foo.bazz.ELResolverPredicate</param-value>
> </context-param>
> Filter is simple instance of org.apache.commons.collections.Predicate.
> For application where no ManagedBean(Resolver) is used or no Flash, user
> can simply return false from Predicate.evaluate and ELResolver won't be
> installed.
> See mail thread here:
> http://www.mail-archive.com/[email protected]/msg52082.html
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
