You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@isis.apache.org by "Dan Haywood (JIRA)" <ji...@apache.org> on 2015/01/07 02:19:35 UTC
[jira] [Resolved] (ISIS-985) Filter collections so that objects
that are not visible to the current user are not shown.
[ https://issues.apache.org/jira/browse/ISIS-985?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Dan Haywood resolved ISIS-985.
------------------------------
Resolution: Fixed
> Filter collections so that objects that are not visible to the current user are not shown.
> ------------------------------------------------------------------------------------------
>
> Key: ISIS-985
> URL: https://issues.apache.org/jira/browse/ISIS-985
> Project: Isis
> Issue Type: New Feature
> Components: Core, Viewer: Wicket
> Affects Versions: viewer-wicket-1.7.0, core-1.7.0
> Reporter: Dan Haywood
> Assignee: Dan Haywood
> Fix For: viewer-wicket-1.8.0, core-1.8.0
>
>
> There are two bits to this.
> First, note that we have similar functionality when rendering an object itself, throwing a 404 if none of the object's members are visible. However, there should also be a check if the object itself is not visible, ie through a new ObjectVisibility check. (We already have ObjectValidity check as well as {Action/Property/Collection}Visibility, so all the required concepts exist.
> Second, the object visibility check should be used to determine if an object should be rendered in a collection/table.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)