[
https://issues.apache.org/jira/browse/RAVE-644?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Anthony Carlucci resolved RAVE-644.
-----------------------------------
Resolution: Fixed
I modified the RavePermissionEvaluator to look for any registered
ModelPermissionEvaluators that are registered to an interface that the target
model in question implements. If it finds one, it adds a registration entry
into the internal map for the class type. So this will allow one model
permission evaluator to be registered for a given model interface (like Page),
and allow any implementation class of that interface to use it (like JpaPage,
MongoPage, FlatFilePage, etc)
> Fix ModelPermissionEvaluators
> -----------------------------
>
> Key: RAVE-644
> URL: https://issues.apache.org/jira/browse/RAVE-644
> Project: Rave
> Issue Type: Sub-task
> Reporter: Anthony Carlucci
> Assignee: Anthony Carlucci
>
> After changing to the interface based models, our
> Default***ModelPermissionEvaluators will fail because the intenal map of
> evaluators built in the RavePermissionEvaluator uses the class name
> (interface) as the key, and now the objects coming into the evaluators will
> either be Jpa* or *Impl objects, and not match up to an evaluator.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
